Fox82
(Fox82)
December 3, 2025, 8:10am
1
I have implemented daily backups at 7pm. My Synology is sleeping during night until 6pm. The backup can be made sucessfully, but I get every day a supervisor repair warining, that the network drive is not reachable. This should only be shown, when the NAS backup cannot be done, what is not the case. Every day is a new message. So the warnings are cumulating each day. It disapears with a reboot of HA. Can this be deactivated or change in the software?
Installationsmethode Home Assistant OS
Core 2025.11.3
Supervisor 2025.11.5
Operating System 16.3
Frontend 20251105.1
tom_l
December 3, 2025, 9:41am
3
Network storage could be used for more than just backups, hence the repair is valid.
1 Like
pkscout
(Kyle Johnson)
December 3, 2025, 10:59am
4
I think the short answer is no, there is no way to disable just that one repair notice (or repair notices generally). Here’s a longer answer from another thread:
That is a valid repair, the example given raises errors and should be fixed.
Sounds like repairs are actually useful in this case
Repairs is core functionality that cannot be disabled, as all integrations should be able to rely on its existence (to be able to report). It is a similar think like all integration rely on the existing of devices or entities.
Repairs can be ignored when version bound (eg breaks in the future), but when causing issues, like in this very example, there i…
Biscuit
(Geoff)
December 3, 2025, 11:22am
5
For myself, the supervisor repair warning (mount failure) self-heals and always disappears at some point after my Synology NAS powers up first thing in the morning. The message may hang around for several hours, but it is always gone by evening.
I have just got used to having an orange circle with a number that either comes and goes on my HA menu, or increments and decrements during the day.
Edit:
Well I spoke too soon.
After the recent update to 2025.12.x, every night when the Synology NAS shuts down I get a new message, but unlike before, this does not go away during the day after the NAS wakes up.
Now I have a growing list of error messages.
What is all this about??!!
Why is Home Assistant such much work and effort, just to stand still?
Be practical and just sync the Synology sleep time for after the backup. Personally I would not run backup when the system might be directly interacting with a user.
luxia
(luxia)
February 1, 2026, 9:41pm
7
There is a bug report, but nothing has happened. i hope that someone can fix this issue with the accumulating repairs.
opened 05:05PM - 22 Jul 25 UTC
no-stale
### Describe the issue you are experiencing
I'm sharing a folder from my Window… s computer over the network for Home Assistant to put backup files in. Sometimes this computer goes offline (rebooting after installing a program or Windows Update). Then there's the 'Network storage device failed' notification in Home Assistant's settings menu by Home Assistant Supervisor. The problam is, when the connection repairs itself, there is no way to get rid of the notification(s). 'Remove' removes the network drive and 'Reload' fails and tells me to check the logs. In the logs I find the moment it lost connection but no new log entries from pressing the 'Reload' button or when the connection resumed again.
<img width="1236" height="1037" alt="Image" src="https://github.com/user-attachments/assets/5b1769aa-2261-4f74-a695-9671faf86522" />
<img width="1256" height="1434" alt="Image" src="https://github.com/user-attachments/assets/1e7ee595-d7a9-468a-b661-bad1c123ea67" />
### What type of installation are you running?
Home Assistant OS
### Which operating system are you running on?
Home Assistant Operating System
### Steps to reproduce the issue
1. Share a folder over the network with Home Assistant
2. Make the storage host go offline
3. Wait until you get the 'Network storage device failed notification' by Home Assistant Supervisor
4. Let the storage host go online
5. ...
### Anything in the Supervisor logs that might be useful for us?
```txt
2025-07-22 18:25:53.848 INFO (MainThread) [supervisor.mounts.manager] Reloading mount: DASWINDOOS2
2025-07-22 18:25:53.914 ERROR (MainThread) [supervisor.mounts.mount] Reloading DASWINDOOS2 did not succeed. Check host logs for errors from mount or systemd unit mnt-data-supervisor-mounts-DASWINDOOS2.mount for details.
2025-07-22 18:36:15.585 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state running
2025-07-22 18:36:15.585 INFO (MainThread) [supervisor.resolution.checks.base] Run check for ipv4_connection_problem/system
2025-07-22 18:36:15.586 INFO (MainThread) [supervisor.resolution.checks.base] Run check for disabled_data_disk/system
2025-07-22 18:36:15.586 INFO (MainThread) [supervisor.resolution.checks.base] Run check for trust/supervisor
2025-07-22 18:36:15.600 INFO (MainThread) [supervisor.resolution.checks.base] Run check for multiple_data_disks/system
2025-07-22 18:36:15.601 INFO (MainThread) [supervisor.resolution.checks.base] Run check for docker_config/system
2025-07-22 18:36:15.601 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_failed/dns_server
2025-07-22 18:36:15.675 INFO (MainThread) [supervisor.resolution.checks.base] Run check for security/core
2025-07-22 18:36:15.676 INFO (MainThread) [supervisor.resolution.checks.base] Run check for free_space/system
2025-07-22 18:36:15.680 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_ipv6_error/dns_server
2025-07-22 18:36:15.681 INFO (MainThread) [supervisor.resolution.checks.base] Run check for pwned/addon
2025-07-22 18:36:15.682 INFO (MainThread) [supervisor.resolution.check] System checks complete
2025-07-22 18:36:15.682 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state running
2025-07-22 18:36:15.966 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
2025-07-22 18:36:15.967 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state running
2025-07-22 18:36:15.968 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
2025-07-22 18:38:11.013 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
```
### System information
## System Information
version | core-2025.7.3
-- | --
installation_type | Home Assistant OS
dev | false
hassio | true
docker | true
container_arch | aarch64
user | root
virtualenv | false
python_version | 3.13.3
os_name | Linux
os_version | 6.12.35-haos
arch | aarch64
timezone | Europe/Brussels
config_dir | /config
<details><summary>Home Assistant Community Store</summary>
GitHub API | ok
-- | --
GitHub Content | ok
GitHub Web | ok
HACS Data | ok
GitHub API Calls Remaining | 5000
Installed Version | 2.0.5
Stage | running
Available Repositories | 2114
Downloaded Repositories | 6
</details>
<details><summary>Home Assistant Cloud</summary>
logged_in | false
-- | --
can_reach_cert_server | ok
can_reach_cloud_auth | ok
can_reach_cloud | ok
</details>
<details><summary>Home Assistant Supervisor</summary>
host_os | Home Assistant OS 16.0
-- | --
update_channel | stable
supervisor_version | supervisor-2025.07.1
agent_version | 1.7.2
docker_version | 28.3.0
disk_total | 28.0 GB
disk_used | 6.0 GB
healthy | true
supported | true
host_connectivity | true
supervisor_connectivity | true
ntp_synchronized | true
virtualization |
board | green
supervisor_api | ok
version_api | ok
installed_addons | Tailscale (0.25.0), Terminal & SSH (9.18.0), File editor (5.8.0), Mosquitto broker (6.5.1)
</details>
<details><summary>Dashboards</summary>
dashboards | 4
-- | --
resources | 2
views | 12
mode | storage
</details>
<details><summary>Network Configuration</summary>
adapters | lo (disabled), end0 (enabled, default, auto), hassio (disabled), docker0 (disabled), vethd71fc7b (disabled), veth3bec474 (disabled), vethb78bceb (disabled), veth6a15c5d (disabled), veth4f1d005 (disabled), veth10e05be (disabled), veth988083a (disabled)
-- | --
ipv4_addresses | lo (127.0.0.1/8), end0 (192.168.129.77/23), hassio (172.30.32.1/23), docker0 (172.30.232.1/23), vethd71fc7b (), veth3bec474 (), vethb78bceb (), veth6a15c5d (), veth4f1d005 (), veth10e05be (), veth988083a ()
ipv6_addresses | lo (::1/128), end0 (2a02:a03f:e888:7601:e79a:b566:197c:4f54/64, fe80::d34c:53ae:a86b:8f61/64), hassio (fe80::841:2fff:fead:bc99/64), docker0 (fe80::1095:cbff:fe31:6f67/64), vethd71fc7b (fe80::ccba:9bff:fe86:4584/64), veth3bec474 (fe80::a4e9:58ff:fe3e:a164/64), vethb78bceb (fe80::7c0d:b0ff:fe59:34ea/64), veth6a15c5d (fe80::6822:1ff:fe59:a754/64), veth4f1d005 (fe80::a8d0:c0ff:fee8:14f5/64), veth10e05be (fe80::749a:bdff:fe0b:3dca/64), veth988083a (fe80::8424:c1ff:feac:d329/64)
announce_addresses | 192.168.129.77, 2a02:a03f:e888:7601:e79a:b566:197c:4f54, fe80::d34c:53ae:a86b:8f61
</details>
<details><summary>Recorder</summary>
oldest_recorder_run | July 14, 2025 at 09:49
-- | --
current_recorder_run | July 22, 2025 at 15:27
estimated_db_size | 368.84 MiB
database_engine | sqlite
database_version | 3.48.0
</details>
### Supervisor diagnostics
_No response_
### Additional information
_No response_
Biscuit
(Geoff)
March 1, 2026, 12:12pm
8
As I often find with software changes that generate an issue, if you wait patiently the problem magically goes away of its own accord.
As of the latest update 2026.2.3, and very quietly, this irritant appears to have gone away. Until last week my HA had an orange number that effectively counted the number of days since I last rebooted HA. As of today, nothing. I am not even sure that it generates a message when the NAS drive shuts down for the night; I will have to stay up tonight just to see…
It would be nice to be back with a clean dashboard with no orange numbers!