Can't connect to NFS Shares after Firmware Update

[swidnikk]

I just updated my firmware (RAIDiator 4.1.9 [1.00a043]) and followed instructions to reboot etc. I can successfully login to the admin control panel and ssh to my device, however the NFS shares are no longer working in their usual fashion. They are listed in the admin panel.

I used to connect via the mac finder and also auto_mount. Any suggestions to troubleshoot the NFS service?

[swidnikk]

Some troubleshooting details below for anyone who may need it someday. The problem *resolved itself* after the READYNAS was up and running all day. Not sure why.

client$ showmount -e READYNAS_IP
Exports list on READYNAS_IP:
/c/seed *
/c/media *
/c/backup *
swid-mba:~ swid$

From one of my clients:
client$ rpcinfo -p READYNAS_IP
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100011 1 udp 625 rquotad
100011 2 udp 625 rquotad
100011 1 tcp 628 rquotad
100011 2 tcp 628 rquotad
100024 1 udp 32765 status
100024 1 tcp 32765 status
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100021 1 udp 4296 nlockmgr
100021 3 udp 4296 nlockmgr
100021 4 udp 4296 nlockmgr
100021 1 tcp 3640 nlockmgr
100021 3 tcp 3640 nlockmgr
100021 4 tcp 3640 nlockmgr
100005 1 udp 4297 mountd
100005 1 tcp 3408 mountd
100005 2 udp 4297 mountd
100005 2 tcp 3408 mountd
100005 3 udp 4297 mountd
100005 3 tcp 3408 mountd

From READYNAS
READYNAS_SERVER:/var/lib/nfs# netstat -unlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
udp 0 0 0.0.0.0:2049 0.0.0.0:* -
udp 0 0 0.0.0.0:663 0.0.0.0:* 2607/rpc.statd
udp 0 0 192.168.11.20:22081 0.0.0.0:* 1075/raidard
udp 0 0 0.0.0.0:22081 0.0.0.0:* 1075/raidard
udp 0 0 0.0.0.0:4296 0.0.0.0:* -
udp 0 0 0.0.0.0:4297 0.0.0.0:* 2618/rpc.mountd
udp 0 0 192.168.11.20:50001 0.0.0.0:* 1087/upnpd
udp 0 0 0.0.0.0:5353 0.0.0.0:* 865/avahi-daemon: r
udp 0 0 0.0.0.0:1900 0.0.0.0:* 1087/upnpd
udp 0 0 0.0.0.0:111 0.0.0.0:* 813/portmap
udp 0 0 0.0.0.0:625 0.0.0.0:* 876/rpc.rquotad
udp 0 0 0.0.0.0:32765 0.0.0.0:* 2607/rpc.statd

The following is odd from daemon.log. You can see that several clients mount successfully and then there are some warning reported about /etc/exports, but no errors.
READYNAS_SERVER:/var/log# cat daemon.log
....
Aug 1 23:24:39 SHUTTER mountd[909]: authenticated mount request from 192.168.11.3:801 for /c/media (/c/media)
Aug 1 23:24:47 SHUTTER mountd[909]: authenticated mount request from 192.168.11.3:895 for /c/media (/c/media)
Aug 1 23:24:55 SHUTTER mountd[909]: authenticated mount request from 192.168.11.3:655 for /c/media (/c/media)
Aug 1 23:25:03 SHUTTER mountd[909]: authenticated mount request from 192.168.11.2:797 for /c/media (/c/media)
Aug 1 23:25:09 SHUTTER mountd[909]: Caught signal 15, un-registering and exiting.
Aug 1 23:25:09 SHUTTER rpc.statd[885]: Caught signal 15, un-registering and exiting.
Aug 1 23:25:20 SHUTTER exportfs[2604]: /etc/exports [1]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/backup". Assuming default behaviour ('no_subtree_check'). NOTE: this default has changed since nfs-utils version 1.0.x
Aug 1 23:25:20 SHUTTER exportfs[2604]: /etc/exports [2]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/media". Assuming default behaviour ('no_subtree_check'). NOTE: this default has changed since nfs-utils version 1.0.x
Aug 1 23:25:20 SHUTTER exportfs[2604]: /etc/exports [3]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/seed". Assuming default behaviour ('no_subtree_check'). NOTE: this default has changed since nfs-utils version 1.0.x
Aug 1 23:25:20 SHUTTER rpc.statd[2607]: Version 1.1.0 Starting
Aug 1 23:25:20 SHUTTER rpc.statd[2607]: statd running as root. chown /var/lib/nfs/sm to choose different user
SHUTTER:/var/log#