This may be the same issue I've had in the past. It's poorly documented, and IMHO buggy. I wasted a week on this ~ 3 years ago - including the bug reports submitted to Raspberry Pi, and then to Debian which were ignored.
Anyway - in my case the issue was unique to the software that handles SMB/CIFS mounts (network drives typically) from
fstab. As it turns out, there are several versions of SMB; you can see a list of these in
man mount.cifs. And - at least in my case - getting the correct version was crucial to a successful mount (consummation? :).
It's still painful to recall (mostly due to how my bug report was handled), and AFAIK it's still buggy. The point of this post is only my effort to raise awareness that when it comes to SMB mounts - version matters.
fstab specification that I'm still using; note the placement of the
//NetgearNAS-3/backup /mnt/NetgearNAS-3/backup cifs rw,username=seamus,password=XXXXXXXX,nofail,vers=1.0 0 0
You may be wondering how to determine the SMB protocol version (I did). On a Windows machine, that is said to be available from the "Power Shell" using the command:
Get-SmbConnection. On a Linux server (Samba), this should work:
sudo smbstatus. If you're using a network appliance (as I am) as a SMB/CIFS file server, you may have to resort to trial-and-error.