Can't mount NFS Share from Raspberry Pi 3

[Mana]

Hello there,
I'm trying to mount an NFS share from my Raspberry Pi 3. I created a share "Backup" on my TS-212 and gave NFS permissions for Hosts "*".
My /etc/exports looks like this:

Code: Select all

"/share/MD0_DATA/Backup" *(rw,async,no_subtree_check,insecure,no_root_squash)
"/share/MD0_DATA/Public" *(rw,async,no_subtree_check,insecure,no_root_squash)
"/share/MD0_DATA/Qmultimedia" *(ro,async,no_subtree_check,insecure,no_root_squash)

But when I try to mount manually from my pi, I don't even get an error, just a timeout:

Code: Select all

 sudo mount -t nfs -o vers=3 192.168.13.13:/Backup /media/Backup -v
mount.nfs: timeout set for Sat Jan  7 08:15:56 2017
mount.nfs: trying text-based options 'vers=3,addr=192.168.13.13'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.13.13 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.13.13 prog 100005 vers 3 prot UDP port 30000
mount.nfs: mount(2): Connection timed out
mount.nfs: Connection timed out

Without forcing Version 3, it's quite similar, but less detailed:

Code: Select all

sudo mount -t nfs 192.168.13.13:/Backup /media/Backup -v
mount.nfs: timeout set for Sat Jan  7 08:32:44 2017
mount.nfs: trying text-based options 'vers=4,addr=192.168.13.13,clientaddr=192.168.13.19'
mount.nfs: mount(2): Connection timed out
mount.nfs: Connection timed out

I have already read in some other threads about NFS problems, so I upgraded to 4.2.2, tried an "exportfs -a", tried to mount from a Ubuntu, but always the same result.

Does anyone have another idea, what could be the problem?

[OneCD]

You may want to check out /etc/config/nfssetting as well.

Not sure if this will work with BusyBox grep but you could try it. I'm using GNU grep so it works for me:

Code: Select all

# grep '\[\|Backup' < /etc/config/nfssetting

As an example, here's my videos share:

Code: Select all

[/share] # grep '\[\|videos' < /etc/config/nfssetting 
[Access]
/share/MD0_DATA/videos = TRUE
[AllowIP]
/share/MD0_DATA/videos = workstation,mediaplayer,laptop,webserver,10.0.0.108
[SquashOption]
/share/MD0_DATA/videos = root_squash,root_squash,root_squash,root_squash,no_root_squash
[AnonUID]
/share/MD0_DATA/videos = 500,500,500,500,65534
[AnonGID]
/share/MD0_DATA/videos = 100,100,100,100,65534
[Global]
[Permission]
/share/MD0_DATA/videos = rw,rw,rw,rw,rw

