Can't clear 'Network storage device failed' notification

[MaxVMH]

Describe the issue you are experiencing

I'm sharing a folder from my Windows 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.

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?

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

Home Assistant Community Store

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

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 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)

Dashboards

dashboards	4
resources	2
views	12
mode	storage

Network Configuration

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

Recorder

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

Supervisor diagnostics

No response

Additional information

No response

[kluner]

I essentially have this with my QNAP. As most energy slurpers, I shutdown a lot of it (often with HA) during the night, when it does not get used. Naturally, home assistant complains about this. But there seems no way to recover except a full core restart.

Since the network storage component does not have entities or anything, it’s also not possible to trigger it to retry at a time when the storage should be online again.

[sbR569]

Pump! I turn off my backup storage for energy saving. Sometimes HA does not have any problems with it but often I have to add my storage again after connection loss. Would suggest to implement a simple checkbox for this case or a time range where I can choose when the external storage will come back online.

[goodlucknow]

Huge pain point for me at the moment. Frequent power cuts in the area and my system can't fully come back online without intervention.

[Geweldich]

It would be nice to be able to dismiss this notification. Especially after the problem has already been solved (connection restored)...

[agners]

It would be nice to be able to dismiss this notification. Especially after the problem has already been solved (connection restored)...

When the connection got restored, the notification should indeed disappear on its own. What type of network storage do you use (NFS/smbfs)?

[kluner]

smbfs for me.

Funny enough,I noticed once in the last 7 days the alert vanished on its own accord. So it does seem like there is code there for it, that just triggers erratically.

[Geweldich]

It would be nice to be able to dismiss this notification. Especially after the problem has already been solved (connection restored)...

When the connection got restored, the notification should indeed disappear on its own. What type of network storage do you use (NFS/smbfs)? NFS

The message has also vanished on my install. Perhaps another thing to mention/research: the notification featured two fixes (if I remember correctly), both of which errored out when applying.

Because a storage outage is extremely unlikely for me I'm not really invested in this issue, but hopefully this extra info helps.

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[WarmChocolateCake]

Just found this issue - perhaps a little late as it went stale.

My NAS powers up & down multiple times during the day so I have 2 of these messages for the same device most of the time.

I'm using NFS and it's mounted for backups:

It looks like the scheduled automatic backups are working, so stating that the Network Storage Device Failed isn't really an accurate message. It should also be mutable as I'm happy that this "fails". (I'd like to know if the backup failed - but that's a separate point).

[kluner]

It's a bit of a mystery to me why this went stale. It was recent with plenty of comments suggesting it was an ongoing issue. (but not of the greatest urgency / importance - since it does work, it's just an annoyance).

the interesting thing is that there does seem to be some recovery mechanism present, since it does occasionally recover without intervention. I would rate that 1 out of 10 times. The other 9 I restart HA to remove the error.

If I do not remove the error by restarting? The backup still functions perfectly.

[fernbrun]

Same issue for me. I shutdown my NAS during night. So the issue comes and don't leave until I restart HA.

[stormshaker]

An issue for me, too. Whenever I stop the NAS array, this repair is notified. Reload won't clear it, but a Home Assistant restart will.

[kepstin]

I've been running into this issue (or something that seems similar) as well, triggered by https://github.com/home-assistant/supervisor/issues/5486 - If I catch it fairly soon after the system boots up and use the "repair" option, it usually successfully mounts the network storage. But if I don't catch it immediately, and the system has been running for a while, the "repair" option won't work, and the only solution I've been able to find is to restart the entire system and try again.

[jam3sward]

Likewise, I have my NAS drive scheduled to shut down for a period overnight, for energy saving. It's scheduled to wake up before Home Assistant does its scheduled backup. However, I get this warning and there seems no way to disable it. I would really appreciate some option to disable the warning, or a checkbox to let Home Assistant know that the network drive may be unavailable.

[fernbrun]

This is very painful, indeed. I tried to script the mount of network shares, but it doesn't work. Anybody as a workaround ?

[jam3sward]

I agree this is pretty annoying as I seem to get multiple warnings about it, and can't even dismiss the warnings. I don't want to leave my NAS drive on 24/7 not just because of energy use, but because the humming noise it makes disturbs our sleep! The only real workaround I could think of would be to disable the network drive in Home Assistant, and just write a shell script to manually duplicate the local backups to the network drive on a cron job or something.

[JasMan78]

Before 2025.11 I was able to "confirm" the network storage fixes by searching for updates when the NAS was online again. Also, it only appeared one message which was updated each time the NAS was offline again. But now I'm getting a new/additional message each time my NAS is offline, and it's no longer possible to "confirm" them by searching for updates.

[joseftw]

Same here, really annoying. My NAS is only running during the nights for backups etc. Would be awesome if we could ignore the notifications/clear the notifications when the NAS comes back up.

[bobbyandck]

Same problem here, hope they reopen the issue ! It would be great to have an option to ignore when a drive goes offline.

[lwheeler]

You should at least be able to easily remove the message. I have 5 of these messages right now that I can't clear.

[tonybaroneee]

Big +1, super annoying.

[jam3sward]

I think we might need to create a new issue to get attention on this, as this one was closed on Sep 28th. There's a related bug #6193 still open.

[WarmChocolateCake]

I've updated my issue on #6193, so if this thread's dead, I'll continue over there...

[CommanderTux]

Same issue here (also related to #6193). I’m using NFS storage over a WireGuard tunnel. After a reboot the error clears, but an even faster workaround is running ha supervisor restart — the message disappears within a minute.

[TheHawkAU]

Same issue here since switching to a new NAS, I'm guessing it must ping it periodically and if for some reason its not responded, that message stays there, BUT the backup works as long as when it's actually being used it works.

Restarting the Supervisor seems to clear the message (after a short period) without having to go through a reboot cycle.

Run this command in terminal: ha supervisor restart

[josephazrak]

Same issue. Really just adding a 'dismiss' button would go 99% of the way.

[ma9mwah]

Just adding that I get the same, my NAS shuts down during the night after HA finishes its backup to it. No way of removing the errors notifaction without a full restart.

[DP-Projects-be]

"I'm experiencing the same issue — my NAS powers off overnight right after Home Assistant completes its backup. After that, the error notification sticks around and the only way to clear it is to reboot the system."

[CBK482]

+1

[omian]

I'm having the same issue. My NAS is scheduled to shut down at certain times and when this happens I get this notification in home assistant. I feel there are two separate issues

1. It doesn't seem possible to dismiss/clear the notification. To get rid of it I have to restart Home Assistant.
2. It would be good if there were an option to disable this notification from displaying in the first place. Whilst I do want a notification if something fails because it can't reach the network storage location (e.g. a scheduled backup), I don't need/want a notification every time the network folder goes offline.