After updating from Umbrel 1.1 my node (laptop with native install of Umbrel OS) did the restart but then got a failed boot because the mount of the HDD took more than 3 minutes (it takes 5 to succeed), which then took me into the emergency mode, but again, as I reported in a previous post, Umbrel auto locks the root user, so I end up in an endless loop without being able to troubleshoot.
I reported about this bug in this post:
So what happened is that I had to use a live USB to get into chroot, reset the root password again, and then when I restarted the HDD with Umbrel, it booted to the previous 1.1 version successfully. I’m guessing that it keeps the old version in case of failure? I can’t tell because even the journalctl logs don’t show the previous failed boot. It’s as if it never happened.
So:
- Please fix the Umbrel release so it doesn’t lock the root user, and add more time for the system to mount the HDD (10 mins is enough, 3 is not).
- How is it that I don’t see the effect of the update anywhere?