NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RN212 share mount access denied from Linux
Some time ago I migrated from a ReadyNAS Duo (Radiator 4.1.14) to an RN212 (OS6 6.8.1) and after some considerable struggles with file access permissions, the 212 now works well. However, I was never able to get Linux access to the 212 working but as the Duo still did what I needed stuck with it. I now NEED to get that bit working.
I am unable to mount 212 shares from my Linux devices (a suite of Raspberry Pi's to be precise). I have, as far as I can tell, set the permissions and protocols on the 212 to be exactly the same as those on the Duo but any attempt to mount a share other than /home returns an Access Denied error, the Duo continues to work fine. I have around 10 shares on each device plus the home shares but three are of interest here, each of which have NFS access enables.
Runing showmount returns the following;
MyPi$ sudo showmount -e <Duo ip address>
Export list for 10.###.###.105
/c/Pi2 *
/c/home *
/c/Pi (everyone)
MyPi$ sudo showmount -e <212 ip address>
Export list for 10.###.###.107
/home *
/data/RpiRoot 127.0.0.1
/data/Pi2 127.0.0.1
Trying to mount a share results in the following;
MyPi$ sudo mount -v 10.##.##.107:/RpiRoot /mnt/Bf2Pi
mount.nfs: timeout set for Mon Feb 26 21:45:13 2018
mount.nfs: trying text-based options 'vers=4.2,addr=10.##.##.107,clientaddr=10.##.##.99'
mount.nfs: mount(2): Invalid argument
mount.nfs: trying text-based options 'vers=4.1,addr=10.##.##.107,clientaddr=10.##.##.99'
mount.nfs: mount(2): Invalid argument
mount.nfs: trying text-based options 'vers=4.0,addr=10.##.##.107,clientaddr=10.##.##.99'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'addr=10.##.##.107'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 10.###.###.107 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 10.###.###.107 prog 100005 vers 3 prot UDP port 33683
mount.nfs: mount(2): Permission Denied
mount.nfs: access denied by server while mounting 10.###.###.107:/RpiRoot
Using the same command for the Duo results in a mounted and accessible share on UDP Port 3074.
Can someone point me in the right direction please? What am I missing?
5 Replies
Replies have been turned off for this discussion
There's no reason to mask out 10.x.x.x IP addresses, as they aren't routable over the internet.
Did you try
sudo mount -v 10.##.##.107:/data/RpiRoot /mnt/Bf2Pi
Oh yes, and /c/RpiRoot (ridiculous but you never know). I even deleted the original share and created a new one with a different name.
Not sure how this became marked as solved. Far from it.
I made a small mistake in the post; the command line should have read;
MyPi$ sudo mount -v 10.##.##.107:/data/RpiRoot /mnt/Bf2Pi
I have also tried various combinations specifying the protocol e.g;
MyPi$ sudo mount -v -t nfs 10.##.##.107:/RpiRoot /mnt/Bf2Pi
but the results are exactly the same.
I have tried every combination of protocols and access rights I can think of but nothing appears to work.
I was able to mount a test share on another ReadyNAS with
mount -v 10.0.0.15:/data/Test /mnt
Did you check "read/write" for anyhost on the NFS network access tab in the share settings?
The simplest of things can be so hard to find. Thank you so much, that appears to have fixed the issue.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
