Hi I recently upgraded my SSD because 64GB was not enough so now I have 512GB.
Im running Home assistant OS 2023.08.1 on raspberry Pi4.
And I’m unable to make a backup now, after I migrated my install to the new ssd.
After 30min of backuping there is error:
And home assistant is in freeze state
System info:
Home Assistant 2023.8.1
Supervisor 2023.07.1
Operating System 10.4
Frontend 20230802.0 - latest
Useless LOGS:
Home Assistant Core
Updating xiaomi_cloud_map_extractor camera took longer than the scheduled update interval 0:00:05
22:34:19 – (WARNING) Camera - message first occurred at 21:57:03 and shows up 220 times
Updating twitch_helix sensor took longer than the scheduled update interval 0:02:00
22:34:16 – (WARNING) Sensor - message first occurred at 22:22:16 and shows up 4 times
Update for camera.xiaomi_cloud_map_extractor fails
22:34:11 – (ERROR) xiaomi_cloud_map_extractor (custom integration) - message first occurred at 21:56:24 and shows up 235 times
Unable to log in, check credentials
22:34:09 – (ERROR) xiaomi_cloud_map_extractor (custom integration) - message first occurred at 21:56:18 and shows up 235 times
Update of sensor.marcrebillet_2 is taking over 10 seconds
22:34:09 – (WARNING) helpers/entity.py - message first occurred at 21:57:08 and shows up 146 times
Can not load data from *hole: 192.168.1.105:8089
22:33:56 – (ERROR) components/pi_hole/__init__.py - message first occurred at 21:56:11 and shows up 31 times
Update for sensor.waqi_krakow_ul_dietla_malopolska_poland fails
22:31:24 – (ERROR) components/waqi/sensor.py - message first occurred at 22:21:24 and shows up 39 times
Referenced entities switch.bathroom_light_switch_left, switch.bathroom_light_switch_right are missing or not currently available
22:31:06 – (WARNING) helpers/service.py - message first occurred at 22:01:29 and shows up 19 times
Error requesting co2signal data: HTTPSConnectionPool(host='api.co2signal.com', port=443): Max retries exceeded with url: /v1/latest?lon=19.90086436271668&lat=50.02081752919411 (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f63d2d7d0>: Failed to establish a new connection: [Errno 101] Network unreachable'))
22:30:40 – (ERROR) Electricity Maps
Failed to retrieve broadcast user from Twitch API: purgegamers
22:30:26 – (WARNING) twitch_helix (custom integration) - message first occurred at 22:22:26 and shows up 18 times
Can't connect to ESPHome API for esp32-testbed @ 192.168.1.131: Error connecting to ('192.168.1.131', 6053): [Errno 113] Connect call failed ('192.168.1.131', 6053) (SocketAPIError)
22:26:14 – (WARNING) runner.py - message first occurred at 21:56:19 and shows up 9 times
TemplateError('ValueError: Template error: float got invalid input 'unavailable' when rendering template '{% set left2 = states('sensor.speaker_l_energy_total') | float %} {% set right2 = states('sensor.speaker_r_energy_total') | float %} {{ (left2 + right2) | round(2) }}' but no default was specified') while processing template 'Template<template=({% set left2 = states('sensor.speaker_l_energy_total') | float %} {% set right2 = states('sensor.speaker_r_energy_total') | float %} {{ (left2 + right2) | round(2) }}) renders=12>' for attribute '_attr_native_value' in entity 'sensor.speakers_energy_total'
22:26:11 – (ERROR) helpers/template_entity.py - message first occurred at 21:58:31 and shows up 9 times
Unable to parse temperature sensor sensor.bme680_temperature_2 with state: unavailable
22:26:11 – (ERROR) mold_indicator - message first occurred at 21:58:31 and shows up 10 times
home-air-quality-sensor-32 @ 192.168.1.172: Connection error occurred: Ping response not received after 90.0 seconds
22:26:11 – (WARNING) runner.py - message first occurred at 21:58:28 and shows up 7 times
State attributes for sensor.watchman_missing_entities exceed maximum size of 16384 bytes. This can cause database performance issues; Attributes will not be stored
22:15:12 – (WARNING) Recorder - message first occurred at 21:56:33 and shows up 12 times
Invalid state specified for select.wled_playlist: unavailable
22:06:41 – (WARNING) Select - message first occurred at 22:06:39 and shows up 12 times
Invalid state specified for light.wled_segment_2: unavailable
22:06:41 – (WARNING) Light - message first occurred at 22:06:39 and shows up 24 times
Platform esphome does not generate unique IDs. ID 08:3A:F2:AC:60:F0 already exists - ignoring update.home_air_quality_sensor_32_firmware
22:01:16 – (ERROR) Update
The unit of sensor.speaker_l_energy_reactivepower (var) cannot be converted to the unit of previously compiled statistics (VAr). Generation of long term statistics will be suppressed unless the unit changes back to VAr or a compatible unit. Go to https://my.home-assistant.io/redirect/developer_statistics to fix this
22:00:10 – (WARNING) Sensor - message first occurred at 21:56:33 and shows up 26 times
MQTT entity name starts with the device name in your config {'availability': [{'topic': 'zigbee2mqtt/bridge/state', 'payload_available': 'online', 'payload_not_available': 'offline'}], 'device': {'identifiers': ['zigbee2mqtt_0xa4c1382f123fd9b7'], 'manufacturer': 'TuYa', 'model': 'Smart plug (with power monitoring) (TS011F_plug_1)', 'name': 'Monitors and Power', 'connections': []}, 'device_class': <SensorDeviceClass.CURRENT: 'current'>, 'enabled_by_default': False, 'entity_category': <EntityCategory.DIAGNOSTIC: 'diagnostic'>, 'json_attributes_topic': 'zigbee2mqtt/Monitors and Power', 'name': 'Monitors and Power current', 'state_class': <SensorStateClass.MEASUREMENT: 'measurement'>, 'state_topic': 'zigbee2mqtt/Monitors and Power', 'unique_id': '0xa4c1382f123fd9b7_current_zigbee2mqtt', 'unit_of_measurement': 'A', 'value_template': Template<template=({{ value_json.current }}) renders=0>, 'qos': 0, 'payload_not_available': 'offline', 'availability_mode': 'latest', 'payload_available': 'online', 'encoding': 'utf-8', 'force_update': False}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes 'Current'
21:57:05 – (WARNING) MQTT - message first occurred at 21:56:20 and shows up 219 times
Error initializing 'WLED cold light morning' trigger: In 'numeric_state' condition: unknown entity sensor.pc_energy_apparentpower
21:56:26 – (WARNING) Home Assistant Core Integration
TemplateError('ValueError: Template error: float got invalid input 'unavailable' when rendering template '{% set left1 = states('sensor.tasmota_l_energy_power') | float %} {% set center1 = states('sensor.monitors_and_power_energy') | float %} {% set right1 = states('sensor.pc_power') | float %} {{ (left1 + + center1 + right1) | round(0) }}' but no default was specified') while processing template 'Template<template=({% set left1 = states('sensor.tasmota_l_energy_power') | float %} {% set center1 = states('sensor.monitors_and_power_energy') | float %} {% set right1 = states('sensor.pc_power') | float %} {{ (left1 + + center1 + right1) | round(0) }}) renders=4>' for attribute '_attr_native_value' in entity 'sensor.total_av_power'
21:56:25 – (ERROR) helpers/template_entity.py - message first occurred at 21:56:25 and shows up 7 times
Error while processing template: Template<template=({% set inside = states('sensor.bme680_temperature_2') | float %} {% set outside = states('sensor.outside_temperature') | float %} {% set critical = states('sensor.critical_temperature') | float %} {{ ((inside - outside)/(critical - outside)) | round(1) }}) renders=2>
21:56:25 – (ERROR) helpers/template.py - message first occurred at 21:56:25 and shows up 4 times
Config entry '192.168.1.211:19444' for hyperion integration not ready yet: None; Retrying in background
21:56:19 – (WARNING) config_entries.py - message first occurred at 21:56:11 and shows up 7 times
Platform esphome does not generate unique IDs. ID home-air-quality-sensor-32lightled_air_quality already exists - ignoring light.led_air_quality
21:56:16 – (ERROR) Light
Platform esphome does not generate unique IDs. ID home-air-quality-sensor-32switchcalibrate_co2_sensor_mh-z19 already exists - ignoring switch.calibrate_co2_sensor_mh_z19
21:56:16 – (ERROR) Switch
Platform esphome does not generate unique IDs. ID home-air-quality-sensor-32sensorbme680_temperature already exists - ignoring sensor.bme680_temperature_2
21:56:16 – (ERROR) Sensor - message first occurred at 21:56:16 and shows up 11 times
Dashboard unavailable; skipping reauth: Cannot connect to host 127.0.0.1:63428 ssl:default [Connect call failed ('127.0.0.1', 63428)]
21:56:15 – (ERROR) ESPHome
Error requesting ESPHome Dashboard data: Cannot connect to host 127.0.0.1:63428 ssl:default [Connect call failed ('127.0.0.1', 63428)]
21:56:15 – (ERROR) ESPHome
Setup of sensor platform twitch_helix is taking over 10 seconds.
21:56:13 – (WARNING) Sensor - message first occurred at 21:56:13 and shows up 2 times
The moon platform for the sensor integration does not support platform setup. Please remove it from your config.
21:56:02 – (ERROR) Sensor
Failed to to call /store -
21:55:52 – (ERROR) Home Assistant Supervisor
/store return code 500
21:55:52 – (ERROR) Home Assistant Supervisor
It seems to stop when the mariadb add on starts to backup, no errors or warnings
23-08-07 00:44:25 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon a0d7b954_influxdb
23-08-07 00:44:25 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on core_mosquitto
23-08-07 00:44:25 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon core_mosquitto
23-08-07 00:44:25 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on a0d7b954_nodered
23-08-07 00:44:25 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon a0d7b954_nodered
23-08-07 00:44:26 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on core_mariadb
23-08-07 00:44:59 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
what was the size of your last backup, that included mariaDB (ideally how big is the mariaDB)?
how long did you let that run?
Is there a real error still present, because this log only shows infos, and mariadb can take a very long time to backup?
EDIT: the log is only 30 minutes old, mariaDB can take up to a few hours to backup, depending on the computer it runs on. A Pi4 is not the fastest for such operations, I’d let it run for at least two hours, and check the log from time to time, if an error comes up. But as long as only infos are present in the log, let it run.
like i said no errors no warnings no nothing. After it starts mariadb backup i get unknown error and thats it
I run it again today. Here are the logs. this time it failed at influxdb database
23-08-07 09:33:23 INFO (MainThread) [supervisor.backups.manager] Found 9 backup files
23-08-07 09:33:28 INFO (MainThread) [supervisor.backups.manager] Creating new full backup with slug dddec9cc
23-08-07 09:33:28 INFO (MainThread) [supervisor.backups.manager] Backing up dddec9cc store Add-ons
23-08-07 09:33:28 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on core_samba
23-08-07 09:33:28 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon core_samba
23-08-07 09:33:28 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on core_configurator
23-08-07 09:33:28 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon core_configurator
23-08-07 09:33:28 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on cebe7a76_hassio_google_drive_backup
23-08-07 09:33:28 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon cebe7a76_hassio_google_drive_backup
23-08-07 09:33:28 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on a0d7b954_grafana
23-08-07 09:33:29 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon a0d7b954_grafana
23-08-07 09:33:29 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on a0d7b954_influxdb
23-08-07 09:34:13 INFO (MainThread) [supervisor.auth] Auth request from 'core_mosquitto' for 'hassio'
23-08-07 09:34:13 WARNING (MainThread) [supervisor.auth] Unauthorized login for 'hassio'
23-08-07 09:46:26 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
EDIT: It seems that the backup was created. But i dont know how much i can trust it with this unknown error. Is there a way to check the backup?
I get exactly the same - I don’t dare to upgrade my HA-OS until I get a “good” backup. It is quite disturbing (unsafe). I have tried to setup backup to my Synology NAS and I dropped my Google Drive Backup setup
I’m having the same problem. Can’t create a backup. No errors shown in the Supervisor logs, only info logs, that is has backup an area/section. My backup files are usually around 500mb.
23-09-05 07:51:26 INFO (MainThread) [supervisor.backups.manager] Creating new full backup with slug 73a171da
23-09-05 07:51:26 INFO (MainThread) [supervisor.backups.manager] Backing up 73a171da store Add-ons
23-09-05 07:51:26 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on core_mosquitto
23-09-05 07:51:26 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon core_mosquitto
23-09-05 07:51:26 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on core_deconz
23-09-05 07:51:26 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon core_deconz
23-09-05 07:51:26 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on a0d7b954_vscode
23-09-05 07:51:33 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon a0d7b954_vscode
23-09-05 07:51:33 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on core_matter_server
23-09-05 07:51:33 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon core_matter_server
23-09-05 07:51:33 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on core_silabs_multiprotocol
23-09-05 07:51:33 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon core_silabs_multiprotocol
23-09-05 07:51:33 INFO (MainThread) [supervisor.homeassistant.module] Backing up Home Assistant Core config folder
The log you posted doesn’t show any error regarding the backup, it just shows, that the influxdb backup isn’t finished at that point.
The only way to check a backup is to restore it. If you want to check, if the backup is working, take a fresh installation of HA and restore the backup. You’ll now see, if everything is working. But don’t delete your running HA installation!
What makes you think, you can’t do a backup? The log you show says nothing about an error. What we can see is that at the moment you scanned that log, the backup for the config folder is still running. That’s it.
That is exactly the “problem” The backup modal shows an error (red alert box), but the error isn’t logged. It just stops and HA ends in a freeze state. The *.TAR backup file isn’t complete (can’t be extracted) and the temporary subfolder tmps1lg5i1q still exist in the backup location. The alert shown, describes that the error can be found in the Supervisor logs, which has no errors logged.
23-09-07 08:00:51 INFO (MainThread) [supervisor.backups.manager] Backing up 01582581 store Add-ons
23-09-07 08:00:51 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on core_mosquitto
23-09-07 08:00:51 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon core_mosquitto
23-09-07 08:00:51 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on core_deconz
23-09-07 08:00:51 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon core_deconz
23-09-07 08:00:51 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on a0d7b954_vscode
23-09-07 08:00:59 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon a0d7b954_vscode
23-09-07 08:00:59 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on core_matter_server
23-09-07 08:00:59 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon core_matter_server
23-09-07 08:00:59 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on core_silabs_multiprotocol
23-09-07 08:00:59 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon core_silabs_multiprotocol
23-09-07 08:00:59 INFO (MainThread) [supervisor.homeassistant.module] Backing up Home Assistant Core config folder
I’m tempted to call it a bug (that’s the second time today ). Let’s just recap: we have four users with an error message, that links to the log, where no errors are logged?
I am very sorry, but I’m really out of ideas for now…
I tried to examine this a bit further. My backup is stored in a Network storage (CIFS) configured in HA. It looks like the modal error is a false positive in some cases.
I noticed this time, that when the error was shown - the backup job was still running on homeassistant.tar.gz. I’ve kept an eye on it and it eventually completed after 19 minutes (for at 480mb file). The question might be, if there is some kind of bug, when backing up to a network storage path.
23-09-10 07:43:34 INFO (MainThread) [supervisor.backups.manager] Creating new full backup with slug a62c8f77
23-09-10 07:43:34 INFO (MainThread) [supervisor.backups.manager] Backing up a62c8f77 store Add-ons
23-09-10 07:43:34 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on core_mosquitto
23-09-10 07:43:34 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon core_mosquitto
23-09-10 07:43:34 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on core_deconz
23-09-10 07:43:34 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon core_deconz
23-09-10 07:43:34 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on a0d7b954_vscode
23-09-10 07:43:42 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon a0d7b954_vscode
23-09-10 07:43:42 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on core_matter_server
23-09-10 07:43:42 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon core_matter_server
23-09-10 07:43:42 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on core_silabs_multiprotocol
23-09-10 07:43:42 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon core_silabs_multiprotocol
23-09-10 07:43:42 INFO (MainThread) [supervisor.homeassistant.module] Backing up Home Assistant Core config folder
23-09-10 08:01:39 INFO (MainThread) [supervisor.homeassistant.module] Backup Home Assistant Core config folder done
23-09-10 08:01:39 INFO (MainThread) [supervisor.backups.manager] Backing up a62c8f77 store folders
23-09-10 08:01:39 INFO (SyncWorker_4) [supervisor.backups.backup] Backing up folder share
23-09-10 08:01:39 INFO (SyncWorker_4) [supervisor.backups.backup] Backup folder share done
23-09-10 08:01:39 INFO (SyncWorker_1) [supervisor.backups.backup] Backing up folder addons/local
23-09-10 08:01:39 INFO (SyncWorker_1) [supervisor.backups.backup] Backup folder addons/local done
23-09-10 08:01:39 INFO (SyncWorker_1) [supervisor.backups.backup] Backing up folder ssl
23-09-10 08:01:39 INFO (SyncWorker_1) [supervisor.backups.backup] Backup folder ssl done
23-09-10 08:01:39 INFO (SyncWorker_0) [supervisor.backups.backup] Backing up folder media
23-09-10 08:01:39 INFO (SyncWorker_0) [supervisor.backups.backup] Backup folder media done
23-09-10 08:02:10 INFO (MainThread) [supervisor.backups.manager] Creating full backup with slug a62c8f77 completed
Can you do a backup on the local HA storage without problems? That would narrow it down to “something with the network storage”. Narrow might not be the fitting term here, but you know .rofl:
It could look like it is some kind of timeout when using a Network storage path. Now it completed without errors (when removing network storage), even though it is extremely slow for 480mb (22mins)
23-09-10 16:44:14 INFO (MainThread) [supervisor.backups.manager] Creating new full backup with slug 5e3a5eb0
23-09-10 16:44:15 INFO (MainThread) [supervisor.backups.manager] Backing up 5e3a5eb0 store Add-ons
23-09-10 16:44:15 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on core_mosquitto
23-09-10 16:44:15 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon core_mosquitto
23-09-10 16:44:15 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on core_deconz
23-09-10 16:44:16 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon core_deconz
23-09-10 16:44:16 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on a0d7b954_vscode
23-09-10 16:45:28 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon a0d7b954_vscode
23-09-10 16:45:29 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on core_matter_server
23-09-10 16:45:29 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon core_matter_server
23-09-10 16:45:29 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on core_silabs_multiprotocol
23-09-10 16:45:29 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon core_silabs_multiprotocol
23-09-10 16:45:31 INFO (MainThread) [supervisor.homeassistant.module] Backing up Home Assistant Core config folder
23-09-10 17:07:03 INFO (MainThread) [supervisor.homeassistant.module] Backup Home Assistant Core config folder done
23-09-10 17:07:04 INFO (MainThread) [supervisor.backups.manager] Backing up 5e3a5eb0 store folders
23-09-10 17:07:04 INFO (SyncWorker_4) [supervisor.backups.backup] Backing up folder share
23-09-10 17:07:04 INFO (SyncWorker_4) [supervisor.backups.backup] Backup folder share done
23-09-10 17:07:04 INFO (SyncWorker_0) [supervisor.backups.backup] Backing up folder addons/local
23-09-10 17:07:04 INFO (SyncWorker_0) [supervisor.backups.backup] Backup folder addons/local done
23-09-10 17:07:04 INFO (SyncWorker_5) [supervisor.backups.backup] Backing up folder ssl
23-09-10 17:07:04 INFO (SyncWorker_5) [supervisor.backups.backup] Backup folder ssl done
23-09-10 17:07:04 INFO (SyncWorker_1) [supervisor.backups.backup] Backing up folder media
23-09-10 17:07:04 INFO (SyncWorker_1) [supervisor.backups.backup] Backup folder media done
23-09-10 17:07:18 INFO (MainThread) [supervisor.backups.manager] Creating full backup with slug 5e3a5eb0 completed
Switching back to Network storage results in a false positive error again. Backup is still running in the background though. So it can almost only be a timeout defined somewhere, which results in the UI error.
I see the same issue here on my Pi4 installation, but I’m NOT using any kind of network storage. Instead the backup is stored on the same SSD the Pi is booting / running from (which isn’t full or shows any other problems).
The modal seems to be misleading though, since the backup keeps running in the background and eventually finishes (creates the backup file on disk and deletes the tmp****** folder).
As for the integrity (corrupt or not) of the backup: that remains to be seen when I reinstall later…
Let’s see, what the logs bring up. 
The backup modal shows an error (red alert box), but the error isn’t logged. It just stops and HA ends in a 
). Let’s just recap: we have four users with an error message, that links to the log, where no errors are logged?
Narrow might not be the fitting term here, but you know .rofl: