search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
73.8k stars 30.9k forks source link

i can't backup home assistant core #124454

Open vothar opened 2 months ago

vothar commented 2 months ago

The problem

i make a full backup before each new version of home assistant. my last full backup was from before 2024.8 version. Just after my last full backup (august the 6, 2024) and before trying to update to version 2024.8, i can't make anymore a full backup of home assistant. i can make a partial backup of the add-ons and Folders section, but when i try to do the partial backup (or a full backup) of the 'home assistant (2024.7.4)' section, i get the error ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /backups/new/partial - An error occurred while making backup, check job 'b567fa7559c140588be5c2489fffddd8' or supervisor logs for details and if i look at the supervisor log, i get ERROR (MainThread) [supervisor.homeassistant.module] Preparing backup of Home Assistant Core failed. Check HA Core logs.

i'm using a RPi4 with HA on a SSD drive.

any idea ?

What version of Home Assistant Core has the issue?

core-2024.7.4

What was the last working version of Home Assistant Core?

core-2024.7.4

What type of installation are you running?

Home Assistant OS

Integration causing the issue

backups

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

HA core log error
ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /backups/new/partial - An error occurred while making backup, check job 'b567fa7559c140588be5c2489fffddd8' or supervisor logs for details

supervisor log error
ERROR (MainThread) [supervisor.homeassistant.module] Preparing backup of Home Assistant Core failed. Check HA Core logs

Additional information

System Information

version core-2024.7.4
installation_type Home Assistant OS
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.12.4
os_name Linux
os_version 6.6.31-haos-raspi
arch aarch64
timezone America/Toronto
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 | 1461 Downloaded Repositories | 26 HACS Data | ok
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 | Home Assistant OS 13.1 -- | -- update_channel | stable supervisor_version | supervisor-2024.08.0 agent_version | 1.6.0 docker_version | 26.1.4 disk_total | 109.3 GB disk_used | 17.9 GB healthy | true supported | true host_connectivity | true supervisor_connectivity | true ntp_synchronized | true virtualization | board | rpi4-64 supervisor_api | ok version_api | ok installed_addons | Mosquitto broker (6.4.1), TheengsGateway (1.11.4), ZigStar TI CC2652P/P7 FW Flasher (0.4.0), Piper (1.5.2), ESPHome (2024.8.0), Advanced SSH & Web Terminal (18.0.0), File editor (5.8.0), Samba share (12.3.2), LMS Lyrion Music Server(Formerly Logitech Media Server) (8.5.2.0), Squeezelite (0.0.19), motionEye (0.20.0)
Dashboards dashboards | 25 -- | -- resources | 15 views | 23 mode | storage
Recorder oldest_recorder_run | August 22, 2024 at 17:52 -- | -- current_recorder_run | August 22, 2024 at 14:27 estimated_db_size | 23.21 MiB database_engine | sqlite database_version | 3.45.3
nekorevend commented 2 months ago

I see the same thing here, also on 2024.7.4!

home-assistant[bot] commented 2 months ago

Hey there @home-assistant/supervisor, mind taking a look at this issue as it has been labeled with an integration (hassio) you are listed as a code owner for? Thanks!

