LMDE 5 - Cannot automount Samba share from fstab

[claude_andre]

Hi – After HD failure I decided to switch from Linux Mint 21.1 to LMDE 5.
I now cannot automount Samba share from fstab.
My first attempt was to use the same fstab statement I had in Linux Mint 21.1, but this failed.
I am not an expert – I now have spent a couple days to find a possible solution without any luck.
Before giving up an rebuild a Linux Mint system, I would like to seek your help.
I search the web and tried many recommendations, but none worked.
My last fstab entry was:
“//192.168.0.1/TOSHIBAEXT /media/SDRIVE cifs vers=1.0,credentials=/home/claude/.smbcredentials,iocharset=utf8,gid=1000,uid=1000,file_mode=0777,dir_mode=0777 0 0”

At the completion of the boot, “dmesg” shows:
----------
FS-Cache: Netfs 'cifs' registered for caching
Key type cifs.spnego registered
Key type cifs.idmap registered
CIFS: Attempting to mount //192.168.0.1/TOSHIBAEXT
CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers
CIFS: VFS: Error connecting to socket. Aborting operation.
CIFS: VFS: cifs_mount failed w/return code = -101
-------------------
However, a “sudo mount -a” worked fine and a “mount” command shows:
--------------
/192.168.0.1/TOSHIBAEXT on /media/SDRIVE type cifs (rw,relatime,vers=1.0,cache=strict,username=claude,domain=WORKGROUP,uid=1000,forceuid,gid=1000,forcegid,addr=192.168.0.1,file_mode=0777,dir_mode=0777,soft,nounix,serverino,mapposix,rsize=61440,wsize=65536,bsize=1048576,echo_interval=60,actimeo=1)
----------------
On rare occasions the SAMBA share work.
Some of my attempts were:
//192.168.0.1/TOSHIBAEXT /media/SDRIVE cifs uid=1000,gid=1000,credentials=/home/claude/.smbcredentials,iocharset=utf8,vers=1.0,noauto,x-systemd.automount,x-systemd.mount-timeout=30,_netdev 0 0
---------------
//192.168.0.1/TOSHIBAEXT /media/SDRIVE cifs uid=1000,gid=1000,credentials=/home/claude/.smbcredentials,iocharset=utf8,vers=1.0,x-systemd.mount-timeout=60,sec=ntlm 0 0
------------

//192.168.0.1/TOSHIBAEXT /media/SDRIVE cifs uid=1000,gid=1000,credentials=/home/claude/.smbcredentials,iocharset=utf8,vers=1.0,auto,x-systemd.automount,x-systemd.mount-timeout=30 0 0
--------
//192.168.0.1/TOSHIBAEXT /media/SDRIVE cifs uid=1000,gid=1000,credentials=/home/claude/.smbcredentials,iocharset=utf8,vers=3.0,noauto,x-systemd.after=network-online.target,x-systemd.mount-timeout=30,_netdev 0 0


Many thanks, Claude

[claude_andre]

Hi - In desperation I added the following options:
",_netdev,x-systemd.after=network-online.target,"
however this did not help. (why is is it so hard?).
Claude

[altair4]

Does it have to automount?

I suspect the problem is your mount point is under /media which interacts with an internal process ( udisks ) and the share is mounting too early in the boot process.

Two possible options:

[1] Keep your current mount point but change your fstab declaration to this:

//192.168.0.1/TOSHIBAEXT /media/SDRIVE cifs vers=1.0,credentials=/home/claude/.smbcredentials,iocharset=utf8,gid=1000,uid=1000,file_mode=0777,dir_mode=0777,noauto,user 0 0

This will not automount on boot. Instead it will create a "launcher" on the side panel of your file manager that when selected will mount the share per your fstab instructions. You would always have to do this from your file manager to use the share.

[2] Change your mount point to be anyplace other than under your home directory or /media - like ...say .. /mnt and use the systemd automounter:

//192.168.0.1/TOSHIBAEXT /mnt/SDRIVE cifs vers=1.0,credentials=/home/claude/.smbcredentials,iocharset=utf8,gid=1000,uid=1000,file_mode=0777,dir_mode=0777,x-systemd.automount 0 0

EDIT: Forgot the x-systemd.automount in option [2]

[claude_andre]

Hi Altair,
Great! I used your second option and this solved my issue. Very much appreciated.
Many thanks.
Claude