Issues with CIFS SMB 'Network' share on same computer mounting too quickly

Configuration
1

I get these annoying repair errors on HA 17.1 2026.2.2 - which won’t be dismissed without a restart, no even ‘reload’ after resolving it doesn’t make them go away!

Screenshot 2026-02-16 at 22.05.27
Screenshot 2026-02-16 at 22.05.271266×592 39.4 KB

Looking into it it’s because HA running in Virtualbox doesn’t wait to check if the mount is available later, I get cifs_mount failed with return code -2. But then the drive DOES become available, and works fine.

Ubuntu 24.04 the host OS sees the volume fine, other computers can write to it, etc etc.

In Ubuntu you can do this:

sudo systemctl enable systemd-networkd-wait-online
sudo systemctl enable systemd-networkd.service
sudo systemctl enable NetworkManager-wait-online.service

And I’ve done this in the host system now, but I suspect it won’t fix the problem cos HAOS will still boot up and try to look for that share too soon!

Only reason I am doing this is the frankly arcane and confusing lack of ability to properly mount shares in HAOS.

Looked into this for hours and it’s either crack open the systen and restore full root with a CONFIG USB (eek! rather not for security reasons) or put/extend HAOS on the big SMB share…but then I can’t use the drive for other devices or have to rely on someone else’s add-on, also not great for security.

I want to be able to edit the smb.conf and set proper user controls or groups if needed…not do that through a very noddy UI (yes I used SAMBAShare addon and it leaves a lot to be desired…also I don’t really want all my files in /media/ in an OS I don’t control - would rather have some separation there in case something goes down with the VM, not have all my files trapped inside a VM with an OS I have limited control over).

So is there a way of either delaying HA trying to access the Network drive on boot? Or a better way to add a CIFS Share without putting in gaping security holes or relying on a very basic add-on?

I have also tried to add the drive into a guest share in Virtualbox, that also is not seen, either mounted either in share or media. That should not have had the ‘network share delay’ issue because Ubuntu sees that natively…

1 Like
2

Are you having a VirtualBox problem? Maybe seek alternatives if it is unsurmountable?

3

No, I don’t think it’s a Virtualbox problem. In fact I couldn’t get KVM to work properly (I followed the official HA instructions and tried other tutorials because the VM instructions on the HA page are too brief and miss things, either way still refused to boot the HA image)

So I’d rather not go there…even with Cockpit (which I also tried). Virtualbox just works.

I suspect it would be even harder with KVM and mounts? Given all the posts here about KVM mount/network drive issues I see here?

I know KVM and Proxmox - I want an full OS I control as host, rather than a dedicated VM OS - are the ‘cool’ thing to use, but they aren’t exactly easy to setup.

And I feel Docker and containers are a bit like the OpenVPS of old which I used to have major issues with before moving to KVM servers (so I use them, just don’t know how to set them up) and related security issues. Also I use add-ons and the app store, which isn’t available in the Docker version?

I personally think VM is the most secure way, sharing resources or kernels for me feels a bit too insecure.

4

I also have the same issue with , seems like 2026.2.2 broke Network storage with Samba/Windows (CIFS). Please update if you found a fix or a workaround…

1 Like
5

Any report in GitHub to let the developers know there is an issue?

6

I couldn’t find any open issues regarding this… Waiting for an update to HASS

1 Like
7

Unless the developers accidentally stumble over your bug, they probably won’t fix it or release a new version without a bug report.
In GitHub.

8

Hi, so I figured out that it was a mounting problem for my SSD and restarting the server fixed the issue… Weird since Samba was sharing the mount but HASS was throwing an I/O error when trying to read from the SSD.

9

Yes I didn’t have problems with SMB generally, just this issue with not waiting for network discoverability or being able to dismiss the repairs. Is that a bug? I dunno.

Been told off for raising ‘wrong’ bug reports on other Github projects before, so wary of doing that. The cutlure on Github is not n00b or non-dev friendly. The point is if I’m not a developer I have no idea whether something is a bug or just an issue with my setup or an outlier…so asking non-devs to know the difference is a big ask.