HAOS on laptop suddenly stopped working, after reboot I get "CLI Not Starting"

Installation Home Assistant OS
,
1

Hi:

I’ve had home assistant running fine for the last few months on an old acer notebook. Sometime in the last few days it stopped responding.
I just looked at the local display and it looked normal, but I could not type in the CLI.
I rebooted, and it responded with “Home Assistant CLI Not Starting! Jump into emergency console …”
rebooting returns the same result.
I can access home assistant observer at http://homeassistant.local:4357/ and it displays the following log. I think this happened after the most recent update to HAOS, but not certain. I always do on-machine backups before updating, but I do not have a copy of the very latest offline.
How can I recover? I can type in the emergency console:

Home Assistant observer
Supervisor:	Disconnected
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/udev.sh
cont-init: info: /etc/cont-init.d/udev.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun supervisor (no readiness notification)
services-up: info: copying legacy longrun watchdog (no readiness notification)
s6-supervise watchdog: warning: unable to spawn ./run (waiting 60 seconds): Exec format error
s6-supervise supervisor: warning: unable to spawn ./run (waiting 60 seconds): Exec format error
s6-supervise watchdog: warning: unable to spawn ./run (waiting 60 seconds): Exec format error
s6-supervise supervisor: warning: unable to spawn ./run (waiting 60 seconds): Exec format error
s6-supervise supervisor: warning: unable to spawn ./run (waiting 60 seconds): Exec format error
s6-supervise watchdog: warning: unable to spawn ./run (waiting 60 seconds): Exec format error
s6-supervise supervisor: warning: unable to spawn ./run (waiting 60 seconds): Exec format error
s6-supervise watchdog: warning: unable to spawn ./run (waiting 60 seconds): Exec format error
s6-supervise supervisor: warning: unable to spawn ./run (waiting 60 seconds): Exec format error
s6-supervise watchdog: warning: unable to spawn ./run (waiting 60 seconds): Exec format error
s6-supervise supervisor: warning: unable to spawn ./run (waiting 60 seconds): Exec format error
s6-supervise watchdog: warning: unable to spawn ./run (waiting 60 seconds): Exec format error
s6-supervise supervisor: warning: unable to spawn ./run (waiting 60 seconds): Exec format error
s6-supervise watchdog: warning: unable to spawn ./run (waiting 60 seconds): Exec format error
s6-supervise supervisor: warning: unable to spawn ./run (waiting 60 seconds): Exec format error
s6-supervise watchdog: warning: unable to spawn ./run (waiting 60 seconds): Exec format error
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/udev.sh
cont-init: info: /etc/cont-init.d/udev.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun supervisor (no readiness notification)
services-up: info: copying legacy longrun watchdog (no readiness notification)
s6-supervise supervisor: warning: unable to spawn ./run (waiting 60 seconds): Exec format error
s6-supervise watchdog: warning: unable to spawn ./run (waiting 60 seconds): Exec format error
s6-supervise watchdog: warning: unable to spawn ./run (waiting 60 seconds): Exec format error
s6-supervise supervisor: warning: unable to spawn ./run (waiting 60 seconds): Exec format error
s6-supervise watchdog: warning: unable to spawn ./run (waiting 60 seconds): Exec format error
s6-supervise supervisor: warning: unable to spawn ./run (waiting 60 seconds): Exec format error
s6-supervise watchdog: warning: unable to spawn ./run (waiting 60 seconds): Exec format error
s6-supervise supervisor: warning: unable to spawn ./run (waiting 60 seconds): Exec format error
s6-supervise watchdog: warning: unable to spawn ./run (waiting 60 seconds): Exec format error
s6-supervise supervisor: warning: unable to spawn ./run (waiting 60 seconds): Exec format error
s6-supervise watchdog: warning: unable to spawn ./run (waiting 60 seconds): Exec format error
s6-supervise supervisor: warning: unable to spawn ./run (waiting 60 seconds): Exec format error
s6-supervise watchdog: warning: unable to spawn ./run (waiting 60 seconds): Exec format error
s6-supervise supervisor: warning: unable to spawn ./run (waiting 60 seconds): Exec format error
s6-s
2

Do you have any way to remove the drive from the acer and connect it to another PC? If so, you can boot a Live Debian ISO and try and retrieve your backups.

I believe the files from /mnt/data/supervisor/backup are the backups. I don’t use HAOS so if someone wants to correct me, please do!

Then you can upload the backup tar file on the on-boarding page of a new installation, simply choose “Restore from Backup” (see Onboarding Home Assistant - Home Assistant).

3

unfortunately I think this device uses onboard storage - no separate drive.

4

Silly question but did you try and type in, “login” once you were in the emergency console? And is it connected by wifi or ethernet?

5

Someone else had the same problem, and they said they were able to mount their drive by booting a vm on a USB. I’m not suggesting this route, but you could try and boot a Live Debian 12 ISO and see if you can mount your internal drive to gain access to it that way - then copy your folder/files on to a separate USB…

I know it’s not fixing your problem, but getting access to your backups is a good start at least.

6

have a backup from a few weeks ago, which is good enough. I’m going to try the reinstall route.

7

I did try login command, and it did not work, even after 30 min. I’m connected by wifi, which I know is working because I can reach observer.