Mine is stuck too. I’m running on a Virtual Machine and upgraded from HassOS 5.x to 6.0 - it just sits at a shell command prompt and looking at the VM, it isn’t doing much in terms of CPU time (ie., don’t think it is loading up Home Assistant)
But I discovered 2 things:
Supervisor system section tells me it is a “Development” build. Is this just correct?
The protocol log of each add-on needs a long time to load (~10-15 seconds). This also affects the logging entries for supervisor system (~20 seconds).
At least for the add-on section this sounds like the reporting from @brucek1642
Same thing here in a proxmox VM.
Just 1%cpu, 130mb mem usage. Doing nothing basically.
I have put node red in a separate container just for this. More logical, instead of a container inside a container. Faster as well anyway.
Same problem for me xu4 with external data partition. First time attempt to upgrade, it shutdown and never rebooted. After power cycle it was still on 6.0rc3. Retried install and second attempt worked.
Fwiw, the upgrade from 5.13 to 6.0rc3 went smoothly.
I have run into that issue with my virtual machine. To fix it, I remove the virtual drive from the VM, delete the VM, then create a new one with the same virtual drive. Takes about 5 mins to do and it is back up and running.
Is it only a message shown during boot process (which I never see cause it´s headless)? And is it only shown when a SSD is being detected?
I´m planning to switch from SD to SSD and currently use original 3.0 A power supply. There even almost are no 3.5 A or 4.0 A power supplies for Pi 4 in my area.
The system will fall back to the previous installation after three unsuccessful boot attempt. But it seems that the corruption is on the writable partition which is shared between the fallback and the main OS installation, so it likely won’t help.
Probably the best way forward is a new installation on a new SD card…
