Troubleshooting • Re: Latest ver of RaspiOS has problem mounting legacy NAS via fstab

//192.168.1.xxx/xxx /xxx cifs rw,username=xxx,password=xxx,dir_mode=0777,filemode=0777,vers=1.0

Personally, I'd start the mount options with defaults and include _netdev,nofail.

You're also missing the last two columns but those should default to something sensible (usually both default to 0).

Is that the only cifs mount in your fstab? If not it may not be the problematic one. sudo mount -a tries to mount every fstab entry that is unmounted and not set noauto so the error may not be related to that fstab entry.

There are more ways than sudo mount -a to mount something that is present in fstab. If you supply just the what or the where the rest will be looked up in your fstab so use one of the following instead:Have you tried the manual mount command that's equivqalent to your fstab entry?If that fails, try again with one less mount option each time until it succeeds. The last one you removed is likely the problem one.

The following command will tell you whether a directory has something mounted on it:[shameless self promotion]
If you've not already seen it, Using fstab A Beginner's Guide may be of interest.
[/shameless self promotion]

BTW, IP addresses in private subnets (like 192.168.1.0/16) don't need to be redacted as they can only be reached from inside your router/firewall. Same applies to the share name and mount point. If we're not on your network we can't access them (well unless you're port forwared CIFS on your router/firewall (which is a bloody stupid thing to do) and we know your router's external IP address or hostname).

Hiding the share name can actively prevent us from spotting some problems too. Like a share name containing white space.

Lastly, are you 101% certain nothing has changed on the NAS?

Statistics: Posted by thagrol — Thu Oct 03, 2024 9:20 pm

---