Without any means to hitchhike your specific question/problem. But did you do an OS-update just before the reboot?
Running HA on a
- Raspberry Pi 4, 4GB
- SSD KINGSTON V400 120GB inside a
- ORICO USB-C 3.1 Gen 2 HDD Enclosure 2159C3-G2
All used to work seamlessly and without any hiccups with this installation method.
Just as a report about some problems I ran into after routinely checking for system updates which I do once a week:
sudo apt update && sudo apt upgrade -y && sudo apt autoremove –y
After the update-process has finished Home Assistant quit working.
So I did a couple of OS-restarts but that did not help. Debian itself was booting without problems and SSH-access to the CLI worked. Just HA didn’t start.
So I decided to redo the whole process as per the instructions here which finished without errors. Nevertheless, the initial Logon/Restore from Snapshot-prompt took ages to load but finally did. All well I thought and after a complete Restore of the final snapshot and some fine-tuning I initiated another system reboot.
Which brought me back to: Debian itself was booting without problems and SSH-access to the CLI worked. But HA didn’t start…
So I stopped Docker, deleted all images and Volumes and finally removed Docker itself to redo all clean.
However, similar to the first attempt I was able to Logon into HA after an extended loading time but after a system reboot all went back to square 1: HA did not load to the end.
Unfortunately I missed to record the relevant log-entries to the latter but it has something to do with resolving names (HA’s internal DNS-server is not starting).
Today I have read an article reporting about some (breaking) changes to Docker which just received an update from version 19.03 to version 20.10. This update already found its way into the Debian 10 repos and was also installed with the latest system update.
Especially the changes to the settings for the hostname and the ports caught my attention since this is now done automatically by Docker. Additionally Docker 20.10 is now supporting cgroup v2 instead of cgroup v1 which is managing CPU-load, memory, storage and networking in a different way.
I suspect there are some incompatibilities between HA Supervised on Raspi Pi with Debian 10 and Docker 20.x which renders this installation method hard to use for the time being.
Unfortunately I am not very familiar with the Docker-world an therefore sadly I am unable to look into this by myself.