Hello,
Every few hours I get “Network storage device failed”.
The network storage is attached to Raspberry Pi (OMV) and is normally accessible from local computers when HA comes up with this message.
After I hit “reload” the message disappears.
Anyone experienced something similar?
2 Likes
Me too . I have an old NAS storage server (seagate blackarmor) with SMBv1 and NFS shares, accessed over wired ethernet, and which is behaving exactly as you describe.
It turns out that although the repair appears to work, really it did not.
My network storage wouldn’t mount because the directory is not empty.
This is my backup location. It looks like the system may have taken a backup while the network storage was absent.
I’m getting this error today, it seems like it may have started after the latest HA OS update was installed. I normally back up to a Synology NAS. Did you manage to get this resolved, and if so could you let me know how please?
Cheers, Sam
I have moved to use GitHub - sabeechen/hassio-google-drive-backup: Automatically create and sync Home Assistant backups into Google Drive instead.
Happening here as well. Seems to have broken w/latest update.
having the same since days/weeks.
I am using a synology NAS
Where can I find the host logs suggested in this message?
I have found a Samba log.
Perhaps it is going to help find a reason.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.6.15 for name WORKGROUP<1d>.
This response was from IP 192.168.7.101, reporting an IP address of 192.168.7.101.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.6.15 for name WORKGROUP<1d>.
This response was from IP 192.168.7.101, reporting an IP address of 192.168.7.101.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.6.15 for name WORKGROUP<1d>.
This response was from IP 192.168.7.101, reporting an IP address of 192.168.7.101.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.6.15 for name WORKGROUP<1d>.
This response was from IP 192.168.7.101, reporting an IP address of 192.168.7.101.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.6.15 for name WORKGROUP<1d>.
This response was from IP 192.168.7.101, reporting an IP address of 192.168.7.101.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.6.15 for name WORKGROUP<1d>.
This response was from IP 192.168.7.101, reporting an IP address of 192.168.7.101.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.6.15 for name WORKGROUP<1d>.
This response was from IP 192.168.7.101, reporting an IP address of 192.168.7.101.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.6.15 for name WORKGROUP<1d>.
This response was from IP 192.168.7.101, reporting an IP address of 192.168.7.101.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.6.15 for name WORKGROUP<1d>.
This response was from IP 192.168.7.101, reporting an IP address of 192.168.7.101.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.6.15 for name WORKGROUP<1d>.
This response was from IP 192.168.7.101, reporting an IP address of 192.168.7.101.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.6.15 for name WORKGROUP<1d>.
This response was from IP 192.168.7.101, reporting an IP address of 192.168.7.101.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.6.15 for name WORKGROUP<1d>.
This response was from IP 192.168.7.101, reporting an IP address of 192.168.7.101.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.6.15 for name WORKGROUP<1d>.
This response was from IP 192.168.7.101, reporting an IP address of 192.168.7.101.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.6.15 for name WORKGROUP<1d>.
This response was from IP 192.168.7.101, reporting an IP address of 192.168.7.101.
And so on and on.
I have just experienced another issue, possibly after a power outage.
I cannot add existing disk storage.
By the way, there are some hints here but too difficult for me to grasp.
I recently started having this network storage problem too. After seeing these logs about 2 responses received, it made me realize that I recently installed a 2nd network card to have my server on both the LAN and a separate IoT network as well. I wonder if the 2 IP addresses are what is causing it.