Hi all,
Have been playing around with Home Assistant for several years now, great platform and happy to made the switch from Domoticz.
Since short while (few days) my backup (to Synology NAS folder, but also the SSD which the Rpi3 runs HA on) doesn’t work anymore.
I tried several things, first looked in DSM to some kind of (time-based-)permissions etc, but could’t find anything. When implementing NAS backup location last week it performed successful full backup, size almost 500Mb.
So to narrow the search I deleted NAS backup folder (as backup location in HA, so network storage folder in storage settings HA), to force backup on SSD, but I still get the same errors message when trying to create a manual backup. this makes me worried… so it seems something is wrong in HA instead of Synology NAS connection and or permissions.
When I search on the error code in the logs, I find underneath log.
And looking at those jobs codes I end up in the same log message.
Am I looking at the wrong place?
Anyone has any idea why I can’t create new backups?
Logger: homeassistant.components.hassio
Bron: components/hassio/websocket_api.py:135
integratie: Home Assistant Supervisor (documentatie, problemen)
Eerst voorgekomen: 12:36:06 (7 gebeurtenissen)
Laatst gelogd: 12:55:38
Failed to to call /backups/new/full - An error occurred while making backup, check job '43d57de44cc9458a8fe1301ba88bdc37' or supervisor logs for details
Failed to to call /backups/new/full - An error occurred while making backup, check job '7c5d0c8b04854a349613bb1552f13278' or supervisor logs for details
Failed to to call /backups/new/full - An error occurred while making backup, check job '1ea4eb777aa04088adef0c02248c9eef' or supervisor logs for details
Failed to to call /backups/new/full - An error occurred while making backup, check job '4abfc65032704cdca0cd697961b86da6' or supervisor logs for details
Failed to to call /backups/new/full - An error occurred while making backup, check job '899b5fee8a4b4169bfc848b653739e54' or supervisor logs for details
Edit: could it be the SSD itself?