Originally Posted by
bobblex
Thanks for your input.
What I have listed in my example are just fillers for the actual share names. I do use the correct IP address and do use the actual same share name as the SMB share name, which happens to be a directory and it's sub-directory on the NAS.
I'm not sure what you are really saying here exactly. The share name (e.g movies) can have a path of something like this: /srv/share/movies. The SMB resource is always //Server IP/movies. We may be talking of the same thing here.
The line is currently working in Lubuntu 14.04.2 and Linux Mint 17.1 Xfce. The line appears to correctly read, but the mount fails as the network isn't loaded at the time it is called. In Lubuntu 14.04.2 and Mint and earlier versions of Lubuntu, I typically saw from three to six failed to connect messages, but the system kept trying to mount until successful. In 15.10 I don't see any warning/errors about not being able to mount due to the network not being ready.
It sounds like you already know what is not working. Ubuntu 15.10 uses a different init system (systemd vs the earlier Upstart) so the workarounds will be different.
As you can see from the first post "_netdev" is used which is supposed make fstab wait until the network is ready, but it apparently doesn't work and it makes no difference where I put it after the "cifs".
That's not my take on what _netdev does. I see it as preventing a failure of the host to complete booting up if there is no network connectivity for one of the lines in the fstab file. In this case it is working as I would expect it to. From the man page for mount
Code:
_netdev
The filesystem resides on a device that requires network access (used to pre‐
vent the system from attempting to mount these filesystems until the network
has been enabled on the system).
After I log in, I'm able to run sudo mount -a and the NAS is mounted correctly.
By this time the network is up and the mount -a command works. The command also uses the fstab file, but this time it works. See below from the same mount man page
Code:
-a, --all
Mount all filesystems (of the given types) mentioned in fstab.
In the end the problem is the network connectivity not the line in the fstab file.
Bookmarks