Hi! My homeassistant running on a Pi4 stopped working. I connected it to a monitor and I see that it is trying to boot but then reboots (and it’s a never ending cycle)
The “failed” part I see (and it is quite fast) is:
Failed to start docker application container engine
Failed dependency for HassOS supervisor
Failed dependency for drophear (?) SSH deamond!
I included the photo of the last boot screen
I’m kind of lost here… what should I do?
Thank you!
Are you running the Pi from an SD-card?
(You should not do that and it’s most likely corrupt now. Better go for an SSD connected to USB.).
Did you make a backup and download that from the Pi before it crashed?
Put the SD-card into an SD-cardreader, hook it up to a Linux box and check the filesystems on the card.
hello
follow andreas advices and
take a look here please
Home Assistant Poor Esperience - Home Assistant OS - Home Assistant Community (home-assistant.io)
then come back , we will try to help you.
Thank you for your suggestions.
I have a laptop running Debian (that I once thought to use with Home assistant).
When I put the SD card on the Debian, I can see all the files (except “docker” for which looks like I need a password).
I took the opportunity to copy the backups folder and the *.yaml files… just in case.
I’m not sure, however, what I should do to try to have the SD card running again…
I’m sure I’m being very basic here… sorry for that … I did study Unix in school but that was almost 30 years ago!
The log file is 24GB… that’s probably causing this (?). Can I just delete the file?
Normaly it should be safe, to delete a logfile, i don’t know here in HA, but it’s safe to delete the DB-file in an offline HA, so i think it would be safe, you could “move it” if possible, then you have the giant log-file to “explore” if you get bored some day 
… which log-file is it ?
edit: if it’s any of the " home-assistant.log* " it’s safe, and yes, a very likely cause, dunno how long you had your HA running, before it died, but while u have it down, check your /backup, do a “manual” cleaning there also … not that you need it immediately if you truncate/delete the log
Copy the logfile as a backup and then truncate it to zero:
cp logfile logfile-backup
cp /dev/null logfile
(That way the logfile keeps owner and permissions)
Yes, but move mv from SD-Card, as it could be that it’s “chocked” , i don’t know how big card/installation he have, but 23GB logfile … lot of entries, most be some huge activity going on, in the system
yes, better be safe than sorry … but as with the DB-file, i think the logfiles is created, if not exist, can’t say for sure, my memory is very short 
Thank you all! It’s working again!
I will move the installation to a small SSD, as the idea of reconfiguring looks ‘more expensive’ than a disk! 
