supervisor
supervisor copied to clipboard
Restore after backup doesn't work
Describe the issue you are experiencing
After my SSD crashed I restored an old image and then used an updated backup Of this I chose the partial recovery, starting with the individual components first with success but once I moved to the core everything stopped, the restore procedure deleted almost all the contents of the config folder. I then solved it with a manual copy of the contents of the backup.
What type of installation are you running?
Home Assistant Supervised
Which operating system are you running on?
Debian
Steps to reproduce the issue
- From the backup function I selected partial restore
- Then I chose home assistant
...
Anything in the Supervisor logs that might be useful for us?
No
System Health information
System Information
version | core-2024.2.3 |
---|---|
installation_type | Home Assistant Supervised |
dev | false |
hassio | true |
docker | true |
user | root |
virtualenv | false |
python_version | 3.12.1 |
os_name | Linux |
os_version | 5.9.0-arm-64 |
arch | aarch64 |
timezone | Europe/Rome |
config_dir | /config |
Home Assistant Community Store
GitHub API | ok |
---|---|
GitHub Content | ok |
GitHub Web | ok |
GitHub API Calls Remaining | 5000 |
Installed Version | 1.34.0 |
Stage | running |
Available Repositories | 1398 |
Downloaded Repositories | 30 |
Home Assistant Cloud
logged_in | false |
---|---|
can_reach_cert_server | ok |
can_reach_cloud_auth | ok |
can_reach_cloud | ok |
Home Assistant Supervisor
host_os | Debian GNU/Linux 11 (bullseye) |
---|---|
update_channel | stable |
supervisor_version | supervisor-2024.02.0 |
agent_version | 1.4.1 |
docker_version | 23.0.0 |
disk_total | 28.6 GB |
disk_used | 20.8 GB |
healthy | true |
supported | failed to load: Unsupported |
supervisor_api | ok |
version_api | ok |
installed_addons | Mosquitto broker (6.4.0), Home Assistant Google Drive Backup (0.112.1), Duck DNS (1.15.0), TasmoAdmin (0.29.1), DHCP server (1.3.1), Tailscale with features (0.16.0.0), Cloudflared (5.1.4), Piper (1.4.0), Whisper (1.0.2), openWakeWord (1.8.2) |
Dashboards
dashboards | 3 |
---|---|
resources | 21 |
views | 33 |
mode | storage |
Recorder
oldest_recorder_run | 29 gennaio 2024 alle ore 22:33 |
---|---|
current_recorder_run | 23 febbraio 2024 alle ore 18:55 |
estimated_db_size | 1979.25 MiB |
database_engine | sqlite |
database_version | 3.44.2 |
Sonoff
version | 3.6.0 (8dd8af9) |
---|---|
cloud_online | 1 / 1 |
local_online | 1 / 1 |
Supervisor diagnostics
No response
Additional information
The only error I have had for years is related to the CGroup Version. Your system is not supported because you are using the wrong version of Docker CGroup. Use the link to find out the correct version and how to fix the problem.
This could be related to #4924.
Gist is, under some circumstances (if large files have been backed up) backups taken by Supervisor 2024.02.0 were not readable.
How old was the backup you've been trying to restore? Did your backup contain large files or folder?
I first restored an image from September 2023, then I updated the image and the components to the latest versions, finally I reloaded a backup made 16 hours earlier, but on this system that is now updated.
Ok, in that case it is most likely related to https://github.com/home-assistant/supervisor/issues/4924.
The issue is fixed, but currently on the beta channel for testing. I'll promote it to the stable channel today.
However, not sure if it helps in your case: You have to make a backup again before you'll be able to restore it :cry:
Well, I don't know, the case is very different from my problem and in any case my compressed file is not damaged
Hm, I see, so I connected dots here just based on timing, but this seems unrelated then.
but once I moved to the core everything stopped, the restore procedure deleted almost all the contents of the config folder.
So your issue was essentially that restoring the Core did not work correct?
To actually debug this we'd need at the very least some logs. Do you have Supervisor logs from when the restore happened? You can use ha host
to go further back in time, e.g. to get the last 100k lines of logs from Supervisor:
ha host logs --identifier hassio_supervisor -n 100000
Yes exactly. For the log I can try to extract it.
same thing here supervisor_2024-03-07T15-44-47.671Z.log
Регистратор: homeassistant.setup Источник: setup.py:266 Первое сообщение: 18:45:12 (1 сообщений) Последнее сообщение: 18:45:12
Setup failed for custom integration 'tuya_local': Requirements for tuya_local not found: ['tinytuya==1.13.1'].
Регистратор: homeassistant.components.hassio.handler Источник: components/hassio/handler.py:593 интеграция: Home Assistant Supervisor (документация, проблемы) Первое сообщение: 20:53:53 (1 сообщений) Последнее сообщение: 20:53:53
/refresh_updates return code 400
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.