operating-system

operating-system copied to clipboard

Describe the issue you are experiencing

After reboot of Home Assistant virtual machine running on VMware Workstation, I get the messages at the console:

Waiting for the Home Assistant CLI to be ready...
[WARN] Home Assistant CLI not starting! Jump into emergency console...

What operating system image do you use?

ova (for Virtual Machines)

What version of Home Assistant Operating System is installed?

8.1

Did you upgrade the Operating System.

No

Steps to reproduce the issue

1. Shutdown or reboot gracefully the Home Assistant virtual machine
2. Power it up
3. Get to the console of the Home Assistant virtual machine
4. In the console see the message:

Waiting for the Home Assistant CLI to be ready...
[WARN] Home Assistant CLI not starting! Jump into emergency console...

https://ibb.co/Qczsr1y

Anything in the Supervisor logs that might be useful for us?

Can't get into the user interface of Home Assistant.
https://ibb.co/D8gLztH

Anything in the Host logs that might be useful for us?

Can't get into the user interface of Home Assistant.
https://ibb.co/D8gLztH

System Health information

Can't get into the user interface of Home Assistant. https://ibb.co/D8gLztH

Additional information

No response

Hi buddy, I had the same problem, just enter "login" in the console and press enter, your problem will be solved. I found a solution in the comments of this post https://community.home-assistant.io/t/warn-home-assistant-cli-is-not-running-jump-into-emergency-console/303548/7

enter in the browser homeassistant.local:8123 or homeassistant.local:4375

Hi buddy, I had the same problem, just enter "login" in the console and press enter, your problem will be solved. I found a solution in the comments of this post https://community.home-assistant.io/t/warn-home-assistant-cli-is-not-running-jump-into-emergency-console/303548/7

It may be the solution, I can't test anymore as I followed the workaround described here https://github.com/home-assistant/operating-system/issues/1970

I have the same bug.Although I can login through the post http://homeassistant.local:8123 ,but don't know how to repair the issue. can u tell the next works.

Try to wait 20 minutes, if it won't shut down the virtual machine, start it again. If it doesn't work then try to change the IP address assigned to the machine from which you start the virtual machine and start it again. But it will definitely work on your local host as well.

I have similar issue. Had to reboot my VM running on virtualbox for system maintenance and home assistant did not come back up. dmesg shows segfaults.

Try to wait 20 minutes, if it won't shut down the virtual machine, start it again. If it doesn't work then try to change the IP address assigned to the machine from which you start the virtual machine and start it again. But it will definitely work on your local host as well.

I am afraid it doesn't make help, but thanks for your comment

I have the same bug.Although I can login through the post http://homeassistant.local:8123 ,but don't know how to repair the issue. can u tell the next works.

I have restored from backup, there was no other way to fix the issue

Hi buddy, I had the same problem, just enter "login" in the console and press enter, your problem will be solved. I found a solution in the comments of this post https://community.home-assistant.io/t/warn-home-assistant-cli-is-not-running-jump-into-emergency-console/303548/7

Thanks, this solved the issue for me!

i have the same issue，while i input "login"，then it doesn't worked, only reflash the screen again and show "[WARN] Home Assistant CLI not starting! Jump into emergency console" again. How can i fix this problem? my system was just break dowm when it's working fine. It's the auto update things?

i have the same issue，while i input "login"，then it doesn't worked, only reflash the screen again and show "[WARN] Home Assistant CLI not starting! Jump into emergency console" again. How can i fix this problem? my system was just break dowm when it's working fine. It's the auto update things?

Same problem when doing fresh install on Intel PC :( Login does not work, setting DNS does not work

There hasn't been any activity on this issue recently. To keep our backlog manageable we have to clean old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant OS version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Same problem. We lost power in Quebec for a while after an ice storm on the 5th of april and I noticed my HA install never came back online. None of the solutions suggested above work.

Is there any way to restore an HA backup from the emergency console ? I made a full backup (from within HA) recently because of another issue.

Typing login resets the screen and outputs same message: CLI not starting! Jump into emergency console

Typing the HA command outputs

Error response from daemon: Container [containerID] is not running

Hm, the power outage probably lead to a corrupted file system of some sort.

What is systemctl status docker saying?

Wrt Backup: The files are stored on the data partition (8th partition on the boot storage, unless you are using the data disk feature, then it is on that partition). You'll find the backups under supervisor/backup/.

here's the output from systemctl status docker

This is running in a vm. Mmm, iirc last time my install crashed it also had something to do with a JSON endpoint call to that address but that was after an update.

Issuing ip addr from the console shows an inet adapter in position 3 named hassio with the 172.30.32.1/23 ip mask, so i assume that's an internal virtual network used by HA

as for the backups, they are on the same vm disk image. ~~i assume i'd have to find a way to copy them elsewhere and reinstall them on a fresh HA install ? No other way to recover from the current state then ?~~

Edit: I ended up creating a new vm. Now i need to find a way to extract my backups from the old one. I can log in to it via the vm console and access the backup folder but i can't seem to find a way to enable ssh/sftp to transfer files out of it

Edit 2: I eventually managed to extract my backups by physically attaching a fat32 usb drive to the pc, connecting it to the old vm, manually creating a mount point folder in /mnt/overlay/ as everything else was read only and after mounting manually it in read/write, i could copy all the files from /mnt/data/supervisor/backup. I then did the same in reverse on the new vm by copying all the extracted files to the new vm /mnt/data/supervisor/backup folder.

With that done i could restore my last full backup from the UI and everything is back in working order.

There hasn't been any activity on this issue recently. To keep our backlog manageable we have to clean old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant OS version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

I have this issue now and I am disappointed but not surprised to find this issue is closed. HA developers appear to focus on new features instead of stability and it is pushing me away from the platform. The time I save in automation is lost in dealing with these kind of inexplicable, undebuggable issues.

I also encountered the same problem. I installed it in Virtualbox version 6.1.32. Because the previous update caused system damage, I reinstalled it once, but it kept prompting this problem, even if I log in based on other people's input or modify the DNS, it doesn't work. This problem still occurs