Node couldn't boot after upgrading to Umbrel OS 1.2

[matrix_stuff]

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:

System doesn't boot (fail to mount) and GRUB menu non existent for troubleshooting

I solved the problem in 2 steps: I unlocked the root user: To unlock the root user I booted from a live USB, then mounted the HDD with Umbrel, and used the “chroot” method to root into the file system and change its root’s user password. Here are the commands I used: lsblk sudo mount /dev/sdc2 /mnt/c2 sudo mount /dev/sdc1 /mnt/c1 sudo mount -t proc none /mnt/c2/proc sudo mount --bind /sys /mnt/c2/sys sudo mount --rbind /dev/ /mnt/c2/dev sudo /usr/sbin/chroot /mnt/c2 sudo passwd root exit T…

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:

1. 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).
2. How is it that I don’t see the effect of the update anywhere?

[matrix_stuff]

This is how the error looks like. I just tried it again. If I just restart the machine it rolls back to 1.1 and again recommenda the update to 1.2

[umbrel101]

Seems I have the same issue. Can you explain how to fix this?

[TCalache]

I have the same error. Pelase, can sombody help us?

[TCalache]

I solve the problem by doing the format on my SSD. I used a run ubuntu from usb without installing to do this

[Daiko]

I finally solve this annoying problem. It’s related with mounting data

Find here the post with all the info

UmbrelOS Update Fails on Large‑Disk Nodes — Emergency‑Mode Boot Loop After Upgrade

The Problem On UmbrelOS x86 installations using large hard drives (e.g. 8TB), updating from version 1.3 to 1.4 (or likely any future version) causes the system to fail during boot. Specifically, the boot process halts in emergency mode because: data.mount fails due to timeout. Why This Happens 1. UmbrelOS uses a dual-partition A/B upgrade model UmbrelOS applies updates to the inactive root partition (e.g. /dev/sda3) while running from the active one (/dev/sda2). Afte…

[jfpoub]

Another way, if your first unbootable UmbrelOS (sda) is in a VM, stop the VM, add a disk of 32GB, install the iso of UmbrelOS (1.5 now) on the second disk not the first unbootable one (in order to keep the blockchain). Until the new UmbrelOS is installed on the second disk (sdb).

Mount the /dev/sda3 (/data) of the first unbootable disk

Change/correct the bad /etc/fstab

Stop the VM

Delete the new disk and verify if the first one is now booting after correcting its bad /etc/fstab