So my supervisor tab tells me I’m running version 239 and that there is an upgrade to 235… what the heck?
Perfectly normal when a release has been pulled. A search should find a number of previous threads on the topic.
Ah thanks, I was not aware that this is apparently perfectly normal so I never searched for what seemed very odd.
Just to be sure… this is all normal too ?
and these lines in the log:
20-09-01 09:02:46 INFO (MainThread) [supervisor.ingress] Load 0 ingress session
20-09-01 09:02:47 ERROR (SyncWorker_1) [supervisor.docker] Corrupt docker overlayfs detect: 500 Server Error: Internal Server Error ("readlink /mnt/data/docker/overlay2: invalid argument")
20-09-01 09:02:47 INFO (MainThread) [__main__] Run Supervisor
20-09-01 09:02:47 INFO (MainThread) [supervisor.api] Start API on 172.30.32.2
20-09-01 09:02:47 CRITICAL (MainThread) [supervisor.core] System running in a unsupported environment!
20-09-01 09:02:47 CRITICAL (MainThread) [supervisor.core] System running in a unhealthy state and need manual intervention!
20-09-01 09:02:47 INFO (MainThread) [supervisor.hassos] Rauc: A - marked slot kernel.0 as good
20-09-01 09:02:47 WARNING (MainThread) [supervisor.core] Ignore Supervisor updates!
and the fact that when trying to update it says this:
I’d say “not normal” 
But then I don’t run Supervised 
some more not normal (it seems) messages
20-09-01 11:17:40 ERROR (SyncWorker_0) [supervisor.docker.interface] Can't install homeassistant/armv7-hassio-supervisor:235 -> 500 Server Error: Internal Server Error ("Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:38400->[::1]:53: read: connection refused").
20-09-01 11:17:40 ERROR (MainThread) [supervisor.supervisor] Update of Supervisor failed!
I have the same one popping up in the logs now:
CRITICAL (MainThread) [supervisor.core] System running in a unhealthy state and need manual intervention!
t sounds alarming. Hope it will keep it together 
I was able to fix all problems by running:
ha su repair
in a terminal window.
1 Like
Where did you type this command? In the console window for the Supervisor docker container, the homeassistant container or on the host os terminal?
Ah. I was not using a docker install but a hassos one. However I restored settings from a previous, docker based install. This probably caused the problem in the first place. So I ran the command in througj the SSH add-on.
I see.
I am running the supervisor docker container on an unraid server. I was able to run “ha su repair” through the terminal & ssh plugin, but am still getting the same error message after restarting the containers.
I’m afraid I can’t help you any further. I’d love to run a docker based install as well but ran into problems (like this one for instance). It’s a shame docker gets so little love and/or attention from the developers…
I am having a similar issue:
Under Configuration > Logs I get:
Error saving events: (sqlite3.DatabaseError) database disk image is malformed [SQL: INSERT INTO events (event_type, event_data, origin, time_fired, created, context_id, context_user_id, context_parent_id) VALUES (?, ?, ?, ?, ?, ?, ?, ?)] [parameters: ('call_service', '{"domain": "system_log", "service": "clear", "service_data": {}}', 'LOCAL', '2020-11-23 16:31:13.471800', '2020-11-23 16:31:13.471800', 'f7ce5fdd7bee1e27850595d87f3999b8', 'a30540d186374be9b553275a2b98d371', None)] (Background on this error at: http://sqlalche.me/e/13/4xp6)
5:31:14 PM – Recorder (ERROR)
Error executing query: (sqlite3.DatabaseError) database disk image is malformed [SQL: INSERT INTO events (event_type, event_data, origin, time_fired, created, context_id, context_user_id, context_parent_id) VALUES (?, ?, ?, ?, ?, ?, ?, ?)] [parameters: ('call_service', '{"domain": "system_log", "service": "clear", "service_data": {}}', 'LOCAL', '2020-11-23 16:31:13.471800', '2020-11-23 16:31:13.471800', 'f7ce5fdd7bee1e27850595d87f3999b8', 'a30540d186374be9b553275a2b98d371', None)] (Background on this error at: http://sqlalche.me/e/13/4xp6)
5:31:14 PM – Recorder (ERROR)
I did try the fix proposed above in the CLI accessed by ssh:
~ $ ha su repair
Processing... Done.
Command completed successfully.
Then, rebooted homeassistant, but still the problem remains.
Any idea?
I have cleared my database home-assistant_v2.db as well, and everything gets correctly recreated on the new database.