-
-
Notifications
You must be signed in to change notification settings - Fork 180
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Bug #1045
Comments
This is most likely docker corruption. Docker is a virtualization system that Home Assistant and addons run in. There are some known issues with how Home Assistant uses it, if updating an addon or Home Assistant is suddenly interrupted (eg a power or disk failure) then docker's cache of files locally can become corrupted. If you want more detail, this thread is where we first identified the issue. AFAIK the home assistant team has no plan to fix it and there isn't anything I can do about it form the addon side of things. In some cases it can be fixed by installing the SSH addon and running the command The easiest way to fix this is to create a new backup (through Home Assistant) reinstall Home Assistant and restore the backup. |
Description:
Addon version:
0.111.1
Home Assistant Version:
2024.5.4
Supervisor Version:
2024.05.1
Supervisor Channel:
stable
Hassos Version:
12.3
Docker Version:
25.0.5
Architecture:
aarch64
Machine:
raspberrypi3-64
Date:
2024-05-22T08:17:56.143874+00:00
Timezone:
Africa/Johannesburg
Failure Time:
Never
Last Good Sync:
2024-05-22T08:17:43.129853+00:00
Next Sync:
2024-05-22T10:19:36.018173+00:00
Next Backup:
2024-05-22T23:00:00+00:00
Next Cache Warm:
2024-05-22T10:07:47.122112+00:00
Time Offset:
0.0
Exception:
Backups:
Config:
Addon Logs:
Supervisor Logs:
Home Assistant Core Logs:
The text was updated successfully, but these errors were encountered: