I have a Raspberry Pi with osmc kodi on it. For more than one year i am mounting a cifs share from my NAS (shares on a Windows server 2013) to the OSMC. All good.
4 Days ago i updated Kodi and since that update, the cifs share won’t mount any more; not even manually when i issue mount -a.
This is my fstab entry: //10.2.2.249/MEDIA /mnt/MEDIA cifs rw,file_mode=0777,dir_mode=0777,noperm,credentials=/home/secret.txt,noauto,x-systemd.automount,iocharset=utf8 0 0
Can you give some hints on how to troubleshoot this?
I saw other similar posts where a solution was to add “vers=3” in my fstab entry, but in my case that does not solve it.
Besides the Kodi update, i haven’t made any other changes in my network or NAS.
Logs from grab-logs -A , here: https://paste.osmc.tv/duluxaviti
Not heard of this version, 2012 then 2016 I think?
Anyway seeing this in the logs:
Mar 09 20:51:00 raspi systemd: Mounting /mnt/MEDIA...
Mar 09 20:51:00 raspi kernel: No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount.
Mar 09 20:51:00 raspi kernel: CIFS VFS: protocol revalidation - security settings mismatch
Mar 09 20:51:00 raspi kernel: CIFS VFS: cifs_mount failed w/return code = -5
Mar 09 20:51:00 raspi systemd: mnt-MEDIA.mount: Mount process exited, code=exited status=32
Mar 09 20:51:00 raspi systemd: Failed to mount /mnt/MEDIA.
Mar 09 20:51:00 raspi systemd: mnt-MEDIA.mount: Unit entered failed state.
If that does’t work, try vers=2.1 or vers=1
If these work its probably just a case of configuring the server to support smbv3, then you return the flag to vers=3.0
I have windows 2012 standard version.
C:\Users\Administrator>systeminfo | findstr OS
OS Name: Microsoft Windows Server 2012 Standard
OS Version: 6.2.9200 N/A Build 9200
OS Manufacturer: Microsoft Corporation
OS Configuration: Standalone Server
OS Build Type: Multiprocessor Free
BIOS Version: Phoenix Technologies LTD 6.00, 21/9/2015
Got the same Problem on a ZyXel NSA 310 as NAS Server. Have you got a solution. I have workarounds within my configuration by tunneling data via another nearly pure Samba-Server. This is not very satisfying. Thanks. Like to here of somthing better
The IP addressed devices are noted as “No such Device” or similar if I try to get access via mount. At the moment i activated the software without the latest update. So if you need further information it will take some time.