Home assistant on RPi suddenly stopped autostarting..?

I have no clue why, but HA doesn’t start anymore. In the syslogs I found this:

Mar  5 22:06:41 hassbian systemd[713]: [email protected]: Failed at step EXEC spawning /srv/homeassistant/bin/hass: No such file or directory
Mar  5 22:06:41 hassbian systemd[1]: [email protected]: Main process exited, code=exited, status=203/EXEC
Mar  5 22:06:41 hassbian systemd[1]: [email protected]: Unit entered failed state.
Mar  5 22:06:41 hassbian systemd[1]: [email protected]: Failed with result 'exit-code'.

It’s correct, there is no /srv/homeassistant/bin/hass only python in this folder.

$ sudo systemctl status -a [email protected]

[email protected] - Home Assistant for homeassistant
   Loaded: loaded (/etc/systemd/system/[email protected]; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2018-03-05 21:51:15 UTC; 14min ago
  Process: 655 ExecStart=/srv/homeassistant/bin/hass (code=exited, status=203/EXEC)
 Main PID: 655 (code=exited, status=203/EXEC)

I find it easier to reflash the card and start over, since I have my config files saved. However before this happened, it seemed to have problems shutting down, taking very long time or never shutting down.

Also when I restarted the server, it had problems starting again. I managed to start it a shile back, and fiddled with systemctl, but now it seems the core files somehow are missing.

So I’d like to know what I could have done to cause this, so I don’t do it again.

Thanks :slight_smile:

It isn’t uncommon to have the SD card corrupted.
You can try a
fsck -n
from the command line to see if the disk has errors. It won’t fix anything but it will tell you if there are problems.
Have you checked to see if the hass file exists? You could do a
find / -name hass
from the command line.

Thanks, I’m trying a fresh install and hopefully it will not break again :slight_smile: