NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
wagb4
Sep 07, 2014Aspirant
Can't Use NFS to Access Home Shares
ReadyNAS model 102, Firmware version 6.1.8 - Tried to mount (on Linux) via entry in fstab a user's home folder and I get the error: mount.nfs: access denied by server while mounting <IP address / user...
wagb4
Sep 10, 2014Aspirant
Update - some new findings ---
Because the showmount -e Linux command shows the NAS is exporting the NAS's /home folder <see previous post> on the LAN, I decided to try mounting just that (/home), not /home/jim. This is what I get:
So, I can mount the /home folder; but not sub-folders of /home. I manually edited the IP address of the NAS and user names in the above code block to hide the correct values.
Notice the User & Group values in the folders under /home that became available. The UID & GID values don't match between the computer's Linux system and the NAS's OS. I cannot access any of the folders under the mounted /home folder, obviously due to permissions.
So, now I need to get the computer's UID & GID values to match, or find a way to translate or associate between the two devices. On a whim I created a new Local User on the NAS and manually assigned the UID for that user to 1003 which matches a different user on the computer system. The NAS created the new user with the desired UID just fine, but that user does not show up when I do a fresh NFS mount (umount then mount). The contents of the NAS /home folder after the new mount are identical to that shown in the code block.
The NAS software appears to want UID values starting at 101, and Linux starts UID values at 1000. Assigning UID value of 1003 on the NAS to a new user is, I'm guessing, beyond the range of valid (usable) UID values on the NAS, at least for NFS. The NAS gives no indication that the UID value of 1003 is bad or not usable for NFS.
The only ID value that matches between the computer's Linux and NAS OS is the GID value for group named "users", that is 101. I checked the computer's passwd and groups files and the Users and Groups listed in the code block agree with my Linux system, as expected. not even root can access those folders, or make changes such as chown or chmod.
I think the NAS OS needs to alter their minimum UID value to start at 1000 (or make that a configuration setting when setting up the NAS), and maybe a tweak is needed in the NFS allowed UID values. I believe UID values can be set in a configuration file on the server (NAS) but that would require using SSH, which NetGear says can void getting future support. I also think NFS supports UID:GID transalation but I am not sure that can be done on the client side, but only on the server (NAS) side, again the SSH warning enters the picture. I'm still researching this.
Are there any ReadyNAS OS 6.1.8 users out there using NFS to Linux systems that have resolved this? Which appoach did you use to get this working.
Because the showmount -e Linux command shows the NAS is exporting the NAS's /home folder <see previous post> on the LAN, I decided to try mounting just that (/home), not /home/jim. This is what I get:
jim@WS-2 ~/Desktop $ sudo mount 192.168.XXX.XXX:/home /mnt/NFS
jim@WS-2 ~/Desktop $ ll /mnt/NFS
total 4
drwxr-xr-x 1 98 98 42 Sep 3 12:03 ./
drwxr-xr-x 3 root root 4096 Sep 7 16:54 ../
drwx------ 1 98 98 0 Sep 3 19:39 admin/
drwx------ 1 messagebus users 38 Sep 3 15:20 user1/
drwx------ 1 syslog users 136 Sep 3 15:41 user2/
drwx------ 1 libuuid 98 0 Sep 3 12:03 user3/
So, I can mount the /home folder; but not sub-folders of /home. I manually edited the IP address of the NAS and user names in the above code block to hide the correct values.
Notice the User & Group values in the folders under /home that became available. The UID & GID values don't match between the computer's Linux system and the NAS's OS. I cannot access any of the folders under the mounted /home folder, obviously due to permissions.
So, now I need to get the computer's UID & GID values to match, or find a way to translate or associate between the two devices. On a whim I created a new Local User on the NAS and manually assigned the UID for that user to 1003 which matches a different user on the computer system. The NAS created the new user with the desired UID just fine, but that user does not show up when I do a fresh NFS mount (umount then mount). The contents of the NAS /home folder after the new mount are identical to that shown in the code block.
The NAS software appears to want UID values starting at 101, and Linux starts UID values at 1000. Assigning UID value of 1003 on the NAS to a new user is, I'm guessing, beyond the range of valid (usable) UID values on the NAS, at least for NFS. The NAS gives no indication that the UID value of 1003 is bad or not usable for NFS.
The only ID value that matches between the computer's Linux and NAS OS is the GID value for group named "users", that is 101. I checked the computer's passwd and groups files and the Users and Groups listed in the code block agree with my Linux system, as expected. not even root can access those folders, or make changes such as chown or chmod.
I think the NAS OS needs to alter their minimum UID value to start at 1000 (or make that a configuration setting when setting up the NAS), and maybe a tweak is needed in the NFS allowed UID values. I believe UID values can be set in a configuration file on the server (NAS) but that would require using SSH, which NetGear says can void getting future support. I also think NFS supports UID:GID transalation but I am not sure that can be done on the client side, but only on the server (NAS) side, again the SSH warning enters the picture. I'm still researching this.
Are there any ReadyNAS OS 6.1.8 users out there using NFS to Linux systems that have resolved this? Which appoach did you use to get this working.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!