Waiting for home assistant cli to be ready

Configuration
1

Earlier today I chose to upgrade my HA Core to 2023.11.0
I had a list of 6-7 pending updates so I manually performed a full backup of HA before starting the core update.
When I launched the core update I did not check the backup box (because I just made a full backup).
HA has not come back. I must have waited 2 hours but I could not reconnect to HA – still installing update.
Eventually I did a hard reboot on my x8086 pc on which HAOS is installed.
The linux terminal window eventually shows up with a message at the top saying “Waiting for the home assistant CLI to be ready …”
There is a prompt on my terminal screen ha>
Is there a terminal command I can enter to restore HA from my full backup?

2

I have the exact same issue (with virtualbox). I don’t know what to do to unlock the situation !

Edit: I have just solved the issue following those instructions :

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.
    5.Probably in your case the device is different.*
    6.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.

11 Likes
3

Thank you. I would have gotten here eventually, but you saved me hours of toil.

1 Like
4

Hi, this happened to me today when I installed the core update that came out. How do I find the file I need to change the name of once I get the second command terminal open? I don’t know many of the ha cli commands.

5

Big thank you. It worked, following your instructions step by step. The only problem I found was when trying to log into HassOS. I tried every user/pwd combo I have ever used, but no luck. Until I simply used “root” as user. And that solved it all. If I had only read your msg paying more attention…

6

Thank you. Saviour.

1 Like
7

Hey,

got the same issue today after the last Core Update. I am stuck at “e2label /dev/sda8”, because it can not be found (no such file or directory… → Couldn’t find valid filesystem superblock) . Am i screwed :(?

8

Got the same issue this week.
Renaming the label fixed the booting problem.
Big thank you!

9

Just adding my “thank you” to the list! While updating to the latest HA core and OS - I ran into the same issue, followed your steps, and now everything is back up and running!

Thanks again!

10

I am in the same boat as Reaver 1988. I get the “no such file or directory” error when I execute e2label /dev/sda8. Anyone have any ideas what could be going on?

11

I had the same problem. HA is not my main system so far therefore I have no idea how long was it on this waiting for CLI screen but it must have been a few months. I tried everything I found and nothing made any difference so I tried a different approach. I am running HA on Virtualbox on Linux Mint so I mounted VDI file to the system using this example. Checked all partitions there and the only thing in /dev folder were 4 files, no subfolders. But in one of the partitions I found backup folder with *.tar files which I copied to my system. Then I got new version VDI file from HA website, started new virtual machine and restored system from that backup I copied.
Sorry for lame explanation, I am quite a noob but I hope it saves some time for someone.

12

I get the same “waiting for home assistant CLI to be ready” on a brand new install on a Pi 4B, and none of these suggestions work.

I can get to the console and the login in, but because I have missed the “onboarding” section I don’t have a username or password and can’t progress

Any help please as I’m about to give up after 10 hours!

TIA

13

I’m a Linux newbie, and I was also struggling with the situation where dev/sda8 was not found.

I’d like to share what I’ve learned from investigating this issue.

The cause of this incident is that the “hassos-data” partition on the SD card has become unreadable due to some problem.

Since I had a PC running Ubuntu Desktop, I checked the SD card partitions using a disk utility and confirmed that “hassos-data” exists but cannot be read.

So, when I ran “sudo e2fsck -a /dev/sda8” in the Ubuntu terminal, I got the following error message:

e2fsck: Bad magic number in super-block while trying to open /dev/sda8 /dev/sda8: The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it really contains an ext2/ext3/ext4 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> or e2fsck -b 32768 <device>

So, I ran “sudo e2fsck -b 32768 /dev/sda8” , and the following output was returned:

`e2fsck 1.46.5 (30-Dec-2021)
hassos-data: recovering journal
e2fsck: unable to set superblock flags on hassos-data

hassos-data: ***** ファイルシステムは変更されました *****

hassos-data: ********** WARNING: Filesystem still has errors **********`

As a result, I was able to start the Home Assistant CLI despite some remaining errors.

14

I have the same problem on my HA, which is hosted on Proxmox.

HA is on the latest core 2024.8.1, tried above recommendations already but none of them working.

Regenerate the virtual machine again and again but the problem still there.

Proxmox firewall is Off. Internet working well, any recommendation?

Capture
Capture820×467 27.3 KB

15

Question to this … is it just to “rename” it … as hassos-data is the current partition… renaming it would make it work either… where to pull back the “old” hasso… sry, newby in that case

Let me rephrase my ask:

As far as I understand the above idea/workaround - we should rename the partition of the SSD volume to ensure that Homeassistant is starting again - right?.. Could anyone maybe give some more hints for people with less IT/technical skills in coding?.. Thanks

16

I encountered the same issue and tried all the suggestions on this forum. What stood out to me was that no one really provided detailed instructions on how to resolve it. This gave me confidence that the issue might be something I was doing wrong, rather than a common community problem.

After looking deeper, I confirmed everything was in working order, but I still couldn’t access Home Assistant via my local IP address. This was driving me crazy. Finally, I checked my router, found the correct IP address, entered it, and—boom!—everything worked. Now, I can log in to Home Assistant without any issues.

I hope this helps someone. In my case, the problem was with my router.

17

This worked for me :smiley: Thank you

18

I tried everything, different flashers and various distributions, and what helped was a simple replacement of the flash drive with another one.