NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Duo suddenly does not allow NFS mounts
I have several ReadyNas Duos and have always had them set up to allow NFS mounting of the shares with root access. A few months ago, with no change to the system or clients, some clients can not mount the NFS share on my older ReadyNas Duo, but others still can. The bad clients were mounted, but after a reboot could not mount again, so nothing was changed. I tried a full reinstall of the first client I saw problems with at the same exact OS to eliminate any new version issues.
Here are the things that I have attempted to eliminate:
- IP address (Changing to one that is able to mount does not resolve the issue)
- nfs client versions
- ReadyNas share permissions
- showmount -e <nas ip> just hangs and times out
- mount command just hangs and times out
This is a very odd problem and I desperately need to resolve it. I'm sure it could be somehting very simple?
I have noticed that the new Duo device does not export the shares that same way and requires a full path to the share when mounting. I'm not sure if an update to the troubled ReadyNas OS caused this or not, but it is up to date as of today. The problem started at a lower version and the update to the most recent was done after the problem existed.
Please help.
Here are the things that I have attempted to eliminate:
- IP address (Changing to one that is able to mount does not resolve the issue)
- nfs client versions
- ReadyNas share permissions
- showmount -e <nas ip> just hangs and times out
- mount command just hangs and times out
This is a very odd problem and I desperately need to resolve it. I'm sure it could be somehting very simple?
I have noticed that the new Duo device does not export the shares that same way and requires a full path to the share when mounting. I'm not sure if an update to the troubled ReadyNas OS caused this or not, but it is up to date as of today. The problem started at a lower version and the update to the most recent was done after the problem existed.
Please help.
8 Replies
Replies have been turned off for this discussion
- The RN102 exports differently, but the other NAS were not changed to match it.
What ReadyNAS fails (please include firmware version). - Model: ReadyNAS Duo [X-RAID]
Firmware: RAIDiator 4.1.13 [1.00a043]
Memory: 1024 MB [2.5-3-3-7]
Volume C: Online, X-RAID, 2 disks, 37% of 1853 GB used
Sorry it took a bit to get back to you. - Did it work properly after you upgraded to 4.1.13? It was released Nov 26, 2013.
- I belive it did, but I can't be sure exactly when I started to see the problem.
It began after a raspberrypi I am running crashed. It had the share mounted and after it came back up, it could not mount the share anymore. I assumed that something was corrupted and reinstalled from scratch only to find that it did not resolve the issue. I chaged the IP address, hoping that would resolve it. I then realized that any machine that had not previously connected to nfs on the NAS, would not be able to mount the share. I have several systems that are currently conneted and can mount and unmount, but no new systems. My guess was that there was an issue with newer versoins of the nfs client, but the raspberryPi was installed with the exact same build after it crashed and it was able to mount prior to the crash.
It seems to me that there is some sort of iptable or filter or ACL that is forbidding the attempts to mount. The systems can ping and can see the http pages of the NAS, but simply can not NFS mount. I have removed all restrictions and rebooted several times. - Some more debug info. showmount worked after a while on one machine, but still could not mount
root@utilite-desktop:~# showmount -e 10.10.55.102
Export list for 10.10.55.102:
/c/home *
/c/media (everyone)
/c/backup (everyone)
/c/MRD_FILES (everyone)
/c/KLD_FILES (everyone)
/c/JFD_FILES (everyone)
/c/CSA_FILES (everyone)
/c/Shared_Media (everyone)
root@utilite-desktop:~# mount -o nolock 10.10.55.102:/MRD_FILES /mnt
mount.nfs: Connection timed out
root@utilite-desktop:~# mount -o nolock 10.10.55.102:/c/MRD_FILES /mnt
mount.nfs: Connection timed out
root@utilite-desktop:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.04.3 LTS
Release: 12.04
Codename: precise
root@utilite-desktop:~# dpkg -l|grep nfs
ii libnfsidmap2 0.25-1ubuntu2 NFS idmapping library
ii nfs-common 1:1.2.5-3ubuntu3.1 NFS support files common to client and server
root@utilite-desktop:~# ps -ef|grep nfs
root 488 2 0 May23 ? 00:00:00 [nfsiod]
root 7642 7609 0 18:36 pts/1 00:00:00 grep --color=auto nfs
root@utilite-desktop:~# ps -ef|grep rpc
root 461 2 0 May23 ? 00:00:00 [rpciod]
root 1478 1 0 May23 ? 00:00:00 rpc.idmapd
root 2300 1 0 May23 ? 00:00:01 rpcbind -w
statd 2586 1 0 May23 ? 00:00:00 rpc.statd -L
root 7644 7609 0 18:36 pts/1 00:00:00 grep --color=auto rpc - Anyone have any ideas?
- So there is no hope of ever figuring this out I guess?
- For anyone who ends up here. The problem was the network switch as described below:
SOLVED!
Rsync:
After a factory default and reinstrall with the latest RN102 firmware availabel on the forums, I created all new shares in the exact same way as the first time and now was able to enable rsync password for all shares.
NFS:
It turns out that there was a firware bug with the Netgear Prosafe switch that this NAS is connected to. Netgear JGS524PE
A firmware upgrade resolved teh NFS issues.
I appreciate all of the help from the forum, which is what led me in teh direction of a possible network problem.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
