I’ve had Hassio running on a Pi 3 with SD card for many months without any major problems until a week or so ago. Hassio now fails to start and SSH access does not work. I’m unsure how to debug the problem.
As far as I can tell, Hassio is failing to start from HassOS. When I connect the Pi to a monitor and watch the boot sequence, I see an initial failure:
[FAILED] Failed to start Docker Container Application Engine
The boot process continues after that with a few more failures, until the Pi is eventually restarted auttomatically and the boot process starts again. This is an apparently infinite loop.
CTRL-C and CTRL-Z don’t interrupt the boot process, so I can’t use systemctl as advised after the failure. If I stop autoboot early on, I get dumped into a HassOS prompt, but I’m unsure if there’s anything I can do to debug from there.
Having the same issue as well today. I was simply restarted the Home Assistant after making a few changes and decided to reboot Hass.io. Now nothing I have a backup of my config files but not a recent snapshot.
I actually wasn’t trying to install an img. All I was doing was power cycling an existing installation. The existing installation stopped responding/working. My first attempt to get it to work was to power cycle. That’s when the boot failure became evident.
No, a clean install fixed the problem. Interesting that it’s the same symptom from an apparently different cause. I wonder it they’re still related somehow.
I am having the same issue. I am running HASSIO on a VM on Windows 10. My desktop lost power and on reboot the HASSIO install appears to be corrupted (only thing I can think that happened at this point, it was working fine before and after it started having this issue). I have a snapshot created but never found a good way to get it off the system, is it still possible and if so, does anyone know how to pull it off at this point?
I was running on a Pi. Fortunately, my snapshot files on the SD card survived. I was able to get to them by putting the SD in a Linux machine.
I’ve taken this opportunity to move my HASSIO set-up to a Docker container on an Ubuntu 18.04 system. I’m still learning about that set-up. However, I can access my Hassio files, including snapshots from the host system mapped to the directory /usr/share/hassio.
That may not help you find the files in Windows 10. But, maybe your Hassio files will be mapped to a Windows directory somewhere outside of the VM. Good luck.
BTW, I’ve now started using the Google Drive Sync add-on for Hassio snapshots in case this happens again. Works perfectly so far.
I wondered too but not competent at all… I was stuck with that failure as I couldn’t load any snapshot from there
As I did not find any solution, I looked over my SD card today. It turned out it was the problem…
My next step would be to make the installation more reliable. (Hassio was running for just 2 months, and I guess the more I will use Hassio, the less reliable it is going to be with this set up)
I have changed the sd card and it seems that everything is going well even much faster, although the other card after analyzing it did not have any error apparently
I have the same problem after a reboot I get the same problem. The last one I installed was grafana. Till the power got unplugged and reboot it happens for me. still don’t know how to switch the pi 3 off in a correct way. I am not sure it is with grafana. but it works first from the begining till it get a reboot it happens for me. The Pi3 keeps in a boot loop and restart the pi 3 every time now. Any idea what it is?
I have a backup of my config files but not a recent snapshot.
