Closed rct closed 7 months ago
Make sure you have read the issue guidelines and that you filled out the entire template.
If you have an issue identical to this, do not add comments like "same here", "i have this too", instead add a :+1: reaction to the issue description. Thanks! :+1:
It wouldd not matter where it was stored. Once your storage media starts to fail like that you should look at alternatives.
System Health details
System Information
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 | 853 Downloaded Repositories | 1AccuWeather
can_reach_server | ok -- | -- remaining_requests | 47Home Assistant Cloud
logged_in | true -- | -- subscription_expiration | May 24, 2024 at 8:00 PM relayer_connected | true relayer_region | us-east-1 remote_enabled | true remote_connected | true alexa_enabled | true google_enabled | true remote_server | us-east-1-3.ui.nabu.casa certificate_status | ready instance_id | ab6ffa1d7b754c2bb359ce96876a25e1 can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okHome Assistant Supervisor
host_os | Home Assistant OS 11.1 -- | -- update_channel | stable supervisor_version | supervisor-2024.01.1 agent_version | 1.6.0 docker_version | 24.0.6 disk_total | 63.0 GB disk_used | 47.9 GB healthy | true supported | true board | ova supervisor_api | ok version_api | ok installed_addons | Advanced SSH & Web Terminal (17.0.4), Grafana (9.1.3), Mosquitto broker (6.4.0), Plex Media Server (3.3.2), Z-Wave JS UI (3.3.1), Zigbee2MQTT (1.35.2-1), UniFi Controller (0.18.1), Studio Code Server (5.15.0), eufy-security-ws (1.7.1)Dashboards
dashboards | 7 -- | -- resources | 3 views | 41 mode | storageRecorder
oldest_recorder_run | February 6, 2024 at 5:56 PM -- | -- current_recorder_run | February 11, 2024 at 8:01 PM estimated_db_size | 1992.78 MiB database_engine | sqlite database_version | 3.41.2Checklist
Describe the issue
It appears If
hacs.repositories
becomes corrupted, HACS loses track of what has been installed. Trying to figure out what was installed and get it reinstalled can be challenging.While the source of the corruption is most likely accidental power loss and not the fault of HACS, it would be a feature if it was easier to recover from this event.
Looking at the corrupted
hacs.repositories
file. It was tracking 1,470 repos of which only 12 repos were installed. Data about the 12 installed repos changes less frequently than the list of available repos. If that data was stored separately, or at least there was a list of repos installed and the version details it would make the recovery process easier.Reproduction steps
.storage/hacs.repositories
to become corrupted, restart Home Assistanthacs.repositories.corrupt.timestamp
file in config/.storageversion_installed
key to try to piece together the previous state and figure out what repos to reinstall.storage/hacs.repositories
in some other location. Shut down Home Assistant, copy the file back into.storage
. Restart home assistant. ...Debug logs