SOLVED NFS Mount Creation Issue

[Ammign]

Hello,

Running into what seems to be a dumb user issue. I am trying to make an NFS mount from my FreeNAS box and mount it on my Ubuntu box. I was already able to do this with CIFS before I wiped and started over.

FreeNAS 9.10.1

I have a volume with Unix Permissions, owned by nobody/nobody. (tried root/wheel)
Apply Mode On
775
Unix Permissions

NFS options
(tried both NFSv4 on and off)
(tried allow non-root mount on and off)

NFS Mount
Authorized network includes the /24 of the subnet
(tried All Directories on and off)
Mapall user (tried nobody, root, and blank)
Mapall group (tried nobody, wheel, and blank)

And I have restarted the NFS service after each change.

I have not been able to get my Ubuntu host to mount the NFS share for anything. It just times out. I can ping the host and telnet to 2049 on the FreeNAS host.

I have added both the client and the FreeNAS host to the host name database in Network > Global config and a dig client, dig freenas, dig -x client ip, and dig x freenas ip all work.

The message that shows up after every time I start nfs is as follows:
Sep 3 23:07:54 nas nfsd: can't register svc name

I am really at a loss here. Any suggestions?



[root@nas ~]# rpcinfo -p
program vers proto port service
100000 4 tcp 111 rpcbind
100000 3 tcp 111 rpcbind
100000 2 tcp 111 rpcbind
100000 4 udp 111 rpcbind
100000 3 udp 111 rpcbind
100000 2 udp 111 rpcbind
100000 4 local 111 rpcbind
100000 3 local 111 rpcbind
100000 2 local 111 rpcbind
100005 1 udp 1000 mountd
100005 3 udp 1000 mountd
100005 1 tcp 1000 mountd
100005 3 tcp 1000 mountd
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100024 1 udp 775 status
100024 1 tcp 775 status
100021 0 udp 800 nlockmgr
100021 0 tcp 989 nlockmgr
100021 1 udp 800 nlockmgr
100021 1 tcp 989 nlockmgr
100021 3 udp 800 nlockmgr
100021 3 tcp 989 nlockmgr
100021 4 udp 800 nlockmgr
100021 4 tcp 989 nlockmgr


 

[dlavigne]

Have you tried the tips in http://doc.freenas.org/9.10/sharing.html#troubleshooting-nfs?

 

[Ammign]

Referring specifically to the section 10.2.3-Troubleshooting NFS?
I am using the mitigation 2 on the mount command, and for mitigation 2 and 4 I have both the FreeNAS host and client in the Global configuration host name database just to be sure.

The mount command I am running is:
mount -t -o tcp nfs 192.168.0.121:/mnt/Bunny /media/nfs
Where /mnt/Bunny is the path to the dataset on the FreeNAS host and /media/nfs is a blank directory on my Ubuntu host

 

[dlavigne]

And what error do you get (on either the client or FreeNAS) when you run that mount command?

 

[Ammign]

I just receive the generic "connection timed out" message.

I ran tcpdump for traffic on the FreeNAS host but did not see any traffic for 2049 during the mount attempt. Is there another initialization service I should be looking for instead?

 

[dlavigne]

Were you able to resolve this?

 

[Ammign]

No, I have has no further success with resolving it

 

[Ammign]

I did find this message running by constantly which seems suspect because nas.local is no longer the hostname of the nas.

Code:

Sep 24 02:33:53 nas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000801406D60 nas.local. (Addr) t
hat's already in the list                                                                                                           
Sep 24 02:33:53 nas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000801407180 121.0.168.192.in-ad
dr.arpa. (PTR) that's already in the list

 

[Ammign]

Still not sure of the original cause, but I rebuilt the system and now NFS is working as expected.