-
-
Notifications
You must be signed in to change notification settings - Fork 28.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Backup problem after 2024.3.3 #117678
Comments
"check [...] supervisor logs for details" |
Yes. Look at logo.txt. |
Looks like you might be low on storage space. Please include your system information as well. You can find it in Settings -> System -> Repairs -> click the three dots -> System Information -> click the copy button at the bottom. |
System Information
Home Assistant Community Store
Airly
Home Assistant Cloud
Home Assistant Supervisor
Dashboards
MiWiFi
Recorder
Xiaomi Miot Auto
|
Hi, |
I try make full and partial backups - all time that same problem. |
Damn.... You have right. I forgot that I set backup on NAS - not local. :) Thanks for help |
Glad you figured it out! Maybe the error should be more clear instead of just failing. |
The problem
Hi
I can't mąkę a full backup. Last partial backup Is From one month ago.
Rejestrator: homeassistant.components.hassio
Źródło: components/hassio/websocket_api.py:135
integracja: Home Assistant Supervisor (dokumentacja, Problemy)
Pierwsze zdarzenie: 09:05:01 (1 zdarzenia)
Ostatnio zalogowany: 09:05:01
Failed to to call /backups/new/full - An error occurred while making backup, check job 'd900e8b0335045c1ab9dc1bb78e4a401' or supervisor logs for details
What version of Home Assistant Core has the issue?
core-2024.5.4
What was the last working version of Home Assistant Core?
core-2024.3.3
What type of installation are you running?
Home Assistant OS
Integration causing the issue
No response
Link to integration documentation on our website
No response
Diagnostics information
logs.txt
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: