#HomeAssistant OS going in to emergency mode following power loss

1 messages · Page 1 of 1 (latest)

crimson verge
#

I had an electrician doing some works recently and the power was cycle'd on/off a few times. It seems that HAOS (running x86/64 directly on a Beelink mini PC) had gotten itself stuck at the boot loader with the following message:

Welcome to emergency mode! After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to
try again to boot into default mode.
(or press Control-D to continue):

I just stuck a monitor/KB on it and did control-D, completed a proper shutdown the CLI and rebooted it and it booted fine again. This is obviously a bit of a pain in the ass. Is there any way to default skip past this since the box is headless and if I'm not at home following a powercut, it leaves my other half slightly fubar...

gritty tartan
#

That said I hope you have a back-up.

crimson verge
#

I do (we've alll learned that painful lesson I'm sure :P)

#

and it's booted and working fine, I'd just like to try and auto-skip past this at the OS level in the future

coral harbor
#

Please video record the boot process up to that point. Also check systemctl status docker hassio-supervisor.

crimson verge
#

is there a way to break out of the HA shell, currently says systemctl isn't found but suspect it's because SSH drops me in to a HA menu shell

coral harbor
#

Just enter login.

crimson verge
#

I did, dropped in with hassio and pwd and the shell I'm in doesn't see systemctl

coral harbor
#

Sounds like you used the SSH addon. Use the real OS CLI via keyboard and monitor.