Network Storage SMB/CIFS compatibility issue/not working with some servers HAOS 14.2/15

[radulyz]

trafficstars

Describe the issue you are experiencing

I noticed only after updating to HAOS 15: I'm running into trouble connecting to my Mikrotik NAS: SMB/CIFS connection from the Storage/Network Storage setting of the HA... Since the update even tho the Mikrotik server logs show a successful login from HA, the network storage doesn’t work. (CIFS protocol, server, share, user and password are all good, the server is confirming that) Current system: OS version: 15; HA core: 2025.3.3

From the logs:

2025-03-17` 22:00:12.932 homeassistant systemd[1]: Mounting Supervisor cifs mount: MikrotikSMB…
2025-03-17 22:00:12.946 homeassistant kernel: CIFS: Attempting to mount [//192.168.30.8/backup-ha] https://192.168.30.8/backup-ha)
2025-03-17 22:00:13.074 homeassistant kernel: CIFS: VFS: cifs_read_super: get root inode failed
2025-03-17 22:00:13.081 homeassistant mount[20512]: mount error(13): Permission denied
2025-03-17 22:00:13.081 homeassistant mount[20512]: Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
2025-03-17 22:00:13.085 homeassistant systemd[1]: mnt-data-supervisor-mounts-MikrotikSMB.mount: Mount process exited, code=exited, status=32/n/a
2025-03-17 22:00:13.086 homeassistant systemd[1]: mnt-data-supervisor-mounts-MikrotikSMB.mount: Failed with result ‘exit-code’.
2025-03-17 22:00:13.086 homeassistant systemd[1]: Failed to mount Supervisor cifs mount: MikrotikSMB.

After downgrading OS to 14.2 the problem still exists... I can't exactly pinpoint when the problem started, I know it worked with the same server before maybe half a year ago, I tested it, but I chose not to use the functionality at that point. Interestingly, the Samba Backup AddOn is working with no issues with the same credentials and the same share/Mikrotik NAS.

What I noticed is that If in the Windows Group Policy [Network security: LAN Manager authentication level] is set to any of the following

- Send LM & NTLM responses
- Send LM & NTLM - use NTLMv2 session security if negotiated
- Send NTLM responses only

The Mikrotik NAS will behave the same way as with the HA when it tries to connect to it (unsuccessfully) but when the [Network security: LAN Manager authentication level] is set to either of the following:

- Send NTLMv2 responses only
- Send NTLMv2 responses only. Refuse LM
- Send NTLMv2 responses only. Refuse LM & NTLM
- Not Defined

The windows machine will connect with no issues to the Mikrotik NAS... So the HA might also have something to do with these communication protocol settings.

Any suggestion where I could change any of these settings in the HA to get the Network Storage working again?

What operating system image do you use?

rpi4-64 (Raspberry Pi 4/400 64-bit OS)

What version of Home Assistant Operating System is installed?

15

Did the problem occur after upgrading the Operating System?

Yes

Hardware details

PI4, 8GB RAM, 120GB Kingston SSD is used for the operating system (HAOS)

Steps to reproduce the issue

1. Tried downgrading HAOS to 14.2, but not sure from which version the problem started I just know it worked 2024 November
2. Tried to connect from the same system with Samba Backup AddOn: that's working with no issues, but I cannot use that in the system as an automatic backup option
3. Tested the NAS in various scenarios to see what the issue could be, it seems like a communication protocol issue. ...

Anything in the Supervisor logs that might be useful for us?

2025-03-17` 22:00:12.932 homeassistant systemd[1]: Mounting Supervisor cifs mount: MikrotikSMB…
2025-03-17 22:00:12.946 homeassistant kernel: CIFS: Attempting to mount [//192.168.30.8/backup-ha] https://192.168.30.8/backup-ha)
2025-03-17 22:00:13.074 homeassistant kernel: CIFS: VFS: cifs_read_super: get root inode failed
2025-03-17 22:00:13.081 homeassistant mount[20512]: mount error(13): Permission denied
2025-03-17 22:00:13.081 homeassistant mount[20512]: Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
2025-03-17 22:00:13.085 homeassistant systemd[1]: mnt-data-supervisor-mounts-MikrotikSMB.mount: Mount process exited, code=exited, status=32/n/a
2025-03-17 22:00:13.086 homeassistant systemd[1]: mnt-data-supervisor-mounts-MikrotikSMB.mount: Failed with result ‘exit-code’.
2025-03-17 22:00:13.086 homeassistant systemd[1]: Failed to mount Supervisor cifs mount: MikrotikSMB.

Anything in the Host logs that might be useful for us?

2025-03-17` 22:00:12.932 homeassistant systemd[1]: Mounting Supervisor cifs mount: MikrotikSMB…
2025-03-17 22:00:12.946 homeassistant kernel: CIFS: Attempting to mount [//192.168.30.8/backup-ha] https://192.168.30.8/backup-ha)
2025-03-17 22:00:13.074 homeassistant kernel: CIFS: VFS: cifs_read_super: get root inode failed
2025-03-17 22:00:13.081 homeassistant mount[20512]: mount error(13): Permission denied
2025-03-17 22:00:13.081 homeassistant mount[20512]: Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
2025-03-17 22:00:13.085 homeassistant systemd[1]: mnt-data-supervisor-mounts-MikrotikSMB.mount: Mount process exited, code=exited, status=32/n/a
2025-03-17 22:00:13.086 homeassistant systemd[1]: mnt-data-supervisor-mounts-MikrotikSMB.mount: Failed with result ‘exit-code’.
2025-03-17 22:00:13.086 homeassistant systemd[1]: Failed to mount Supervisor cifs mount: MikrotikSMB.

System information

System Information

version	core-2025.3.3
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
user	root
virtualenv	false
python_version	3.13.2
os_name	Linux
os_version	6.6.62-haos-raspi
arch	aarch64
timezone	America/Edmonton
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	1660
Downloaded Repositories	16

Home Assistant Cloud

logged_in	true
subscription_expiration	December 31, 2017 at 17:00
relayer_connected	false
relayer_region	null
remote_enabled	false
remote_connected	false
alexa_enabled	true
google_enabled	true
cloud_ice_servers_enabled	true
remote_server	null
certificate_status	null
instance_id	522ea45401b84655b89d624f3bf4c2fe
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Home Assistant Supervisor

host_os	Home Assistant OS 14.2
update_channel	stable
supervisor_version	supervisor-2025.03.3
agent_version	1.6.0
docker_version	27.2.0
disk_total	219.4 GB
disk_used	14.2 GB
healthy	true
supported	true
host_connectivity	true
supervisor_connectivity	true
ntp_synchronized	true
virtualization
board	rpi4-64
supervisor_api	ok
version_api	ok
installed_addons	Samba share (12.5.0), Node-RED (19.0.2), Terminal & SSH (9.16.0), WireGuard (0.11.0), File editor (5.8.0), Grafana (10.4.2), InfluxDB (5.0.2), Samba Backup (5.2.0), Studio Code Server (5.18.3), ESPHome Device Builder (2025.2.2), Duck DNS (1.18.0), NGINX Home Assistant SSL proxy (3.11.1), Silicon Labs Multiprotocol (2.4.5), Matter Server (7.0.0), Mosquitto broker (6.5.0), Piper (1.5.2), Whisper (2.4.0)

Dashboards

dashboards	2
resources	8
views	6
mode	storage

Network Configuration

adapters	lo (disabled), wlan0 (enabled, default, auto), hassio (disabled), docker0 (disabled), veth994c03e (disabled), vethd49bde0 (disabled), vethe5609cb (disabled), vetha9778cc (disabled), veth57ddbfd (disabled), veth90d1722 (disabled), veth57c8c56 (disabled), veth3a2d8fd (disabled), vethb983e13 (disabled), vethfc13319 (disabled), vethcf546fd (disabled), wpan0 (disabled), vethd4a0479 (disabled), vethf820688 (disabled), vethc138276 (disabled)
ipv4_addresses	lo (127.0.0.1/8), wlan0 (192.168.30.11/24), hassio (172.30.32.1/23), docker0 (172.30.232.1/23), veth994c03e (), vethd49bde0 (), vethe5609cb (), vetha9778cc (), veth57ddbfd (), veth90d1722 (), veth57c8c56 (), veth3a2d8fd (), vethb983e13 (), vethfc13319 (), vethcf546fd (), wpan0 (), vethd4a0479 (), vethf820688 (), vethc138276 ()
ipv6_addresses	lo (::1/128), wlan0 (fe80::c576:9f87:aace:654/64), hassio (fe80::42:84ff:fefa:93ab/64), docker0 (fe80::42:3bff:fe16:5afd/64), veth994c03e (fe80::2845:e2ff:fee7:1e72/64), vethd49bde0 (fe80::2c8c:5cff:fe24:a68a/64), vethe5609cb (fe80::b0f1:c9ff:fe75:cf26/64), vetha9778cc (fe80::ac9a:edff:fea7:ba46/64), veth57ddbfd (fe80::40d5:36ff:fe9b:5d45/64), veth90d1722 (fe80::2841:5bff:fe22:bc0b/64), veth57c8c56 (fe80::f49e:96ff:fe92:e140/64), veth3a2d8fd (fe80::837:d1ff:feba:f267/64), vethb983e13 (fe80::346e:28ff:fe0f:e04/64), vethfc13319 (fe80::1057:61ff:fe45:a226/64), vethcf546fd (fe80::9882:46ff:fea1:93e7/64), wpan0 (fdcf:c870:d009:c9fd:0:ff:fe00:fc11/64, fd87:1d93:d25e:1:460d:3272:7b12:84be/64, fdcf:c870:d009:c9fd:0:ff:fe00:fc10/64, fdcf:c870:d009:c9fd:0:ff:fe00:fc38/64, fdcf:c870:d009:c9fd:0:ff:fe00:fc00/64, fdcf:c870:d009:c9fd:0:ff:fe00:3000/64, fdcf:c870:d009:c9fd:ddd7:eab2:f671:65c7/64, fe80::b48f:4e9e:763e:a7ae/64), vethd4a0479 (fe80::60e4:7cff:feb8:6486/64), vethf820688 (fe80::400:a3ff:fe05:cece/64), vethc138276 (fe80::401:2fff:fe7d:917e/64)
announce_addresses	192.168.30.11, fe80::c576:9f87:aace:654

Recorder

oldest_recorder_run	September 18, 2024 at 14:36
current_recorder_run	March 18, 2025 at 00:34
estimated_db_size	595.42 MiB
database_engine	sqlite
database_version	3.48.0

Sonoff

version	3.8.2 (c4b6fda)
cloud_online	7 / 10
local_online	1 / 1

Additional information

NAS Server LOGs on successful login when using Samba Backup AddOn (when the backup was performed: ~450MB):

NAS Server LOGs on UNsuccessful connection when using the Network Storage (even tho the login is OK, still error from the HA on 2 separate ocations):

[supperka]

also have problems with samba connection, to my share disk.

Logger: homeassistant.components.hassio
Zdroj: components/hassio/websocket_api.py:141
integrace: Home Assistant Supervisor (dokumentace, problémy)
První výskyt: 20:41:33 (12 výskyty)
Naposledy logováno: 20:55:40

Failed to to call /mounts/share - Mounting share did not succeed. Check host logs for errors from mount or systemd unit mnt-data-supervisor-mounts-share.mount for details.

Failed to to call /mounts/share - Mounting share did not succeed. Check host logs for errors from mount or systemd unit mnt-data-supervisor-mounts-share.mount for details. Hour before update all works great.

[brugk000]

I have the same error. After an unsuccesfull update to 15.0 there was a problem connecting a samba share to my Unraid server. After removing the share in HAOS, I am having this errors now: 2025-03-19 10:55:22.705 WARNING (MainThread) [supervisor.addons.options] Option 'interface' does not exist in the schema for Samba share (core_samba)

[TrilIiard]

Same errors on rpi4 4gb with 15.0, smb stopped working. Sadly it's not even possible to go back to previous version with existing backups. No matter how old the backup is, a day (14.3) or a month (14.1) it doesn't restore to that version and always reboots to 15.0. In the last months it looks like they stopped testing new version updates like 13.0, 14.0 and 15.0 before publishing them. There are allways bugs that are related to main functionality which would be easy to find if they would test the updates. Maybe everybody should stop updating main version with x.0 and allways wait for the x.1 updates 😂

[supperka]

Version 15.1 isn't fix my problem.

[radulyz]

Yeah, the issue persists. I don't know where it comes from or if it's from HA or HAOS. As I said, with the same server credentials (and server), Samba Backup (v 5.2.0) works without issues. 90% is from the [Network security: LAN Manager authentication level] communication mismatch...

[1kemp]

After the upgrade to HAOS 15.0 my network storage CIFS to a WIN11 machine stopped working. If I try to re-add the storage I get this error

2025-04-17 16:23:13.544 homeassistant systemd[1]: Mounting Supervisor cifs mount: TapoRecordings... 2025-04-17 16:23:13.547 homeassistant kernel: CIFS: Attempting to mount //192.168.0.106/TapoRecordings 2025-04-17 16:23:13.605 homeassistant kernel: CIFS: VFS: cifs_read_super: get root inode failed 2025-04-17 16:23:13.608 homeassistant mount[209966]: mount error(95): Operation not supported 2025-04-17 16:23:13.608 homeassistant mount[209966]: Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) 2025-04-17 16:23:13.609 homeassistant systemd[1]: mnt-data-supervisor-mounts-TapoRecordings.mount: Mount process exited, code=exited, status=32/n/a 2025-04-17 16:23:13.609 homeassistant systemd[1]: mnt-data-supervisor-mounts-TapoRecordings.mount: Failed with result 'exit-code'. 2025-04-17 16:23:13.610 homeassistant systemd[1]: Failed to mount Supervisor cifs mount: TapoRecordings.

Mounting the same with the same credentials works on my Proxmox Server works without issue.

[HarriVa]

After the upgrade to HAOS 15.0 my network storage CIFS to a WIN11 machine stopped working. If I try to re-add the storage I get this error

After HAOS upgrade I have the same problem with Win 11 machine, but strangely it only happens when I share an OneDrive folder from Windows. Non-OneDrive folder shares are accessible from HAOS.

[techjunkie91]

After HAOS upgrade I have the same problem with Win 11 machine, but strangely it only happens when I share an OneDrive folder from Windows. Non-OneDrive folder shares are accessible from HAOS.

I get the same issue. Any folder outside of the OneDrive location works fine.

[github-actions[bot]]

There hasn't been any activity on this issue recently. To keep our backlog manageable we have to clean old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant OS 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.