operating-system: Stuck waiting for home assistant cli to be ready

I had the same problem. My system got stuck with the message Waiting for the Home Assistant CLI to be ready.... During boot it run into a 1:30 min. timeout when accessing the /dev/disk/by-label/hassos-data.

My solution after 2-3 hours research was relabeling the /dev/disk/by-label/hassos-data-old into /dev/disk/by-label/hassos-data.

But How?!

1. Within the open blocked console with the text “Waiting for the Home Assistant CLI to be ready…” hit Ctrl+Alt+F2 to open a second terminal.
2. here you have to login to HassOS in my case the user was “root”
3. Now you should have a terminal to work with.
4. Here you should check the label with e2label /dev/sda8. Im my case this returned hassos-data-old. Probably in your case the device is different.
   If it returns the correct hassos-data then this solution is probably caused by another reason.
5. To rename the label execute e2label /dev/sda8 hassos-data
6. Finally reboot HassOS by executing reboot in the terminal.

I hope this step by step guide helps the not so experience users.

My Environment: HassOS in an LXC container on Proxmox running in a Celeron Intel NUC

1. Within the open blocked console with the text “Waiting for the Home Assistant CLI to be ready…” hit Ctrl+Alt+F2 to open a second terminal.

2. here you have to login to HassOS in my case the user was “root”

3. Now you should have a terminal to work with.

4. Here you should check the label with e2label /dev/sda8. Im my case this returned hassos-data-old. Probably in your case the device is different. If it returns the correct hassos-data then this solution is probably caused by another reason.

5. To rename the label execute e2label /dev/sda8 hassos-data

6. Finally reboot HassOS by executing reboot in the terminal.

After getting a system unhealthy error within home assistant (which led to this error page). After rebooting the system, it was stuck on Waiting for Home Assistant CLI to be Ready. After following instructions from @rvdbergh, it was able to successfully start.

Finally, to solve the problem of the screen being stuck on ‘waiting for the Home Assistant CLI to be ready’, I had to make sure all partitions on the drive were removed. This was necessary because Balena Etcher doesn’t completely wipe the disk. Then, I connected the target disk to an external reader and used Balena Etcher to write the latest Home Assistant OS onto the disk. This solution worked like a charm

Same here.

The problem was that the device had a zfs_member signature. wipefs fixed it.

In the end I relabeled /dev/sda8 from hassos-data-backup to hassos-data, rebooted, and Home-Assistant came back.

@willsargent I don’t have the command “supervisor”

@himslm01 I did “supervisor repair” at the CLI, and that seemed to bring the web interface back to life after a few minutes

Had the exact same issue, my problem was that I had an ubuntu installed on ssd I’m using and leftover zfs metadata was left on an ssd. Formatting it clean to unallocated with gparted solved it for me.

I encountered the exact same issue when updating from HA 2023.5.0 -> 2023.5.1 and found that my hassos-data partition was labeled as LABEL="hassos-data-old". Removing the “-old” from the label and rebooting fixed the issue.

Maybe the root cause lies somewhere in the data disk move script, as @agners stated above.

So I tried installing on 3 different Lenovo machines, all failed. Intel and AMD. Different firmware versions, every permutation I could muster. Tried an HP laptop and bingo. No errors and up-and-running first time.

@mac-city I’m not sure we’re facing the same issue. I have no prompt to type “login” at, it’s just stuck at a black screen which says “Waiting for the Home Assistant CLI to be ready…”. The system time messages appear to be a red herring, the main issue seems to be that the hassos-data is never set up.

@ipm79 It seems we have the same issue, have you made any further progress?

I am having the exact same issue - start job for hassos-data is timing out and system is stuck on “waiting for CLI to be ready”. I don’t use a NUC but a Lenovo ThinkPad T540p laptop. Booting from a live Ubuntu USB drive shows a 255GiB partition at the end of the disk but without a filesystem.

Some new details as I’ve been trying to debug this issue today. After a fresh install the boot process seems to stall out at two tasks:

• start job is running for Wait Until Kernel Time Synchronized
• start job is running for /dev/disk/by-label/hassos-data

I thought maybe originally this was an issue with DNS and not being able to resolve time.cloudflare.com, but I’ve ensured my router is providing 1.1.1.1 and 8.8.8.8 as DNS servers now so there shouldn’t be any curious blacklisting, or rate limiting. Another weird network-related clue is that when the machine first boots the ethernet appears to be functional (lights up on the router and the back of the NUC), when it goes through the init process the network shuts off, and when I eventually get to “Waiting for home assistant CLI to be ready…” the network is back on again.

I now think the issue is actually the initial step to set up hassos-data. Eventually the timeout says that start job timed out waiting for device. When I boot the machine back on a usb stick and view the partition table for the disk, its showing me that hassos-data exists but its unformatted - is that expected?