Running HAOS on a rasberrypi5, hybrid SDD setup. I received the update notification for HA OS 14.0 this morning and gave it ago. HA did not boot after 2 attempts. On third attempt it booted to slot b successfully.
Welcome to my world, have been stuck on 12.3 for months, any update past that just bricks the system, including the latest 14.0.
That’s the problem with a project like this, it’s now so unbelievably complicated, that when bugs like this come up, there in no hope of getting them fixed.
I have the same issues. I tried downgrading slot B to 13.1 which worked and then proceeded to upgrade to 14.0. Both slots now are on 14.0 but I have the most curious status display where both slots are 14.0 but the os reports to be on 13.2???
board: rpi5-64
boot: B
boot_slots:
A:
state: inactive
status: bad
version: "14.0"
B:
state: booted
status: good
version: "14.0"
data_disk: KINGSTON-SA400S37240G-50026B738188555E
update_available: true
version: "13.2"
version_latest: "14.0"
Does anyone know if it’s possible to “wipe” a boot slot? I had some issues a while back and tried 14.0 rc1. It didn’t work at all and my boot slot B was marked as bad.
Now I can’t upgrade nor downgrade as any attemt changing anything in slot B throws an error.
My current status according to os info:
➜ ~ ha os info
board: rpi5-64
boot: A
boot_slots:
A:
state: booted
status: good
version: “13.2”
B:
state: inactive
status: bad
version: 14.0.rc1
data_disk: CT500P3SSD8-2403463A4A7A
update_available: true
version: “13.2”
version_latest: “14.0”
And the error I get from the supervisor trying to update OR downgrade:
ERROR (MainThread) [supervisor.os.manager] Home Assistant Operating System update failed with: Installation error: Failed updating slot boot.0: failed to run slot hook: Child process exited with code 1
Still suffering the same issues and haven’t found a way to get this resolved. Here is a bit of detail since my last post.
Back on December 9, Slot A was bad (v14.0 installed) with Slot B on v13.2 and booted.
With the release of 14.1, I tried to upgrade today but it failed. Both boot slots showed 14.1 and good, but the system says I’m running 14.0 (slot A). Similar scenario to @hugobloem, above, except different OS versions in play (still, the active version doesn’t match what the system thinks is installed).
Forced slot B back to 13.2 thinking maybe the slot switching has to see older versions in the offline slot. 13.2 showed installed but the slot was marked bad.
Using CLI, did the standard update ha os update which installed 14.1 into slot B but it reports as bad and booted into Slot B.
Using CLI, I forced the system over to Slot B and it attempts to load but fails back to slot A (v14.0). I attempted to watch the yellow LED to see if I got an error on why booting failed, but wasn’t able to distinguish anything. Maybe I’ll try it again and see if I can record it.
Just joining the “same here” crowd but have posted about this issue as well. CM4 on official I/O Board and just moved my data disk to a USB SSD while troubleshooting a separate issue. All checks, repairs, and rebuild commands come back clean.
# ha os info
board: rpi4-64
boot: A
boot_slots:
A:
state: booted
status: good
version: "14.1"
B:
state: inactive
status: good
version: "13.2"
data_disk: External-USB3.0-201703310007F
update_available: true
version: "11.5"
version_latest: "14.1"
GUI reports the same 11.5 version and if I update it has been taking me back to 11.2 for some reason. If I update again, it takes me back to 11.5! Something is wonky but I have no idea where the system is caching the version or upgrade details. I got to 14.1 by using ha os update --version but following reboot, and a hard power cycle, the version is still reporting as 11.5. Do not feel like rebuilding a working production box, just don’t know enough (yet) about haasos to dig around.
