argief:
nd named depends on the architecture and bootloader version being used. The boot config in step 8 is pretty straight forward. There is an “A” and a “B” option, and then 2 “recovery” versions of same. The trick was in selecting the right drive and partition for the kernel (bzImage) and then identifying the root partition correctly so the kernel can handover to the OS. What worked in the end was to reboot, then hit “c” for command line when the GRUB menu came up. There I could run “ls” to see how my drives are being labelled. I had to change (HD0, GPT1) to (AHCI0,msdos7). The “root=” is defined by UUID (unique hardware reference to the partition) but this gave me a “Waiting on root” message and hanged for hours even after updating the UUID to the one matching the new partition. I replaced it with “root=/dev/hda7” (7th partiti
Hi @jscongdon was wonding if you were able to find a solution to this issue. I’m getting a similar issue with the boot slots and HAOS booting to the older OS version in Boot Slot A instead of the updated version 14 in Boot Slot B.
Similar issue:
Hello,
I have a Pi 3B with an SSD.
My solution was to flash the 12.4 image and restore the backup.
I tried using a better power supply, increasing the swap memory, and updating all the add-ons before the update, but everything failed. If the RPi 4 has the same issue, it seems to be a software problem.
So, I decided to stay on 12.4 and wait for a future fix.