Hassio doesnt start with last update!

I did a clean install to 4.15 and restored a backup. Everything worked fine again. Just for fun I updated to 5.18 again and everything was bricked again. I’ve took some screenshots. Hopefully someone will be able to fix this.



no purpose, I thought you didnt have monitor :slight_smile:

1 Like

i dont have a monitor… same problem… pi doesnt boot after update.

No booting here as well.

1 Like

I too suffered this issue.

The first thing I did was upgrade the OS from 5.5 to 5.8 and this worked fine, did a reboot to make sure it came up without issue. I then went ahead and upgraded to 2020.12 and like everyone else had the problem with the reboot. I then did a rebuild and moved my SSD from the Raspberry and flashed the latest figuring that might solve the problem. No luck. I moved my PI to my Den and hooked up a Monitor and Keyboard. Typed in the suggestion above (Root followed by Core Start) and that allowed me to bring up an empty Home Assistant. Put the PI back in my Server Closet and restored my config (but did not select 118.4) and I am back up and running.

I wish I had seen this thread before going through and restoring would have been easier.

as confirmed in thread below, 5.8 doesn’t boot from ssd neither when updated from previous 5.x nor installed from scratch

Not booting here neither :frowning:
RP4 4GB

As an FYI, I am running from an SSD. So SSD Boot works with 5.8.

This is how i got Home Assistant working again on my Odroid C2:

Download 4.15 image and write to storage (SD/eMMC): https://github.com/home-assistant/operating-system/releases/tag/4.15

When credentials are asked, choose the restore from backup option and select your pre-upgrade backup.

After a successful restore run the following command in the terminal:
ha os update --version 4.20
to upgrade HassOS to version 4.20.

HassOS 4.20 is now running stable with Supervisor 2020.12.6

1 Like

Are you using any ‘quirks’?

I can’t get 5.6 or even 5.2 to boot now either!

I’ll try via Raspbian to go back to an older version of the eeprom. Can’t work it out right now!

Nothing that I recall, followed the instructions here.

I did the OS uprade first and it stopped working.
After 3 cold boots hass started again.
The upgrade to 2020.12 worked but still offered the update after reboot while it showed the updated version under system.
After another reboot there were no more issues.

My C2 also did not reboot from the update from 5.7 to 5.8. I tried to do a fresh install based on the 5.8 image, but that also does not work. I connected an HDMI cable, but the C2 does not give any output at all.

My Pi 4 wouldn’t be connected to after updating the OS. Initially it showed up in the router, but after a while it disappeared, so I’m thinking it might have been just a remnant. I pulled the plug and reinserted it a few times, to no effect. Here’s what worked for me:

  1. Pulled the plug again
  2. Unplugged USB hub with Conbee stick and Ethernet cable
  3. Waited a while, still couldn’t connect (I’m not sure if it has any Wi-Fi credentials or not)
  4. Plugged the Ethernet cable back in
  5. Connected to my HTTPS DuckDNS as usual. Fixed!

I had this issue and the “root” suggestion above didn’t work for me. Manual power cycling was bringing me back into the supervisor, but without the update applied.

I managed to fix it by SSH’ing into the device and running the “ha supervisor repair” command. After this, the update ran successfully and the reboot was successful.

I followed your instructions and it works again.
But we need to know what is wrong with last update.
Can we apply it sometime soon?

So? Any thoughts?
I guess it is not normal to brick so many devices by an update.

devs more or less have answered in release thread that they are not gonna support ssd boot. They fave vslid reasons too.
Instead they encourage to use sd boot with data moved to ssd.
IMO they will promote this way, intentionally or not leaving us with decission to change approach to only proper one, or risk reliability of our installations

OK. But my setup is on SD card. Nothing to be related to SSD boot. And my system like others was bricked by this update.

1 Like