Tried my luck with discord, figured might as well try it here.
I recently (start of '25) reinstalled HA from scratch - it was long overdue. Went fine, and I was happy with the cleanup and bunch of new features.
Yesterday I had an abrupt power cycle and network connectivity issues at home, after which HA (HAOS) did not boot up.
I hooked it up to a screen, and started going through it. I encountered the horrid Waiting for Home Assistant CLI to be ready, followed by WARN ... jumping into emergency console.
There I inspected what I could, and noticed that a likely reason was a connectivity issue, since HA was set up with AdGuard, it was acting internally as a DNS, and since AdGuard was not available (HA did not start), there was no network. Fine - I used nmcli at first to modify the DNS address, which did not work, so I followed the network docs to reset the network configuration altogether.
Unfortunately that did not work either. I do have connectivity now, but still no HA.
At this point I started digging deeper, and noticed that docker ps -a reports the hassio_supervisor image has crashed, and other images were not started at all (I suppose the supervisor launches the rest of them?). The logs from the supervisor had an issue with sentry_sdk and ssl, and the last bit read (see attached photo too):
…/_ssl.cpython-313-aarch64-linux-musl.so: BIO_read: symbol not found
I’m not sure how to continue. At this point I at least have access to the HA files, and I thought about making a backup, full reinstall, and restoring, but I’m not even sure what would constitute a full backup manually (as I do not have the HA CLI).
I thought about that (and tried it yesterday), but I ran into two issues here -
The first is that I had to manually login to Docker, fine. I suppose HA updates these images using some credentials that are baked into the HAOS once it’s up and running.
The second is that the image repository was not found/accessible – or then I had a wrong docker pull instruction. I could post the error message in a bit once I get to the raspberry pi. I’m also somewhat afraid for my configuration and setup, so I want to be extra careful here.
Thanks @francisp!
Weird stuff - I still needed to login, but I was now able to pull the latest image.
It still crashes on the same error though unfortunately. I’ll give it a quick reboot just to verify things haven’t changed in the meantime.
Wow, uh, I guess the pull worked after all and it was, for some reason, unavailable yesterday.
Now the Supervisor boots and the system works, but of course, my network settings are gone and f’d, so I can’t access the UI (since I’m using Let’sEncrypt, it’s not available on the local IP address).
Any last thoughts on this? Could I restore some of the network settings via the HA CLI?
I set it up again, but still no UI accessibility, not local nor remote.
So I went ahead and ran ha core check – only ot get the same SSL-related error (this time from jwt package).
So something is still fishy, I’m not sure what’s going on. Maybe another docker image that needs updating?
Ironically (?), the CLI is up and running now. What fails is the homeassistant docker image itself (ghcr.io/home-assistant/raspberrypi4-64-homeassistant:latest). I pulled the latest here as well, but not change.
It seems like there’s no openSSL on that system (not sure if that’s expected or not).
ha backup new --help
This command can be used to trigger the creation of a new Home Assistant
backup.
Usage:
ha backups new [flags]
Aliases:
new, create, backup
Examples:
ha backups new
ha backups new --addons core_ssh --addons core_mosquitto
ha backups new --folders homeassistant
ha backups new --uncompressed
Flags:
-a, --addons stringArray addons to backup, triggers a partial backup
-f, --folders stringArray folders to backup, triggers a partial backup
-h, --help help for new
--homeassistant-exclude-database[=false] Exclude the Home Assistant database file from backup
-l, --location string where to put backup file (backup mount or local)
--name string Name of the backup
--password string Password
--uncompressed[=false] Use Uncompressed archives
Global Flags:
--api-token string Home Assistant Supervisor API token
--config string Optional config file (default is $HOME/.homeassistant.yaml)
--endpoint string Endpoint for Home Assistant Supervisor (default is 'supervisor')
--log-level string Log level (defaults to Warn)
--no-progress Disable the progress spinner
--raw-json Output raw JSON from the API
Creating a backup is anyway a good idea, so I’ll do that right away.
Before I go down the apocalyptic route, is there anything else I could try?
I know HAOS also regularly (occasionally? when?) does a backup to a similar partition (ha os’s boot-slot). Is that worth a shot here at all?
I tried that (was simply ha os boot-slot other) - but it ran into the same issue. I assume it’s just a different HAOS, but the underlying issue persisted.
So I made a backup (tar file) and copied it to a USB stick.
Do I understand correctly, that now the way forward would be to reinstall from scratch, and once HA is up, I can restore from the UI by uploading this tar file? Are there any additional backups I should do, if I just ran ha backups new, or does this cover addons, all configurations, lovelace, etc?
Thanks again for everything @francisp, and mostly for your patience and willingness to help I’d give you a cookie if I could!
