Problems mounting shares at boot with fstab
by road hazard from LinuxQuestions.org on (#52V6K)
I have a server running Linux Mint 19.3. It has various directories shared out via Samba. I can access those shares from anything in my house so I think that's good to go.
I have a headless box running Mint 19.2 that is an FTP server that people can log into and it has mounts that point to the 19.3 server box and all is well. Shares on the 19.2 headless FTP server are mounted via fstab:
Code://192.168.1.5/Classic\040cars /mnt/classic_cars cifs username=anonymous,password=anonymous,iocharset=utf8 0 0
//192.168.1.5/Friends /mnt/friends cifs username=anonymous,password=anonymous,iocharset=utf8 0 0
//192.168.1.253/crap /mnt/asus_test cifs username=anonymous,password=anonymous,iocharset=utf8 0 0From the FTP box, Classic cars and Friends works fine. The only problem is the last one... the .253/crap share. 253 is my test Debian 10 box. Here is the SMB.conf file from my Debian 10 test box:
Code:[crap]
path = /mnt/crap/
read only = yes
guest ok = yes
guest only = yes
map to guest = bad userI'm sharing out the /mnt/crap folder on the Debian 10 box (192.168.1.253). I can see this share from any and all boxes in my house. But when I try to map it via the fstab file on the headless FTP server, it's not mounting at boot. If I start X on the FTP server and login to the GUI and go to the Network icon, I can see my Debian 10 test box and I can see the 'crap' folder and I can open it up anonymously and see the files inside perfectly. What am I missing with the fstab mounting at boot?
I see this in dmesg on the FTP server when it boots:
Code:[ 15.257176] 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.
[ 15.263147] 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.
[ 15.270375] 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.So I tried adding vers=1.0 for the 'crap' mount and it made no difference. Heck, I get that same error for the other 2 shares and they seem to work fine so maybe that's a red herring?
I have a headless box running Mint 19.2 that is an FTP server that people can log into and it has mounts that point to the 19.3 server box and all is well. Shares on the 19.2 headless FTP server are mounted via fstab:
Code://192.168.1.5/Classic\040cars /mnt/classic_cars cifs username=anonymous,password=anonymous,iocharset=utf8 0 0
//192.168.1.5/Friends /mnt/friends cifs username=anonymous,password=anonymous,iocharset=utf8 0 0
//192.168.1.253/crap /mnt/asus_test cifs username=anonymous,password=anonymous,iocharset=utf8 0 0From the FTP box, Classic cars and Friends works fine. The only problem is the last one... the .253/crap share. 253 is my test Debian 10 box. Here is the SMB.conf file from my Debian 10 test box:
Code:[crap]
path = /mnt/crap/
read only = yes
guest ok = yes
guest only = yes
map to guest = bad userI'm sharing out the /mnt/crap folder on the Debian 10 box (192.168.1.253). I can see this share from any and all boxes in my house. But when I try to map it via the fstab file on the headless FTP server, it's not mounting at boot. If I start X on the FTP server and login to the GUI and go to the Network icon, I can see my Debian 10 test box and I can see the 'crap' folder and I can open it up anonymously and see the files inside perfectly. What am I missing with the fstab mounting at boot?
I see this in dmesg on the FTP server when it boots:
Code:[ 15.257176] 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.
[ 15.263147] 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.
[ 15.270375] 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.So I tried adding vers=1.0 for the 'crap' mount and it made no difference. Heck, I get that same error for the other 2 shares and they seem to work fine so maybe that's a red herring?