Hi. Long time lurker here. I know enough about Linux to use it for what I need in general, though now with a bit more money to experiment, I have been getting back into it (I am professional systems analyst who deals with windows applications and VMware virtualization.

So I set up a home Xpenology server.
Set up a Plex server in an Ubuntu Server VM.
Successfully mapped the main media share to the Plex vm, no problems, works beautifully.

So I got to add a drive into the Xpenology server to share around my home network as a junk/storage/scratch drive. Nice use for an old 1TB WD blue drive that is still trucking along...

And I get flummoxed. I can access it from windows in seconds.
I can browse to it through both the Ubuntu network browser and the Linux mint network browser (I am most comforable in mint, it reminds of me of OS/2 UI which I loved, but Plex gives explicit instructions for Ubuntu).

In both Ubuntu (16.04) I have the following 2 lines in fstab. The first one works to mount the Xpenology media share. The second returns

mount.nfs an incorrect mount option was specified

10.0.0.9:/volume1/Media /mnt/nfs/xpenology nfs username=myusername,password=mypassword,gid=1000,uid=1000,iocharset=utf8,sec=ntlm 0 0
10.0.0.6:/volume1/Junk_Drive /mnt/nfs/Junk nfs username=myusername,password=mypassword,gid=1000,uid=1000,iocharset=utf8,sec=ntlm 0 0

My Xpenology server has 4 network cards. I dedicated x.x.x.9 to the plex media share

10.0.0.6 is for the Junk share.

NFS is set up correctly in Xpenology. With a rule for the client based on IP. Both shares are set up identically in terms of permissions.

I have no idea why I am getting that message for only the second drive

Any help is appreciated. I have been goggling for 2 days on. I am trying to avoid just doing it the lazy way through samba/cifs which I know works.

I have never used NFS over 2 interfaces on one server, so this is a long shot.

Since the connection to 10.0.0.9 succeeds, what happens if you change the second (junk_Drive) to 10.0.0.9 as well. Since this is the same subnet it should work right away. The only difference being using the same NIC for Media and for Junk_Drive.

If this fails as well, think about permissions on you shared drive, export options...

If it is successful it tells you there is something with the IP. I am not sure one NFS server can serve over 2 NICs.

jlinkels

I just tried that again, it was one of the first things that I experimented with.

No go.

OK. Did you try to mount Junk_Drive from the command line? Without any options. Stupid question, but does /mnt/nfs/Junk actually exist. No stupid mistake like naming it differently. Did you try to mount Junk_Drive to another mount point?

The error message "wrong option" is not always correct. (Or we humans think it is not an option. Don't stick too much to the option thing)

You have checked /var/log/messages and /var/log/syslog on the nfs server?

jlinkels

yes the mounting location exists.

yeah, mounting it manually with

mount -t nfs 10.0.0.6:/volume2/Junk_drive /mnt/nfs/Junk -o async

mounts it

Hilariously, once I executed the command line mount on a LM vm, which mounted it, and then immediately did the sudo mount -a

it executed without error.

It did not stick on reboot however.

That is a large step forward. It looks like a timing problem. Not in measurement of time, but in measurement of other processes which must be running before nfs client can mount.

This is in contradiction with the mounting of 10.0.0.9 which is successful and to the same server. Which is strange.

You can try to postpone the nfs mounting until the last process has started during boot. If you do that, you have to find out the last process which is starting, and make nfs mounting dependent on that.

No idea if that is useful, because it is mighty strange that 10.0.0.9 does mount.

Anyway, see this to see what I mean: https://www.linuxquestions.org/quest...2/#post5757529

jlinkels

Thanks so far.

I am not touching the line that mounts my media drive in the plex server until I know more about this.

I have been trying to get it to mount by itself on the Linux mint vm as a I said.

As a work around until I can get a solution, I have mounted it via cifs

I need to continue this shift of all online storage to my storage server. Its funny, I can access and even mount the drive, every which way but the idea one for it. And the one that would be most convenient for what I am doing on some of the vms.

It is weird. On my main computer I see this as well sometimes after a reboot. But since I reboot less than once every three months I don't see it very often. After the desktop is active I can do mount -a and then everything is mounted.

Even stranger, to other desktop computers (running Mint and Debian) never fail to mount. Fstab is identical. Server is identical.

The computer running Mint has identical hardware as mine. The Debian machine has different hardware but the same Debian as mine.

Summarizing, I don't see any correlation. Anywhere.

jlinkels