This is driving me absolutely batty. I have two shares:
[applications] comment = applications path = /mnt/applications browseable = yes read only = no guest ok = no valid users = andrew create mask = 0770 [media] comment = media path = /mnt/media writeable = yes public = yes guest ok = yes create mask = 0777
I have a VM with the following fstab:
//192.168.50.232/media /mnt/media cifs vers=3.0,rw,noserverino,users,_netdev,credentials=/root/.smbcredentials,x-systemd.automount,noauto 0 0 > //192.168.50.232/applications /mnt/applications cifs vers=3.0,users,credentials=/root/.smbcredentials,_netdev,x-systemd.automount,noauto 0 0
(I know, the mounts are ugly, but it took a lot of trial and error to get the setup functional and I didn't want to break anything by cleaning it)
This was working fine, until I needed to move everything to a new SSD. After restoring everything from backups, Media mount won't automount. I get the following during boot:
[FAILED] Failed to mount /mnt/media CIFS: VFS: Error connecting to socket. Aborting operation. CIFS: VFS: cifs_mount failed w/return code = -101
The Applications mount has zero issues auto-mounting.
'sudo mount -a' doesn't give any response.
When I manually mount using:
mount //192.168.50.232/media /mnt/media
I am asked for password and once I enter it the share mounts just fine.
Has anybody seen something like this?