nice! ‘login’ worked for me, thank you!
Hey I had experienced the same issue in my raspberry pi 4.
Tried many methods including the login one but none helped.
The issue i noticed is that the docket containers aren’t starting by itself so we need to manually do that.
Steps i used.
1: type docker ps -a and check which docker containers are not up.
2: If many containers including the homeassistant container and supervisor container are exited start it manually.
3: Just type docker start hassio_suppervisor
4:Then type docker start homeassistant
5:Now type login and check weather both cli and supervisor is now active.
Note:
Sometime starting both manually will result in network error between homeassistant and supervisor.
In such cases type docker stop homeassistant and then type docker restart hassio_supervisor.
This will restart the supervisor and it should also automatically start the homeassistant again and this time the network error wont be there.
2 Likes
genius! I had 2 dockers that had failed to come up after a power outage. Thank you!
Really quite annoying this issue persists but they choose to close the issue on their GitHub. [WARN] Home Assistant CLI not starting! Jump into emergency console · Issue #1969 · home-assistant/operating-system · GitHub
while login works, it’s insane they haven’t fixed this bug that bricks peoples HA and have them potentially spend endless time, effort and stress if they don’t find this fix easily.
I am having this same problem with a fresh install of the VM image from
https://github.com/home-assistant/operating-system/releases/download/16.0/haos_ova-16.0.qcow2.xz
it will run for a day or a few days but after a reboot I get the message
[[WARN] Home Assistant CLI is not running! Jump into emergency console…
trying the login just eventually returns to the same place, and I have waited up to hours but it is still the same and return to the same “#” prompt. Using the docker command I can see that most of the containers have failed including the homeassistant one, while hassio_supervisor and observer are still running. The containers for the add-ons from the add-on page are also failed. The web interface is none existent so I can not see anything using that. Rebooting the VM also brings me back to the same “#” prompt.
Does anyone have any suggestions as to what might be causing this and any way to stop it occuring?
I wrote login and dann
coming the same error again
can you help me?