Code owner commands Code owners of `hassio` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign hassio` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)

hassio documentation hassio source (message by IssueLinks)

eric1090 commented 2 months ago

same for me

RenaudPerr commented 2 months ago

Hello Quite strange. I had the same problem yesterday with several attempts ( Full + partial) even after reboot with Core 2024.8.2 on RPI3, and this morning, it is OK again, without any new installation / upgrade

ledeckyr commented 2 months ago

Hello, I have the same Raspberry Pi 3/64GB SD card. Full backkup has the same issue, partial (like folder) is O.K. I'm after recovery(afted SD card crash) and change of SD card from 32GB to 64GB. Radek Core 2024.8.3; Supervisor 2024.08.0; Operating System 13.1; Frontend 20240809.0

agners commented 2 months ago

@vothar It seems the Supervisor fails to take the backup when notifying the Core that a backup is about to be taken. Is there really nothing else in the Core logs? :thinking:

@eric1090 @RenaudPerr @ledeckyr were the errors on both sides the exact same (Core and Supervisor logs as reported by the original poster)? If the problem disappeared again it might have been a temporary hickup communicating with the Core.

RenaudPerr commented 2 months ago

@agners tks for your answer but my logs were full of debug lines and I cannot retrieve the errors anymore. I will update this post if pb appears again.

vothar commented 2 months ago

@agners i just try another time and it's what i get from HA core 

 Logger: homeassistant.components.hassio
Source: components/hassio/websocket_api.py:135
integration: Home Assistant Supervisor (documentation, issues)
First occurred: 11:07:13 (1 occurrences)
Last logged: 11:07:13

Failed to to call /backups/new/full - An error occurred while making backup, check job '63041d752d3d45819667a967e86d8ebc' or supervisor logs for details

and then from supervisor 

2024-08-28 11:07:07.026 INFO (MainThread) [supervisor.backups.manager] Backup 6c3f1d4d starting stage addon_repositories
2024-08-28 11:07:07.027 INFO (MainThread) [supervisor.backups.manager] Backup 6c3f1d4d starting stage docker_config
2024-08-28 11:07:07.027 INFO (MainThread) [supervisor.backups.manager] Creating new full backup with slug 6c3f1d4d
2024-08-28 11:07:07.031 INFO (MainThread) [supervisor.backups.manager] Backup 6c3f1d4d starting stage home_assistant
2024-08-28 11:07:13.407 ERROR (MainThread) [supervisor.homeassistant.module] Preparing backup of Home Assistant Core failed. Check HA Core logs.

with Core 2024.7.4 Supervisor 2024.08.0 Operating System 13.1 Frontend 20240710.0

is there something i can set to make Core log more verbose ?

ledeckyr commented 2 months ago

@agners After more restarts it looks good. And I decided, that I will reinstal it to new HW as clear instalation and will migrate only automatizations.

vothar commented 2 months ago

@agners i also try a 'Ha core rebuild' on CLI to see if it change something and no, same errors when i try a backup after the core rebuild...

Jolskutin commented 2 months ago

Same issue still also with 2024.09.0 .... same errors as above; cannot make core backup What does a warning: "Database already locked" mean, is it possibly linked to the failing backups?

bconte commented 2 months ago

Running into the same issue, can't backup core (example below is a partial backup of just core)


2024-09-06 12:16:24.742 ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /backups/new/partial - An error occurred while making backup, check job '4071de4f262a4d788e7b1f1da4f43cd8' or supervisor logs for details
2024-09-06 12:15:39.445 INFO (MainThread) [supervisor.backups.manager] Backup 906d5bab starting stage addon_repositories
2024-09-06 12:15:39.446 INFO (MainThread) [supervisor.backups.manager] Backup 906d5bab starting stage docker_config
2024-09-06 12:15:39.446 INFO (MainThread) [supervisor.backups.manager] Creating new partial backup with slug 906d5bab
2024-09-06 12:15:39.503 INFO (MainThread) [supervisor.backups.manager] Backup 906d5bab starting stage home_assistant
2024-09-06 12:16:09.513 ERROR (MainThread) [supervisor.homeassistant.module] Preparing backup of Home Assistant Core failed. Check HA Core logs.

Is there anything else i can include that would help debug this?

Jolskutin commented 2 months ago

Did some trials and errors in the weekend; Made a clean install to a windows VM, core 2024.9.1; backup1 OK installed SSH, backup2 OK used ssh to copy backup I managed to do somehow earlier from my full system with core 2024.9.0 restored it (some hassle with starting ZHA) and the whole system works, BUT backup does not work anymore restored to backup2 -> backup does not work

Jolskutin commented 2 months ago

Could this be related; my history freezes after about two hours after restarting the whole machine

Jolskutin commented 2 months ago

Anybody?? tips for more deep logging / debugging

mx-square commented 2 months ago

I seem to be having the same problem on 2024.9.1.

When I try to do a backup, a 10kb *.tar file is created in the backup directoy but I get the following errors messages:

HA Core Logs:

Logger: homeassistant.components.hassio Source: components/hassio/websocket_api.py:135 integration: Home Assistant Supervisor (documentation, issues) First occurred: 19:21:34 (2 occurrences) Last logged: 19:32:05

Failed to to call /backups/new/full - An error occurred while making backup, check job 'ead6b379d56743bf8c6d87e74509bf86' or supervisor logs for details Failed to to call /backups/new/full - An error occurred while making backup, check job '80905ee7726f4d5da5132f5e8d965d2d' or supervisor logs for details

Supervisor Logs:

2024-09-13 19:31:32.046 INFO (MainThread) [supervisor.backups.manager] Found 0 backup files 2024-09-13 19:31:32.061 INFO (MainThread) [supervisor.backups.manager] Found 0 backup files 2024-09-13 19:31:35.063 INFO (MainThread) [supervisor.backups.manager] Backup 2b678043 starting stage addon_repositories 2024-09-13 19:31:35.063 INFO (MainThread) [supervisor.backups.manager] Backup 2b678043 starting stage docker_config 2024-09-13 19:31:35.063 INFO (MainThread) [supervisor.backups.manager] Creating new full backup with slug 2b678043 2024-09-13 19:31:35.646 INFO (MainThread) [supervisor.backups.manager] Backup 2b678043 starting stage home_assistant 2024-09-13 19:32:05.653 ERROR (MainThread) [supervisor.homeassistant.module] Preparing backup of Home Assistant Core failed. Check HA Core logs.

Farmand77 commented 2 months ago

I have the same errors. Running on x86 everything updated. But if i delete the 10kb file/files reboot ha and when started jump directly into system and backup it Will do the backup

vothar commented 2 months ago

yes @Farmand77 .. I've tried it and I can confirm that it also works with my HA on an RPi4. However, I see an error when starting the backup when Ha has not finished rebooting completely. 2024-09-15 20:08:43.648 WARNING (MainThread) [homeassistant.components.recorder.core] Database currently not locked

vothar commented 1 month ago

I'll add to the problem that if you do a core update (like today with 2024.9.2 to 2024.9.3), and you leave the box checked to make a backup before the update, the update is done without any report indicating that the backup failed (you can see it only with the infamous 10kb backup file full of nothing in backup directory)... and you're screwed if the update has a problem.

the problem is still present with HA 2024.9.3 fully updated.

gillesguillemin commented 1 month ago

I'm on the same boat here, and have been for literally several months now, hoping to see some sort of resolution before I end up totally screwed like you said @vothar.

It doesn't look like an isolated problem and yet...

vothar commented 1 month ago

in the mean time @gillesguillemin , you can use @Farmand77 solution before an update ( reboot HA, then start backup as soon as you get HA reconnected and before HA finish the reboot cycle..)

gillesguillemin commented 1 month ago

Thanks, I had missed that tip 👍 Will try.

gillesguillemin commented 1 month ago

Brilliant, it works indeed, so at least now I've got a current backup.

AllegedlyUndead commented 1 month ago

in the mean time @gillesguillemin , you can use @Farmand77 solution before an update ( reboot HA, then start backup as soon as you get HA reconnected and before HA finish the reboot cycle..)

I can't even get this to work in 2024.9.2. Just creates the same 25,790kb .tar file. I am going to be moving my HA to a dell micro PC and am really trying to not have to rebuild everything from scratch but I can't get a new backup smh

Jolskutin commented 1 month ago

2024.9.3 brought the problem back? somehow all started to work with 9.2, BOTH database and backups now after update to 9.3 and about a day after, the database is locked and backups does not work (database locked means that all history is now flat lines, all charts shows flat, though the sensors gives the right value to the UI)

vothar commented 1 month ago

When I encounter this flat sensor recording problem, a complete reboot of the host usually brings all the sensors back to life. (a full reboot, not only HA reboot)

Jolskutin commented 1 month ago

Well, just now it worked after full restart about 1 hour, sometimes it works even 3 hours. Size of the DB is now about 2M, and about 20% of the disk is used.

Strange thing happened this morning, the automatic full backup worked.... manual backup did not work yesterday, nor does it work today.

prenetic commented 1 month ago

Same here, been happening for me around 2024.07 / 2024.08. It's gotten to the point where I have to accept that 50% of my backup attempts will fail. What's worse is with the database lock not being released upon backup failure I had to automate restarting HAOS five minutes after a backup is requested to forcibly release the lock.

prenetic commented 1 month ago

Given there are a handful of similar issues that have been opened around the same timeframe, I'm wondering if something changed recently that is leading to these backup failures. My setup is fairly lightweight and I haven't made changes on my end in quite some time.

Not only am I having the issue above, but also below (even though my backups are all taking place locally, no Samba integration). All started happening at the same time.

https://github.com/home-assistant/supervisor/issues/5288 https://github.com/home-assistant/supervisor/issues/3707

I see lots of these errors in the supervisor logs whenever I interact with the native backup component, and curiously I see "Found 42 backup files" even though in the backups menu I only see 17.

2024-10-15 19:00:18.481 INFO (MainThread) [supervisor.backups.manager] Found 42 backup files
2024-10-15 19:00:18.484 ERROR (MainThread) [supervisor.backups.backup] Can't read backup tarfile /data/backup/9d35182d.tar: "filename './backup.json' not found"
2024-10-15 19:00:18.484 ERROR (MainThread) [supervisor.backups.backup] Can't read backup tarfile /data/backup/0f1500c8.tar: "filename './backup.json' not found"
2024-10-15 19:00:18.485 ERROR (MainThread) [supervisor.backups.backup] Can't read backup tarfile /data/backup/bd516aca.tar: "filename './backup.json' not found"
2024-10-15 19:00:18.485 ERROR (MainThread) [supervisor.backups.backup] Can't read backup tarfile /data/backup/e5a4ad74.tar: "filename './backup.json' not found"
2024-10-15 19:00:18.485 ERROR (MainThread) [supervisor.backups.backup] Can't read backup tarfile /data/backup/a94dc78d.tar: "filename './backup.json' not found"

When checking /backup I DO show 42 backup files, but many of them are 10K in size (presumably the failed backups that have been accumulating).

[core-ssh backup]$ ls -lh
total 2G
-rw-r--r--    1 root     root       10.0K Oct 14 00:00 0e329cf6.tar
-rw-r--r--    1 root     root       10.0K Aug  9 00:00 0f1500c8.tar
-rw-r--r--    1 root     root       10.0K Sep 26 00:46 113d72a6.tar
-rw-r--r--    1 root     root       97.4M Mar  4  2024 1ab82815.tar
-rw-r--r--    1 root     root      101.2M Jan  1  2024 1f3530f2.tar
-rw-r--r--    1 root     root       63.5M Dec  4  2023 21de9cc6.tar
-rw-r--r--    1 root     root       10.0K Oct  3 00:08 292d2a96.tar
-rw-r--r--    1 root     root      132.8M Oct  7 00:09 2bd660d5.tar
-rw-r--r--    1 root     root       76.7M Nov  6  2023 3a375526.tar
-rw-r--r--    1 root     root       10.0K Aug  8 00:00 3b7b2ed8.tar
-rw-r--r--    1 root     root       10.0K Sep  6 00:00 45683feb.tar
-rw-r--r--    1 root     root       10.0K Oct 14 21:20 4c40f773.tar
-rw-r--r--    1 root     root       78.2M Sep  2 00:00 4cc893c1.tar
-rw-r--r--    1 root     root      116.7M Sep 30 00:00 6676013f.tar
-rw-r--r--    1 root     root       10.0K Sep  5 00:00 73292c56.tar
-rw-r--r--    1 root     root      122.2M Jun  3 00:00 74d0dab7.tar
-rw-r--r--    1 root     root       10.0K Oct  9 00:00 77828b71.tar
-rw-r--r--    1 root     root       10.0K Oct  5 00:00 7a421288.tar
-rw-r--r--    1 root     root      139.1M Oct  8 00:00 87e77e01.tar
-rw-r--r--    1 root     root       10.0K Oct  6 00:00 92699f07.tar
-rw-r--r--    1 root     root       10.0K Sep  3 00:00 96917071.tar
-rw-r--r--    1 root     root      143.0M Oct 11 00:00 96b9cd46.tar
-rw-r--r--    1 root     root       10.0K Sep 16 12:38 9d35182d.tar
-rw-r--r--    1 root     root      151.1M Oct 13 00:00 a01f06c5.tar
-rw-r--r--    1 root     root       10.0K Oct 14 21:17 a87553f0.tar
-rw-r--r--    1 root     root       10.0K Sep  4 00:00 a94dc78d.tar
-rw-r--r--    1 root     root       10.0K Sep 22 01:30 ad16e3aa.tar
-rw-r--r--    1 root     root      102.0M Apr  1  2024 b186eb75.tar
-rw-r--r--    1 root     root       10.0K Oct 15 00:00 b746fec2.tar
-rw-r--r--    1 root     root       95.7M Feb  5  2024 ba37ce07.tar
-rw-r--r--    1 root     root       10.0K Oct 10 00:00 bd516aca.tar
-rw-r--r--    1 root     root      117.2M Aug  5 00:00 c2517b32.tar
-rw-r--r--    1 root     root       10.0K Oct 14 21:22 c5505348.tar
-rw-r--r--    1 root     root      151.2M Oct 12 00:00 c5665c41.tar
-rw-r--r--    1 root     root       10.0K Aug  7 00:00 ce85be12.tar
-rw-r--r--    1 root     root       10.0K Sep 13 00:00 d32e35e7.tar
-rw-r--r--    1 root     root       10.0K Sep 23 01:30 d9c0af0f.tar
-rw-r--r--    1 root     root       10.0K Oct 14 21:19 e5a4ad74.tar
-rw-r--r--    1 root     root       10.0K Sep 16 00:00 ef8eb706.tar
-rw-r--r--    1 root     root      109.9M May  6 00:00 f34e119e.tar
-rw-r--r--    1 root     root       10.0K Sep 24 01:30 f483574d.tar
-rw-r--r--    1 root     root      112.9M Jul  1 00:00 fc514b1c.tar

I've deleted these backups manually via the CLI and issued five full backups manually which were successful. I will let this run for a few days and see if the situation has improved, as failures only occur sometimes. I also only saw failures occur when "Home Assistant" was selected for partial backups which gives me the idea this isn't caused by an add-on.

2024-10-15 19:14:59.479 INFO (MainThread) [supervisor.backups.manager] Creating new full backup with slug 895203e0
2024-10-15 19:14:59.483 INFO (MainThread) [supervisor.backups.manager] Backup 895203e0 starting stage home_assistant
2024-10-15 19:15:30.795 INFO (MainThread) [supervisor.homeassistant.module] Backing up Home Assistant Core config folder
2024-10-15 19:15:36.683 INFO (MainThread) [supervisor.homeassistant.module] Backup Home Assistant Core config folder done
2024-10-15 19:15:36.690 INFO (MainThread) [supervisor.backups.manager] Backup 895203e0 starting stage addons
2024-10-15 19:15:36.755 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on core_ssh
2024-10-15 19:15:36.766 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon core_ssh
2024-10-15 19:15:36.798 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on a0d7b954_logviewer
2024-10-15 19:15:36.800 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon a0d7b954_logviewer
2024-10-15 19:15:36.825 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on core_configurator
2024-10-15 19:15:36.828 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon core_configurator
2024-10-15 19:15:36.855 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on core_matter_server
2024-10-15 19:15:38.213 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon core_matter_server
2024-10-15 19:15:38.278 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on a0d7b954_aircast
2024-10-15 19:15:38.304 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon a0d7b954_aircast
2024-10-15 19:15:38.304 INFO (MainThread) [supervisor.backups.manager] Backup 895203e0 starting stage folders
2024-10-15 19:15:38.305 INFO (SyncWorker_11) [supervisor.backups.backup] Backing up folder share
2024-10-15 19:15:38.320 INFO (SyncWorker_11) [supervisor.backups.backup] Backup folder share done
2024-10-15 19:15:38.321 INFO (SyncWorker_23) [supervisor.backups.backup] Backing up folder addons/local
2024-10-15 19:15:38.322 INFO (SyncWorker_23) [supervisor.backups.backup] Backup folder addons/local done
2024-10-15 19:15:38.322 INFO (SyncWorker_10) [supervisor.backups.backup] Backing up folder ssl
2024-10-15 19:15:38.341 INFO (SyncWorker_10) [supervisor.backups.backup] Backup folder ssl done
2024-10-15 19:15:38.341 INFO (SyncWorker_2) [supervisor.backups.backup] Backing up folder media
2024-10-15 19:15:38.349 INFO (SyncWorker_2) [supervisor.backups.backup] Backup folder media done
2024-10-15 19:15:38.349 INFO (MainThread) [supervisor.backups.manager] Backup 895203e0 starting stage finishing_file
2024-10-15 19:15:38.351 INFO (MainThread) [supervisor.backups.manager] Creating full backup with slug 895203e0 completed
2024-10-15 19:15:38.353 INFO (MainThread) [supervisor.backups.manager] Found 18 backup files
Jolskutin commented 1 month ago

and still same problem continues.. Core 2024.10.3 Supervisor 2024.10.2 Operating System 13.2 Frontend 20241002.3

backups does not work, and when backup tries to start, it freezes the database and now there is backup in queue, so after restart backup freezes database rightaway

is there anybody who could help with these

prenetic commented 4 weeks ago

Yeah unfortunately cleaning up the failed backups does not seem to have helped, so this is an ongoing issue.

agners commented 4 weeks ago

To give a bit of context, there is a bit a back and forth between Core and Supervisor as discussed here: Ultimately the Core is the frontend, and calls the Backup API. So that is why you see the first error in the Core logs:

ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /backups/new/partial - An error occurred while making backup, check job 'b567fa7559c140588be5c2489fffddd8' or supervisor logs for details

However, during backup of Core, we ask Core (or more specifically the recorder integration) to freeze the database in order to make a "hot backup".

backups does not work, and when backup tries to start, it freezes the database and now there is backup in queue, so after restart backup freezes database rightaway

So the question becomes: Why does this initial freeze does not work :thinking:

It clearly must be related to the data/database somehow, since not everyone experiences the problem.

As a test, can you try to stop the Core (ha core stop) delete (or move away) the Core database (e.g. visa Samba) and start Core gain (ha core start from the local console using keyboard/display), and see if that makes backups consistently work again?

Anybody?? tips for more deep logging / debugging

I'd be insterested if the Core shows more in detail what is going on when enabling more logging for the recorder component (see https://www.home-assistant.io/integrations/logger).

When I try to do a backup, a 10kb *.tar file is created in the backup directoy but I get the following errors messages:

I have the same errors. Running on x86 everything updated. But if i delete the 10kb file/files reboot ha and when started jump directly into system and backup it Will do the backup

Hm, that these 10kB files influence a successive is actually a separate issue which might need addressing.

Jolskutin commented 4 weeks ago

Yes, I have tried the core stop - delete DB - start core / reset HA etc ... does not help

these were in the debug logs... any useful info?

2024-10-21 22:39:08.678 DEBUG (MainThread) [homeassistant.components.websocket_api.http.connection] [139980421236624] Supervisor from 172.30.32.2 (HomeAssistantSupervisor/2024.10.2 aiohttp/3.10.10 Python/3.12): Sending b'{"id":137,"type":"result","success":false,"error":{"code":"pre_backup_actions_failed","message":"Unexpected entry type: 4"}}'
2024-10-21 22:39:08.682 DEBUG (MainThread) [homeassistant.components.websocket_api.http.connection] [139980421236624] Supervisor from 172.30.32.2 (HomeAssistantSupervisor/2024.10.2 aiohttp/3.10.10 Python/3.12): Received {'type': 'supervisor/event', 'data': {'event': 'job', 'data': {'name': 'home_assistant_module_begin_backup', 'reference': None, 'uuid': '09ac3abbab934286bc7b9a038b323ed5', 'progress': 0, 'stage': None, 'done': False, 'parent_id': '6c18128dc2af4ae4b14feaeaec3b615f', 'errors': [{'type': 'HomeAssistantBackupError', 'message': 'Preparing backup of Home Assistant Core failed. Check HA Core logs.'}]}}, 'id': 148}
Jolskutin commented 3 weeks ago

Anybody ???? please help, this is stressful knowing the backups does not work,

vothar commented 3 weeks ago

@Jolskutin at the moment, the only solution that seem to work is @Farmand77 solution ( reboot HA, then start backup as soon as you get HA reconnected and before HA finish the reboot cycle..).

Jolskutin commented 3 weeks ago

thanks.... now I manage to get backups, ...but the size of the backup file is now half it used to be ?????

Dgigie commented 1 week ago

Hello I have the same problem for several days

" Enregistreur: homeassistant.components.hassio Source: components/hassio/websocket_api.py:135 intégration: Home Assistant Supervisor (documentation, problèmes) S'est produit pour la première fois: 5 novembre 2024 à 22:13:14 (2 occurrences) Dernier enregistrement: 12:18:30

Failed to to call /backups/new/full - An error occurred while making backup, check job '3933da91afbc40c596d8f575f3b26ccf' or supervisor logs for details Failed to to call /backups/new/full - An error occurred while making backup, check job 'b8f818846fd644ae9a41dca690d724c4' or supervisor logs for details "

Do you think we have to wait for the next update to solve the problem or is there another solution?

Thanks

prenetic commented 1 week ago

This issue has persisted for months now, there's no indication a fix is coming @Dgigie.

vothar commented 1 week ago

at the moment , the temporary only solution is 3 post above...

solution

Dgigie commented 1 week ago

Thank you but I think I have finally found a solution to the problem that concerns me but perhaps others are affected. Capture

I think this is due to a problem on the hard drive where home assistant is installed, as soon as I have some time, I will format the disks and reinstall home assistant with my last backup to see if everything works again

Dgigie commented 1 week ago

A little feedback that may be useful to some people, for me it was indeed a problem on the hard drive because after reinstalling Home Assistant on another disk I put a backup and everything works perfectly again