Network storage device failed on HASS OS

[Vandana (Vandana Dass)]

Hi,

Recently migrated from Homeassistant Supervised to Homeassistant OS. Running on raspberrypi 4b.

I have connected an external USB for backup. But after every restart of raspberrypi. I get the above warning. Even if I dont repair it the backup is successful.

Any fix to remove this warning? What am I doing wrong here?

Kindly guide.

[Mixam]

I’m having a similar issue I think, I share a Windows folder with Home Assistant Green and get the same error. “Reload” doesn’t work (I get “Could not apply the fix. Check the Supervisor logs for more details.”) and the notification won’t disappear until I restart Home Assistant.

In the supervisor logs I find this at the time of the reboot:

2025-07-20 11:22:10.266 INFO (MainThread) [supervisor.mounts.manager] Creating or updating mount: DASWINDOOS2

2025-07-20 11:22:12.542 ERROR (MainThread) [supervisor.mounts.mount] Mounting DASWINDOOS2 did not succeed. Check host logs for errors from mount or systemd unit mnt-data-supervisor-mounts-DASWINDOOS2.mount for details.

2025-07-20 11:22:28.745 INFO (MainThread) [supervisor.mounts.manager] Creating or updating mount: DASWINDOOS2

2025-07-20 11:22:28.988 INFO (MainThread) [supervisor.backups.manager] Found 12 backup files

So I assume that at 11:22:10-12 it fails to connect because the machine is rebooting and at 11:22:28 it automaticaly re-connects. But the notification remains and I can’t get rid of it.

[Vandana (Vandana Dass)]

Is there no solution to this?

[Mixam]

Only thing that works for me is waiting a long time, or restarting Home Assistant.

I think next to ‘remove’ and ‘reload’ there should be a ‘clear’ or ‘acknowledge’ button, or integrate that in the reload button.

It’s not really a problem that breaks functionality but the menu gets cluttered when my Windows computer restarts multiple times in a day.

[Vandana (Vandana Dass)]

I agree.

After restart Homeassistant should check again for the storage and if found ot should clear the warning automatically.

Has anyone reported this on github ?

[Mixam]

I don’t know if everyone will agree to have the warning clear automatically - especially people who have their network storage connected 24/7, I think they want to know about (even short) outages.

Being able to manually clear the error (having a clear button or including in the reload button) would be a better option imo.

I searched for this issue on GitHub but then I saw version 2025.7.3 is right around the corner so I was meaning to test that before opening a new issue.

[Vandana (Vandana Dass)]

Fair enough.

If not automatically. They could let us clear it via an automation.

[sora0kuro]

Hi!

Same “problem” here.

I connected a shared folder from my windows pc as a storage in HA, so it performs an automatic backup once a month on the external pc (by waking it up via WOL before the backup). It’s working fine, but the rest of the time I use the windows pc as a normal pc, resulting in a lot of warnings from HA whenever it goes offline.

(all 17 are the same warning: Network storage device failed)

No matter if I click “reload” or “remove”, I cannot get rid of them, just by restarting the whole HA.

It’s not a big problem, just really annoying to always see so much warnings in my settings (and always need to check if somewhere between them might be a “real” warning, I should react to)
If it would be possible to somehow clear them (even if I have to do it manually), it would be great!

Have you already opened an issue on gitHub, where I can contribute to?

[Vandana (Vandana Dass)]

No not opened yet. Really busy with work lately. If you want please open the issue on github and share the link here.

[AutoT]

Looks like the issue was opened on github in July, but it went stale as no-one was looking at it and is now closed:

Can't clear 'Network storage device failed' notification

[jm314159 (Jerzy)]

So, I experience the same issue…
My solution, instead of restarting HA as a whole, is to just restart supervisor in terminal:

ha supervisor restart

After that, the messages disappear until the next sleep time of my NAS, unfortunately.

[jm314159 (Jerzy)]

Should anyone be interested in the working workaround, please have a look into GitHub HA Supervisor issue #6193. I have described it in there.

[tim.plas]

I’ve also had occasional issue with storage repair not clearing via either Reload or Remove, e.g., after extended power outage affecting NAS but not HA (in other building).

I’ve found that I can clear it without restart, by re-entering credentials:
Settings – System – Storage – Network Storage – [share name] – then enter Username and Password, and click Update.

[digin]

Blockquote
I’ve found that I can clear it without restart, by re-entering credentials:
Settings – System – Storage – Network Storage – [share name] – then enter Username and Password, and click Update.

Does not work for me. Restarting HA solved this issue temporary, until the NAS will shut down for a while.

[unglazedswansea]

I have now successfully resolved this issue with the following workaround.

Insert into configuration.yaml

Create a new automation with a sensor to check whether the NAS has been successfully reloaded – optionally remove the notification.

In your configuration.yaml

shell_command:

supervisor_restart: ‘curl -X POST -H “Authorization: Bearer $SUPERVISOR_TOKEN” http://supervisor/supervisor/restart’

Automation:

alias: “Fix: Reload mounts when NAS is online”

description: “Restarts the supervisor to repair network mounts when the NAS returns.”

trigger:

• platform: state

entity_id: binary_sensor.synology_nas_ping # Adjust this entity ID to match your ping sensor

from: “off”

to: “on”

for: “00:02:00” # Wait 2 minutes to ensure all services on the NAS are ready

condition:

action:

• service: shell_command.supervisor_restart

data: {}

• service: notify.persistent_notification

data:

message: “NAS is back. Supervisor has been restarted to repair mounts.”

title: “Network Storage Fix”

mode: single

[RayLation]

I tested this idea manually by restarting the supervisor from the CLI. It did indeed clear the notification!

Before actually using the automation, I’d love to understand how the supervisor_restart command actually works…? why use curl? what’s this $SUPERVISOR_TOKEN ? what is behind http://supervisor/supervisor/restart ?

Thank you!