drmullins
Posts: 43
Joined: Fri Jun 23, 2017 9:22 pm

Samba shares not mounting after kernel 4.14 upgrade ?

Sat Apr 14, 2018 12:13 pm

As noted in my earlier post, (auto)mounting of samba shares stopped working for me after upgrading from 4.9.80 to 4.14.30 kernel and I reverted to kernel 4.9.80.
viewtopic.php?f=66&t=210429

After further investigation it appears that the nominal samba protocol version is (intentionally ?) different between 4.9.80 and 4.14.30 kernel. This affects samba shares whether mounted via mount command, fstab or autofs. The only case I found where no change was required is where sharing is between raspberry pis.

Using autofs as an example and after some experimentation I found I had to change mount descriptions in my /etc/auto.sambashares as follows :

# Synology DS215J server automount
# kernel 4.9.80
#ds215j -fstype=cifs,rw,uid=${UID},guest ://DS215J/PUBLIC
# kernel 4.14.30
ds215j -fstype=cifs,rw,uid=${UID},guest,vers=2.0 ://DS215J/PUBLIC

# QNAP TS112 server automount
# kernel 4.9.80
#qnap112 -fstype=cifs,rw,uid=${UID},guest,sec=ntlm,nounix,noserverino ://QNAP112/Public
# kernel 4.14.30
qnap112 -fstype=cifs,rw,uid=${UID},guest,nounix,noserverino,vers=1.0 ://QNAP112/Public

# TP-LINK router USB drive automount
# kernel 4.9.80
#tplink -fstype=cifs,rw,uid=${UID},guest ://192.168.1.1/"volume(sda1)"
# kernel 4.14.30
tplink -fstype=cifs,rw,uid=${UID},guest,vers=1.0 ://192.168.1.1/"volume(sda1)"

# Windows XP guest share or Windows 7 guest share with full control access automount
# kernel 4.9.80
#asus2014 -fstype=cifs,rw,uid=${UID},user=guest,password="" ://ASUS2014/sharedntfs
# kernel 4.14.30
asus2014 -fstype=cifs,rw,uid=${UID},user=guest,password="",vers=1.0 ://ASUS2014/sharedntfs

# Raspberry Pi Samba share automount
# kernel 4.9.80 or kernel 4.14.30
raspi22 -fstype=cifs,rw,uid=${UID},guest ://raspi22/piShare

I just posted this for information as it might be useful to someone.

milhouse
Posts: 641
Joined: Mon Jan 16, 2012 12:59 pm

Re: Samba shares not mounting after kernel 4.14 upgrade ?

Sun Apr 15, 2018 7:10 pm

Yes this is intentional.

The default CIFS dialect negotiated by the 4.14.y kernel is now SMB 2.1 or better. This has been the case since 4.13.y.

The original kernel commit in 4.13.y defaulted to SMB 3.0 but this has since been toned down so that SMB 2.1 (introduced by Microsoft with Windows 7) is now the default.

You can configure a specific dialect with the "vers=1.0", "vers=2.0" etc. options.

Return to “Raspbian”