And to mount this on OpenSUSE (don't need to specify any options):

Code: Select all

$ sudo mount wocky:/videos /mnt/wocky/videos

[OneCD]

I have already read in some other threads about NFS problems, so I upgraded to 4.2.2, tried an "exportfs -a", tried to mount from a Ubuntu, but always the same result.

I'd also advise against using the usual NFS share creation methods via the NAS command line. The OS is an embedded, trimmed, and modified Linux - not a standard(?) desktop distro.

[Mana]

Hello,
thanks for your answer. Here's my /etc/config/nfssetting for that share:

Code: Select all

[~] # grep '\[\|Backup' < /etc/config/nfssetting 
[Access]
/share/MD0_DATA/Backup = rw
[AllowIP]
/share/MD0_DATA/Backup = *
[SquashOption]
/share/MD0_DATA/Backup = no_root_squash
[AnonUID]
/share/MD0_DATA/Backup = 65534
[AnonGID]
/share/MD0_DATA/Backup = 65534

The only real difference to your config seems to be the [Access] section, where your share is listed with "TRUE" instead of "rw" like in my setting.

I'd also advise against using the usual NFS share creation methods via the NAS command line.

I only tried the 'exportfs -a' because I read in some other threads, that this could reveal config errors in the NFS settings, but that didn't work out.

Do you have another idea?

[schumaku]

Is the NFS v2/v3 service enabled at all?

Control Panel -> Network Services -> Win/Mac/NFS -> [NFS Service]

Are the NFS related processes on the NAS up and running?

[~] # ps -ef | grep nfs
1417 admin SW< [nfsiod]
6662 admin 576 S grep nfs
9736 admin SW< [nfsd4]
9737 admin SW< [nfsd4_callbacks]
9738 admin SW [nfsd]
9739 admin SW [nfsd]
9740 admin SW [nfsd]
9741 admin SW [nfsd]
9742 admin SW [nfsd]
9743 admin SW [nfsd]
9744 admin SW [nfsd]
9745 admin SW [nfsd]
[~] # ps -ef | grep rpc
1410 admin SW< [rpciod]
6666 admin 576 S grep rpc
9495 admin 132 S /usr/sbin/rpc.rquotad -p 30002
9707 admin 1896 S /usr/sbin/rpc.mountd -p 30000 -F
9757 admin 592 S /usr/sbin/rpc.idmapd
9760 admin 812 S /usr/sbin/rpc.statd -p 30001
[~] #

This is a TS-419PII on QTS 4.2.2 Build 20161214 (ok, with NFSv4 basic services enabled). Check your TS-212 ...

Don't play exportfs ... use the QTS Web UI only.

[Mana]

Hi schumaku,

yes, the NFS v2/v3 is enabled, I also tried to disable it once, and then re-enable it.

Your "ps" on the NAS CLi gives the following output:

Code: Select all

[~] # ps -ef | grep nfs
 1259 admin           SW< [nfsiod]
 7261 admin       576 S   grep nfs
 8248 admin           SW< [nfsd4]
 8249 admin           SW< [nfsd4_callbacks]
 8250 admin           SW  [nfsd]
 8251 admin           SW  [nfsd]
 8252 admin           SW  [nfsd]
 8253 admin           SW  [nfsd]
 8254 admin           SW  [nfsd]
 8255 admin           SW  [nfsd]
 8256 admin           SW  [nfsd]
 8257 admin           SW  [nfsd]
[~] # ps -ef | grep rpc
 1251 admin           SW< [rpciod]
 7303 admin       576 S   grep rpc
 8124 admin       128 S   /usr/sbin/rpc.rquotad -p 30002
 8174 admin       880 S   /usr/sbin/rpc.mountd -p 30000 -F
 8290 admin       828 S   /usr/sbin/rpc.statd -p 30001
[~] #

Is there a NFSv4 option for the TS-212 also?

[schumaku]

Is there a NFSv4 option for the TS-212 also?

Of course...

Code: Select all

/sbin/setcfg NFS Enable_V4 TRUE

Code: Select all

/etc/init.d/nfs restart

[OneCD]

Is there a NFSv4 option for the TS-212 also?

Of course...

Code: Select all

/sbin/setcfg NFS Enable_V4 TRUE

Code: Select all

/etc/init.d/nfs restart

Thanks Kurt - didn't know about that one.

[Mana]

Thanks for the NFSv4 command, but that doesn't work either. I still can't mount an NFS share. Obviously not with v3, but with the enabled v4 it also doesn't work:

Code: Select all

pi@raspberrypi:~ sudo mount -t nfs -o vers=3 192.168.13.13:/Backup /media/Backup -v
mount.nfs: timeout set for Sat Jan 14 14:08:02 2017
mount.nfs: trying text-based options 'vers=3,addr=192.168.13.13'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.13.13 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: portmap query retrying: RPC: Program not registered
mount.nfs: prog 100005, trying vers=3, prot=6
mount.nfs: portmap query failed: RPC: Program not registered
mount.nfs: requested NFS version or transport protocol is not supported
pi@raspberrypi:~ $ sudo mount -t nfs -o vers=4 192.168.13.13:/Backup /media/Backup -v
mount.nfs: timeout set for Sat Jan 14 14:08:10 2017
mount.nfs: trying text-based options 'vers=4,addr=192.168.13.13,clientaddr=192.168.13.19'

Are there any other options to try?

[schumaku]

This reads to me like either NFS and RPC is not listening at all on this interface, or the RasPI IP address is blocked resp. not in an allowed list for the NAS platform in Security.