Hi

 

I had to upgrade my Odroid N2 from Armbian Buster to Armbian Bullseye to run newer versions of Nextcloudpi (24.x).

So I did the upgrade by writing the Armbian 22.05 version to the eMMC and started Armbian.

Works fine.

Then I installed a fresh nextcloudpi (23.0.2) which is the same version I used on Armbian Buster.

Works fine. I added the external disks (ncdata und ncbackup). After a restore of my nextcloudpi backup everything was well.

But the next reboot did nothing, i.e. no output on the HDMI Interface, nothing.

So, I did a power-off and looked at the eMMC via a Micro-SD adapter I have.

Of course, no logs, nothing.

Of course, there are no logs in /var/log because of the /dev/zram1 mounted at /var/log.

Mounting /dev/zram1 on /var/log might be good if everything works, but if a reboot fails,

you are host.

I found a work-around: disable apache2 startup by editing the systemd unit file - I couldn't use systemctl

because the system did not boot.

After plugging in the external disks (nc-automount was enabled) and correcting the unit file, I could start

apache2 and nextcloudpi is running well - until the next reboot.

So, how do I disable the mount of /dev/zram1 to /var/log to find the real culprit ?

Is it sufficient to delay the start of apache2 by adding

      ExecStartPre=/bin/sleep 30

?

 

Thanks for your advice.

Kind regards

Norbert

Edited June 30, 20224 yr by NOBL
several typos

It does not just reboot automatically, but it crashes after a few hours of use.

In addition it automaticall shuts down after a while.

I am sick of opening the case, remove the eMMC, put it on the Micro-SD adapter, put it into the Micro-SD slot on my computer, edit the apache2 startup script, put the eMMC back on board

and start the Odroid N2 again and repeat this several times a day.

OK, I'll try to figure out myself how to stop using /dev/zram1 as /var/log.