Supervisor failed to start with error "exec /init: exec format error"

[DeminLi]

Describe the issue you are experiencing

I have run HA in RP4 for years but it is completely broken 6 days ago, it matched the time the supervior get upgraded. Seems the issue happened on version 2024.09.0 and above The error "hassio_superviosr: exec /init: exec format error" is shown on systemctl status docker.service, and can be reproduced when running docker run docker pull ghcr.io/home-assistant/aarch64-hassio-supervisor:2024.09.0

Manually pulling 2024.08.0 image can bypass the error, however, looks like I lost everything, now my HA is empty. I have backed up my sd files, so I can recover it all, no worries. Any suggestion about how to resolve the "exec format error" is welcome.

What type of installation are you running?

Home Assistant OS

Which operating system are you running on?

Home Assistant Operating System

Steps to reproduce the issue

1. restart my HA
2. check "systemctl status docker.service" ...

Anything in the Supervisor logs that might be useful for us?

N/A

System Health information

N/A

Supervisor diagnostics

N/A

Additional information

No response

[agners]

I have run HA in RP4 for years but it is completely broken 6 days ago, it matched the time the supervior get upgraded. Seems the issue happened on version 2024.09.0 and above

2024.09.0 did not got released to stable. So most likely this was the upgrade to 2024.09.1.

Manually pulling 2024.08.0 image can bypass the error, however, looks like I lost everything, now my HA is empty.

Sorry to hear that. :cry: Supervisor doesn't deal with /config much, so this is unlikely caused by Supervisor itself. I'd guess this is a hardware failure. Do you use a SD card? They are known to fail hard suddenly. Probably the Supervisor upgrade caused some extra writes to the SD, which pushed it over the edge :cry:

[DeminLi]

It is actually failed on 2024.09.1, but I found that it also failed on 2024.09.0, until I see it succeed on 2024.08.0. Yes, I am using sd card, and copying data to a new sd card doesn't resolve the issue. Is there any way to reset supervisor or downgrade it without erasing my data?

[agners]

If you have a full backup, you can try to clear the Docker data storage. It is a bit a hack, a full backup and start over is always recommended. Here are the details on that approach: https://community.home-assistant.io/t/help-home-assistant-cannot-start-after-forced-reboot-audio-layer-cannot-be-installed/724463/11?u=agners

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[vasekch]

I had the same issue on 2024.11.4 and here is how I make it work.

I tried mentioned docker run with older image 2024.11.2 and it was starting ok.

I've listed all exited containers using docker ps -a and removed all containers running from image ghcr.io/home-assistant/aarch64-hassio-supervisor using docker rm

I've removed broken image using docker image rm ghcr.io/home-assistant/aarch64-hassio-supervisor:2024.11.4 and docker image rm ghcr.io/home-assistant/aarch64-hassio-supervisor:latest

Then I restarted systemd service systemctl restart hassio-supervisor.service. It took a bit as it was repulling the latest image. But everything started with original data preserved and system correctly updated.