[SOLVED] Can't access unRAID NFS share from Ubuntu 20.04 desktop

[Keek Uras]

Hello. I found a few posts close to this but not exactly the same, so I've started a new topic. I've followed this guide to set up an external box to help with caching for Plex (and hopefully Emby).

 

The article. See section titled: "Software Installation & Configuration"

 

The setup on unRAID: 

I have a share called Files that has all my media folders within (e.g., Movies, TV Shows, eBooks, etc). I have NFS enabled and the rule for the share is 

172.16.0.0/24 (sec=sys,rw,UID=100)

Note: 100 is a user on the share with r/w.

 

My external Ubuntu settings:

I created the same username and password of the user on the unRAID share. In fstab, I have these 2 maps:

172.16.0.250:/mnt/user/files/Movies /mnt/movies nfs defaults,noatime 0 0 
172.16.0.250:/mnt/user/files/TV\040Shows /mnt/tv nfs defaults,noatime 0 0 

If I run "sudo mount -a" I get:

mount.nfs: access denied by server while mounting 172.16.0.250:/mnt/user/files/Movies
mount.nfs: access denied by server while mounting 172.16.0.250:/mnt/user/files/TV Shows

If I run "showmount -e repository.local" (repository is my unRAID server name), I get:

Export list for repository.local:
/mnt/user/Files 172.16.0.0/24

Any thoughts on what I might have missed? Thank you in advance for your assistance.

Edited September 24, 2020 by Keek Uras
nfs mount corrections from incorrect copy/paste

[Keek Uras]

I ran "sudo mount -v -a". Here is the output:

 

mount.nfs: timeout set for Thu Sep 24 11:59:58 2020

mount.nfs: trying text-based options 'vers=4.2,addr=172.16.0.250,clientaddr=172.16.0.200'

mount.nfs: mount(2): Protocol not supported

mount.nfs: trying text-based options 'vers=4.1,addr=172.16.0.250,clientaddr=172.16.0.200'

mount.nfs: mount(2): Protocol not supported

mount.nfs: trying text-based options 'vers=4.0,addr=172.16.0.250,clientaddr=172.16.0.200'

mount.nfs: mount(2): Protocol not supported

mount.nfs: trying text-based options 'addr=172.16.0.250'

mount.nfs: prog 100003, trying vers=3, prot=6

mount.nfs: trying 172.16.0.250 prog 100003 vers 3 prot TCP port 2049

mount.nfs: prog 100005, trying vers=3, prot=17

mount.nfs: trying 172.16.0.250 prog 100005 vers 3 prot UDP port 55268

mount.nfs: mount(2): Permission denied

mount.nfs: access denied by server while mounting 172.16.0.250:/mnt/user/files/Movies/

mount.nfs: timeout set for Thu Sep 24 11:59:58 2020

mount.nfs: trying text-based options 'vers=4.2,addr=172.16.0.250,clientaddr=172.16.0.200'

mount.nfs: mount(2): Protocol not supported

mount.nfs: trying text-based options 'vers=4.1,addr=172.16.0.250,clientaddr=172.16.0.200'

mount.nfs: mount(2): Protocol not supported

mount.nfs: trying text-based options 'vers=4.0,addr=172.16.0.250,clientaddr=172.16.0.200'

mount.nfs: mount(2): Protocol not supported

mount.nfs: trying text-based options 'addr=172.16.0.250'

mount.nfs: prog 100003, trying vers=3, prot=6

mount.nfs: trying 172.16.0.250 prog 100003 vers 3 prot TCP port 2049

mount.nfs: prog 100005, trying vers=3, prot=17

mount.nfs: trying 172.16.0.250 prog 100005 vers 3 prot UDP port 55268

mount.nfs: mount(2): Permission denied

mount.nfs: access denied by server while mounting 172.16.0.250:/mnt/user/files/TV Shows/

 

I tried adding vers=3 to the mount points but that didn’t work either.

Edited September 24, 2020 by Keek Uras
punctuation

[Keek Uras]

They helped me on the server forum board. I changed the NFS rule on the share to 172.16.0.0/24(rw) and changed the lower case f to F for Files in fstab and it worked. I just wanted to share in case anyone else has this issue.

[JorgeB]

Thanks for posting back, few users using NFS, so more difficult to get help here.

[nraygun]

Is there a tutorial anywhere on how to setup NFS shares on the unRaid side as well as on a Linux client side?

I'm having some SMB and GVfs problems and I'm thinking of moving over to NFS shares (simultaneous with SMB so the family's Win10 machines can get to the shares).