Hello friends, I need your help. HA constantly falls back to an old save after restarting and everything I changed from the save up to that point in the dashboard or added integrations are gone after the restart. The SSD is new and has 265GB of storage. HA runs on a Mini PC with 265GB memory and 16GB Ram with HAOS
Anything in the logs?
It doesn’t say anything there as to what could be the problem
If there is nothing in the logs, It sounds like your file system may be in read-only mode. This can happen if the disk is full or the file system is corrupt. You may want to take a backup, reformat the disk or use a new disk, reinstall Home Assistant, then restore the backup.
I have already done all of that. I bought a new SSD with 256 GB storage and loaded it onto the new SSD via backup but the problem is still there
Settings → System → Repairs
Click on the three dots in the upper right corner and click on System Information
Provide a copy of that information here.
System Information
| version | core-2024.12.4 |
|---|---|
| installation_type | Home Assistant OS |
| dev | false |
| hassio | true |
| docker | true |
| user | root |
| virtualenv | false |
| python_version | 3.13.0 |
| os_name | Linux |
| os_version | 6.6.66-haos |
| arch | x86_64 |
| timezone | Europe/Berlin |
| config_dir | /config |
Home Assistant Community Store
| GitHub API | ok |
|---|---|
| GitHub Content | ok |
| GitHub Web | ok |
| HACS Data | ok |
| GitHub API Calls Remaining | 5000 |
| Installed Version | 2.0.1 |
| Stage | running |
| Available Repositories | 1508 |
| Downloaded Repositories | 90 |
Home Assistant Cloud
| logged_in | true |
|---|---|
| subscription_expiration | 14. August 2025 um 02:00 |
| relayer_connected | true |
| relayer_region | eu-central-1 |
| remote_enabled | true |
| remote_connected | true |
| alexa_enabled | false |
| google_enabled | false |
| cloud_ice_servers_enabled | true |
| remote_server | eu-central-1-17.ui.nabu.casa |
| certificate_status | ready |
| instance_id | 11dcb4763a3a418e9186c539d98b6d4a |
| can_reach_cert_server | ok |
| can_reach_cloud_auth | ok |
| can_reach_cloud | ok |
Home Assistant Supervisor
| host_os | Home Assistant OS 14.1 |
|---|---|
| update_channel | stable |
| supervisor_version | supervisor-2024.12.0 |
| agent_version | 1.6.0 |
| docker_version | 27.2.0 |
| disk_total | 3666.9 GB |
| disk_used | 10.6 GB |
| healthy | true |
| supported | true |
| host_connectivity | true |
| supervisor_connectivity | true |
| ntp_synchronized | true |
| virtualization | |
| board | generic-x86-64 |
| supervisor_api | ok |
| version_api | ok |
| installed_addons | Advanced SSH & Web Terminal (19.0.0), File editor (5.8.0), Spotify Connect (0.13.0), Govee to MQTT Bridge (2024.07.13-82ddc6e9), Mosquitto broker (6.4.1), PS5 MQTT (1.4.0), Home Assistant Google Drive Backup (0.112.1), AirCast (4.2.3), Music Assistant Server (2.3.3), Silicon Labs Multiprotocol (2.4.5), ESPHome Device Builder (2024.12.1), Matter Server (6.6.1), Zigbee2MQTT (1.42.0-2) |
Dashboards
| dashboards | 6 |
|---|---|
| resources | 68 |
| views | 50 |
| mode | storage |
Recorder
| oldest_recorder_run | 7. Dezember 2024 um 11:52 |
|---|---|
| current_recorder_run | 20. Dezember 2024 um 02:00 |
| estimated_db_size | 203.01 MiB |
| database_engine | sqlite |
| database_version | 3.45.3 |
Spotify
| api_endpoint_reachable | ok |
|---|
Just to confirm, did this problem exist before using the new SSD?
Have you examined each of these files?
- Home-assistant.log
- home-assistant.log.1
- Home-assistant.log.fault
Yes, the problem was already before the new SSD. I used a new SSD because I assumed that my old SSD might
is defective. There is nothing in the log files that would explain this, only that some integrations are out of date, but it is not the integrations that are causing problems
I noticed you have 6 dashboards. Is the problem occurring on all 6 dashboards?
yes because after the restart HA deletes all added integrations, changes in the dashboard, calendar etc. that I have added or changed since the save. I have to add and change everything manually after each restart
No the system does not start in safe mode. it starts in normal mode
Recovery mode is different than safe mode. I asked because recovery mode typically exhibits the type of behavior you are describing: “it will still continue to start using parts of the configuration from the last time Home Assistant did start.”
Can I somehow find out if it starts in this mode?
There should be a notification at the top of the page.
Have you updated all your HACS integrations, rebooted your host computer, then checked to see if the issue persists?