Hi all, have been running HA on an optiplex using VM for about 2 years without issues. Rebooted PC this week and after starting HA in VM, HA does not start anymore and I get the following error warning:" [WARN] Home Assistant CLI not starting! Jump into emergency console…"
Some people on the forum suggested typing login, but after some time I just return to the same warning. I can reach http://homeassistant.local:4357/ which gives me the info below.
Any advice on how to resolve this?
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 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
This problem (some systems have when updating from 14.2 to 15) sounds like what you’re getting. Is that right?
This did not resolve it regrettably, if I boot via the other drive I get the same error: [WARN] Home Assistant CLI not starting! Jump into emergency console… " When I enter the "ha os update --version 14.1’’ as suggeted it says container is not running.