Hassio was running slow after getting some zwave devices added to the network so I SSHd into the host and rebooted it. After the system booted back up, hassio never came back. I checked on docker the only way I know how, sudo docker ps -a and it didn’t list any containers at all. My host is running Ubuntu server 18, and I’ve got the version of docker installed that the system prompted me to install during setup.
Some more troubleshooting I’ve done since:
ran systemctl enable hassio-supervisor.service
ran the installer again (curl -sL https://raw.githubusercontent.com/home-assistant/hassio-build/master/install/hassio_install | bash -s)
ran sudo docker ps -a again, and the supervisor docker container was listed, but it wasn’t listed when running sudo docker ps.
waited 5-10 minutes, still nothing, rebooted host, still nothing.
I verified my /usr/share/hassio was still there and pulled a backup down, but I’m at a complete loss for what’s happening. I had a similar issue when I first installed hassion on this machine, where it would get lost on every reboot, and I totally re-installed the host OS to get it back up then and eventually followed a supplementary guide to get it installed and sticking correctly.
out of desperation I tried apt-get update and apt-get upgrade and rebooted, still nothing.
I got some help from the Discord Server’s hassio channel, @onceler#7767, and he helped me identify that the supervisor is failing to load due to thinking that /usr/share/hassio is a read only file system.
which as far as I can understand can’t be the case since I was able to use zip -r backup /usr/share/hassio/ and for it to be able to successfully make the zip, and it’s all the same file system.
So then I tried to chmod 777 -R /usr/share/hassio and that didn’t solve anything either. Still the same issue.
I’d like to just wipe my OS and restore my latest backup and assume this is a fluke, but this isn’t the first time I’ve had this issue. When I first moved to this ubuntu host from the RP3B+ hassos to upgrade the horse power behind my hassio this would happen every reboot without fail until I followed a slightly modified set of instructions for installation. After doing a fresh OS install, then following that set of instructions (along with a small modification that I commented on the gidt with) everything was find for at least 2 weeks before this has happened.
Did you properly shut down Home Assistant, any add ons and the Hassio supervisor container before you gave the reboot command?
I have the same setup as you running and powered it down two nights ago to move my server. Plugged everything back in, hit power and in a minute or two things were up and running.
That I did not, I was under the impression that using the reboot command would do that for me, send stop commands to everything else. I’ve been rebooted this way numerous times without any trouble until now, if that’s what caused this I definitely won’t be doing that anymore >.>
How can I recover though? do I just have to re-install the host OS? is there nothing I can do to fix this?
