Having the same issue for a few weeks now.
Backup does not actually fail however… it does happen in the background (can bee seen that it is working because CPU is working quite hard (even after this failure message). and in the end after a few hours of it working in the background snapshot will appear and will be downloadable
in the beginning i thought it was because of my InfluxDB that was huge. I deleted InfluxDB because it had a lot of unnecessary data anyways and recreated a new empty one with just a few includes (instead of including everything) But still i am getting this error message when backing up
Also when checking the home-assitant.log i have those two lines only
And when checking the Supervisor logs everything looks OK. the error message happens when actually doing the backup for mariadb. dont know if it is related. FYI maria db has only a retention of 7 days so this DB is not that huge
I’m adding to this conversation although the reason shown for not being able to create a snapshot is due to “system is in startup state”.
Today I noticed that there was a Core update available, core-2021.3.4 -> core-2021.4.3. I went to create a snapshot before updating and am seeing the same msg Creating a snapshot is not possible right now because the system is in startup state..
I’ve read through the other posts here and I find zero reasons or resolutions. I don’t want or mean to be negative, truely, but dam?t, every time I turn around something borks with HA. While I love the concept, I keep running into issues that require too much fing time to dig into and not find any solution, like this one. I had made no changes to my system. All I want to do is update and move on with my day. I don’t want to spend the rest of my day with what should not be an issue.
Actions:
Restart core - didn’t resolve
Reload Supervisor - didn’t resolve
Restart Supervisor - didn’t resolve
Restart Host - didn’t resolve
Every time I click Create snapshot, the log is appended with ‘Found 1 snapshot files’. There is no other information in the log to indicate the reason/cause:
21-04-10 18:09:55 INFO (MainThread) [supervisor.snapshots] Found 1 snapshot files
21-04-10 18:10:21 INFO (MainThread) [supervisor.snapshots] Found 1 snapshot files
21-04-10 18:11:39 INFO (MainThread) [supervisor.snapshots] Found 1 snapshot files
21-04-10 18:15:25 INFO (MainThread) [supervisor.snapshots] Found 1 snapshot files
21-04-10 18:24:03 INFO (MainThread) [supervisor.snapshots] Found 1 snapshot files
21-04-10 18:26:45 INFO (MainThread) [supervisor.snapshots] Found 1 snapshot files
21-04-10 18:26:54 INFO (MainThread) [supervisor.snapshots] Found 1 snapshot files
Given that I’ve read a number of posts related to this issue w/ zero resolution, and wanting to move forward, I wanted to see if an upgrade would solve the problem. It did. Although as a software dev myself, it shouldn’t have. That being, what broke it in the first place where it worked with core-2021.3.4 and then arbitrarily stopped working?
Going to the Supervisor -> Snapshot tab and choosing Create continues to fail throwing the error msg. So I made a backup of the entire hassio-supervisor directory and proceeded to do an upgrade from core-2021.3.4 -> core-2021.4.3. I was prompted to create a snapshot before the upgrade. To my surprise, Instead of seeing the message that a snapshot can’t be created because the system is in startup state, a snapshot was created and the upgrade was successful (in that it didn’t error or crash, further testing before I sign off on the upgrade). It appears to me to clearly be an internal code issue where the system gets stuck in whatever state it thinks it’s in and thereby fails to be able to create a snapshot manually.
I just posted a response on another similar topic, but the forum doesn’t allow similar posts, so I will link it below. The solution that worked for me was to fix an error for deprecated code that does not show up on default logs. The other error that I had was an integration for Plex, that I was not using and had not setup, so I deleted it.
Same here. I am on core-2021.6.6. Either manually snapshot or auto does not work. Was able to delete some of the older snapshots, but that did not solve the issue.
Can confirm. Had same issue tired to make snapshot multiple times with restarting and debugging issues from log, but after 2 h with total size of snapshot 5,5 GB there is snapshot created. It seems stuck because it says that system is freeze and log in supervisor is continuing to give new entries beside those about snapshot.
So another solution to this could be patience.
I’ve never had this problem before until today. I’m thinking this may be because earlier today I installed Frigate and I’m wondering if the Backup is trying to copy some media clips, or something related to Frigate.
I am having the same issue. Fresh new install and getting ‘system is in startup state’. However in my case it got fixed by restarting core [running core-2021.10.6].
Seems however that every time that I need to run a backup task I need to make sure to restart core otherwise it keeps reporting that the system is in startup state.
A bit frustrating!
I am now stuck in this state as well… have restarted HA, have powered down and restarted the host and nothing seems to have resolved the issue. System info below…
It does appear that an automation can request and create a backup, just can’t do it from the front end.
System Health
version: core-2021.11.3
installation_type: Home Assistant OS
dev: false
hassio: true
docker: true
user: root
virtualenv: false
python_version: 3.9.7
os_name: Linux
os_version: 5.10.17-v8
arch: aarch64
timezone: America/Chicago
GitHub API: ok
Github API Calls Remaining: 4682
Installed Version: 1.17.2
Stage: running
Available Repositories: 912
Installed Repositories: 12
host_os: Home Assistant OS 6.6
update_channel: stable
supervisor_version: supervisor-2021.10.8
docker_version: 20.10.8
disk_total: 228.5 GB
disk_used: 5.8 GB
healthy: true
supported: true
board: rpi4-64
supervisor_api: ok
version_api: ok
installed_addons: Samba share (9.5.1), ArgonOne Active Cooling (24.1), Backup Hassio to Google Drive (1.7.2), Check Home Assistant configuration (3.9.0), DHCP server (1.2), Dropbox Sync (1.3.0), Duck DNS (1.14.0), File editor (5.3.3), Glances (0.14.0), Log Viewer (0.12.1), Mosquitto broker (6.0.1), Network UPS Tools (0.9.0), Node-RED (10.1.0), Portainer (2.0.0), RPC Shutdown (2.2), SSH & Web Terminal (9.1.0), Samba Backup (5.0.0), TasmoAdmin (0.16.0), WireGuard (0.6.0), HassOS I2C Configurator (0.13), Home Assistant Google Drive Backup (0.105.2)
dashboards: 1
resources: 5
views: 15
mode: storage
I’ve had, the same issue, either it displayed Freeze state, or startup state, I’ve restarted HA, the VM (because it’s a Proxmoxx install ) didn’t help. Then I simply refreshed(F5) the Browser and voila, It’s a miracle, and the life is good once again.
The point is that backup creation is running in the background and you just have to wait to finish. Even if you restart, i guess that HA either job runs again or continues from where it was cut off at restart. Since database is also included in backup creation it can take as long as one hour to complete. And database file is easy 2GB or more.
Since i moved my main database to Synology mariaDB my backup creations are very small and very quickly finished, while before they took ages…
I think main “problem” is that nowhere in HA is indicated in any way that backup is in fact running in the background. Only thing you can notice is occasional log entry of something “being finished”.
Having the same issue. Made backups pointless and will now be starting over from scratch unless anyone has any ideas?
Ive rebooted, the VM and Host machine, verify connetivity. Still same error
1-Install “auto_backup” from jcwillox https://github.com/jcwillox/hass-auto-backup
With this integration you can easely manage the “exclude” part of addon and folder (like /media and /usbstorage for me )
2-in the UI, integration, add “Auto Backup” integration, you will then have a “sensor.auto_backup”
3-Create a binary_sensor template:
- platform: template
sensors:
auto_backup_template:
friendly_name: "Auto Backup Template"
value_template: >
{% if is_state('sensor.auto_backup', '0') %}
off
{% elif is_state('sensor.auto_backup', '1') %}
on
{% endif %}
