newest update crash my owncloud server

Troubleshooting
1

im totally pissed off actually

update to new version 6.20.5 crashes my server complete

im running dietpi on Odroid C2

Owncloud is not reachable and SSH is also not running

Ping to the server fails

thanks for this :cry:

Instead of putting more and more features to dietpi you better should test that updates are working

2

Thanks for your report and yes there was an issue with the update, that occurred in rare enough cases, that it passed all our own and beta tests :face_with_raised_eyebrow:.

This is resolved with v6.20.6. If even SSH is down, I am not sure if there is another issue in your case, but pretty sure it is related at least.

Please attach monitor and keyboard to your C2 to access local console. You might face a dietpi-software prompt on login, or error messages that DietPi-Login script failed. In case cancel everything, also check htop for any running DietPi scripts and kill them (navigate to them via up/down buttons and hit F9 and return to kill).

To be failsafe, restore the v6.17.9 state:
echo 1 > /DietPi/dietpi/.update_stage
echo 1 > /DietPi/dietpi/.install_stage

Reapply the update (now to v6.20.6):
dietpi-update 1

3

Yup, my Odroid C2 server bit the big one with this update also. Practicing some anger management.

4

Poui
Did you face issues when updating v6.19.7 => v6.20.5
or as well when directly updating to v6.20.6 (which is live for some hours now)?

In first case, please try to apply the steps mentioned above.
In second case, some more details would help to investigate.

5

sorry for my hard words last night
i like dietpi and recommend it to anyone who uses a sbc but sometimes it makes me desperate
I spent a good part of last night bringing my server back to life.
With a local keyboard and monitor I did the last backup.
now it runs again
I have a bad feeling starting the update again.
you said the update to 6.20.6 should work ?

6

perlian
No worries, totally understandable that such surprises are frustrating.

In case interested: Finally I even understood how/why the error occurred, at least most important one. We added a fix for a certain situation and did a change that relied on that fix. However for one single shutdown directly after the update, the fix might not yet be “active” on the running system. Sadly in most cases this was no issue (so it was not recognized during own and beta tests), but in some it was: DietPi-RAMdisk was “able to” attempt writing RAMdisk content do /boot, after the /boot partition was already unmounted, which caused the mixed/broken system state after reboot.

Yeah the above issue is fixed + some other hardening done with v6.20.6. But as always, keep a backup ready, and if you already have it there, apply the update with keyboard + monitor on local console, just to be failsafe this time.

We will take the last day of update issue reports serious and increase our testing efforts, especially on the update process. One should not have bad feelings before every update…

7

I had the same issue with all of my C2’s plus the rpi1. Once I launched dietpi-software and selected “Install” without making any changes, every service was available again upon reboot. Was a bit scary, though.