Nextcloudpi on Odriod N2 (and N2+): Updates impossible for nextcloud

[NOBL]

Hi

 

Unfortunately, I use an Odroid N2 (and N2+) for nextcloud installed via the nextcloudpi script. Now, the support is gone and there are no longer updates for nextcloud beyond version 30.0.x available.

Currently I am running nextcloud 30.0.17. The version 30.0.x will reach end-of-support soon.

I can imagine the following alternatives:

1.  Use armbian-config to install nextcloud - but will it do the update correctly or at all esp. for my external disks which nextcloud is using ?
2. Use the image for the Odroid C2 (another arm-based SBC) and replace the kernel by the one for the Odroid N2+
3. Port the script from the Odroid C2 image to my Odroid N2
4. Buy an Raspi 4 or, even better, a Raspi 5 and use the images for that HW - how about a migration path ?

 

So what do you suggest ?

I think I could do all of those alternatives myself and I have an Odroid N2 and an Odroid N2+ useable for testing purposes.

One of those was planned to run HomeAssistant and I'm happy that HAOS is supported on my hardware. But that can be postponed to later.

 

Kind regards

Norbert

Edit: Added question for the migration path if HW changed to Raspi 4 or 5

 

Edited 21 hours ago by NOBL

[geoW]

I have no clue of your Odroid hardware, but nextcloudpi there

sudo ncp-config

-> system -> info

will start with an overview

pi@nc-rspios5:~ $ sudo ncp-config
Running nc-info
Gathering information...
NextcloudPi version  v1.55.4
NextcloudPi image    NextcloudPi_06-01-25
OS                   Debian GNU/Linux 12. 6.12.47+rpt-rpi-2712 (aarch64)

 

ncp version 1.55.4 is only offered to running instances and no image is provided on github to start with.

But this version offers support of nextcloud 31 which gives you some more month support, ncp maintainer is ttrying 

to get supprt done to nc 32.

You may try

sudo ncp-update

and then

sudo ncp-update-nc

 

[eselarm]

19 hours ago, NOBL said:

I use an Odroid N2 (and N2+) for nextcloud installed via the nextcloudpi script

I see from https://github.com/nextcloud/nextcloudpi/releases

that 'pi' is sort of a synonymy for 'ARM SBC' or pre-installed images. 'pi' is great but a problem as it is not generic arm64 so every SBC flavor needs a 1GByte zip image just for a different kernel and bootloader. 

 

Same as long time ago I used a 'pi' script to get Node-RED installed in an x86 Debian Bullseye Virtual Machine (so just 'Debian' actually), I would focus on generic solutions. Armbian is doing very well w.r.t. alignment and portability, so the SoC or SBC does not really matter, as long as it is compliant with Debian ARM64. 

For Node-RED on Opensuse-Tumbleweed ARM64 I needed to hack the script a bit to fake a compliance check, but with that, it also worked. It saved an enormous amount of effort re-installing OS etc.

 

So bottom line is, maker sure you don't lock yourself into a certain SBC or SoC, but make sure it is standard generic ARM64 (or standard x86-64, which is already the case for years)

 

A way to keep your current installation is to 'virtualize' it: What runs on the Odroid or RaspberryPi or other SBC from SD-card or eMMC or NVME or SSD can be made EFI bootable and then it will run as virtual machine on the same SBC or other new/faster SBC of course as well. I have done this for RPI3B functions -> RPI4B in the past (also 32-bit VM in 64-bit host, Pi-Hole for example) and this year again to replace RPi4B-8GB with ROCK5B-16GB. It is beyond the scope of this topic, but start with installing 'virt-manager' and try to boot and Armbian-UEFI image/instance.

 

Or see: https://github.com/nextcloud/vm

I haven't used 'cloud' since owncloud, but right now, if I would certainly start with a VM. Same for e.g. HAOS, runs fine in a VM on ROCK5B. You do not need proxmox, all is build-in in Linux already.

Edited 1 hour ago by eselarm