Unable to mount NFS share on Ubuntu

[Steven Scott]

I have FreeNAS 9.3.1 running on a computer with an NFS share. I am unable to mount this share via the mount command:
mount -t nfs 192.168.0.104:/mnt/NAS /mnt/test on Ubuntu 15.10. I also cannot do this on the FreeNAS box. On the FreeNAS box, I get a permission denied doing it through the Shell menu option. On the Ubuntu system, I get a timeout error. Adding the vers=3 to the fstab loading on the Ubuntu machine

FreeNAS
/etc/exports
/mnt/NAS -alldirs -mapall=mediactr:wheel freenas AMD6Core DellXPS

All the machines above can ping the FreeNAS box

Ubuntu /etc/fstab
192.168.0.104:/mnt/NAS /mnt/FreeNAS nfs async,auto,dev,exec,rw,nouser,vers=3 0 0[

Command Line fails as well:
mount -v -t nfs -o nfsvers=3 192.168.0.104:/mnt/NAS /mnt/FreeNAS

The command line gets a timeout, until I added the nfsvers, which now has the protocol unsupported.

The command liine attempt on the FreeNAS computer itself, gives and error of:
nfsd: RPCPROG_NFS: RPC: Remote system error - Connection
refused

 

[SweetAndLow]

Did you install nfs-common on the client? Looks like you are doing it correctly. Must be something silly.

 

[Steven Scott]

I have installed it. The funny thing, is that this was all working until the previous weekend. My Ubuntu 15.04 stopped mounting this after a reboot. I have been unable to get it to mount the drive, so I upgraded it to Ubuntu 15.10. I cannot even load the share on the FreeNAS server either. I have the dump from my other computer (Ubuntu 15.10) which appears to be a routing problem, but ping works.

~$ ping 192.168.0.104
PING 192.168.0.104 (192.168.0.104) 56(84) bytes of data.
64 bytes from 192.168.0.104: icmp_seq=1 ttl=64 time=0.214 ms
64 bytes from 192.168.0.104: icmp_seq=2 ttl=64 time=0.257 ms
64 bytes from 192.168.0.104: icmp_seq=3 ttl=64 time=0.252 ms
^C
--- 192.168.0.104 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.214/0.241/0.257/0.019 ms

~$ sudo mount -t nfs -o nfsvers=3 192.168.0.104:/mnt/NAS /mnt/test
mount.nfs: portmap query failed: RPC: Remote system error - No route to host
mount.nfs: portmap query failed: RPC: Remote system error - No route to host
mount.nfs: portmap query failed: RPC: Remote system error - No route to host
mount.nfs: portmap query failed: RPC: Remote system error - No route to host
mount.nfs: portmap query failed: RPC: Remote system error - No route to host
mount.nfs: portmap query failed: RPC: Remote system error - No route to host
mount.nfs: portmap query failed: RPC: Remote system error - No route to host
mount.nfs: portmap query failed: RPC: Remote system error - No route to host
mount.nfs: portmap query failed: RPC: Remote system error - No route to host
mount.nfs: portmap query failed: RPC: Remote system error - No route to host
mount.nfs: portmap query failed: RPC: Remote system error - No route to host
mount.nfs: portmap query failed: RPC: Remote system error - No route to host
mount.nfs: portmap query failed: RPC: Remote system error - No route to host
mount.nfs: Connection timed out
mount.nfs: timeout set for Tue Nov 3 08:17:51 2015
mount.nfs: trying text-based options 'nfsvers=3,addr=192.168.0.4'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying text-based options 'nfsvers=3,addr=192.168.0.4'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying text-based options 'nfsvers=3,addr=192.168.0.4'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying text-based options 'nfsvers=3,addr=192.168.0.4'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying text-based options 'nfsvers=3,addr=192.168.0.4'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying text-based options 'nfsvers=3,addr=192.168.0.4'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying text-based options 'nfsvers=3,addr=192.168.0.4'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying text-based options 'nfsvers=3,addr=192.168.0.4'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying text-based options 'nfsvers=3,addr=192.168.0.4'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying text-based options 'nfsvers=3,addr=192.168.0.4'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying text-based options 'nfsvers=3,addr=192.168.0.4'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying text-based options 'nfsvers=3,addr=192.168.0.4'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying text-based options 'nfsvers=3,addr=192.168.0.4'
mount.nfs: prog 100003, trying vers=3, prot=6

This dump is from the Ubuntu attempting to mount the FreeNAS volume.

FreeNAS attempting to mount the same thing, gives an RPC routing error, then permission denied. I am using the shell option on FreeNAS to try to run the commands. The shell starts with a ~#, but maybe I need the sudo there as well?

 

[Steven Scott]

Did you install nfs-common on the client? Looks like you are doing it correctly. Must be something silly.

I posted further information on errors in verbose mode. I have updated to Ubuntu 15.10 without any change either. I can however, browse through the File GUI and see the folder (Browse Network, FreeNAS, ...) and can access the files that way, just not with nfs.