Latest supervisor break updates and snapshots on synology dsm
See original GitHub issueDescribe the issue
Trying to update ha to 0.118.2 from 0.118.1, get error
20-11-23 10:15:34 WARNING (MainThread) [supervisor.jobs] 'HomeAssistantCore.update' blocked from execution, system is not healthy
also when trying to update addon
20-11-23 11:00:24 WARNING (MainThread) [supervisor.jobs] 'AddonManager.update' blocked from execution, system is not healthy
also snapshots are broken
20-11-23 11:12:41 WARNING (MainThread) [supervisor.jobs] 'SnapshotManager.do_snapshot_full' blocked from execution, system is not healthy
Steps to reproduce
I know that synology docker installation isn official supported, but it popular way to use home assistant May be there are some way to disable this health check to update? Or downgrade supervisor is nessesary?
Enviroment details
- Operating System:: Synology DSM
- Supervisor version:: 2020.11.2
- Home Assistant version: 0.118.1
- Docker version: 18.09.8, build bfed4f5 (latest on DSM so far)
Supervisor logs
Supervisor logs
Paste supervisor logs here
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:80 (16 by maintainers)
Top Results From Across the Web
Snapshots | Snapshot Replication - Synology Knowledge Center
Snapshots. This page allows you to take, remove, and edit snapshots, as well as to configure snapshot schedule and retention settings.
Read more >Release Notes for DSM | Synology Inc.
If you want to update to the latest version now, please go to Synology Download Center and manually update your DSM. This update...
Read more >Snapshot | DSM - Synology Knowledge Center
All snapshot versions within one hour since the taking of newest snapshot will be kept by default, for your convenience to find and...
Read more >Snapshots | Snapshot Replication - Synology Knowledge Center
This page allows you to take, remove, and edit snapshots, as well as to configure snapshot schedule and retention settings. Snapshots minimize disk...
Read more >Update | DSM - Synology Knowledge Center
Note: · Updating DSM does not affect the data on the Synology NAS. · After you update to a newer DSM version, you...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It works fine for me. See attached screenshot how it should look like. I restarted the supervisor container and now I am able to play with add-ons.
Sad to see this breaking change, too. Yes, Synology uses some old docker version, but it is the most recent version for all synology users out there. Can understand the intention to move forward, but am unhappy to see so many installations break…
The actual FIX is this post: https://github.com/home-assistant/supervisor/issues/2288#issuecomment-738158680
and how I implemented it here: https://github.com/home-assistant/supervisor/issues/2288#issuecomment-738182230
For posterity, I’m keeping this in case its needed by others in the future:
For those searching for a solution here who are NOT as technical (like me) and you’re using Ubuntu or other Linux Supervised Installs, here are detailed steps used to FIX (OK, BYPASS)this problem:
find your Home assistant install directory (“hassio”). It will look like the pic below. rt-click Open the dir AS ADMINISTRATOR
Create a new file there with all the other json files called jobs.json. or just duplicate one of the existing files and rename it
put this one line in that file:
{“ignore_conditions”: [“healthy”]}
save it
restart the Supervisor Docker container either in Portainer or reboot your system.
I Was successfully able to restore a Snapshot after doing this. All is now well in the Universe. I can now see my chickens are about to lay eggs on each other!
Jeff