NFS server - cannot connect

komodo

komodo

Vu+ User
Hi,

I have VU+ Solo2 with BH 2.0.7 and trying to setup NFS server. I am not able to connect.

It doesn't work even if I try from remote host or from localhost.

Is there anybody who has solved this issue ? I think there has to be some problem in the image itself.

Here are some outputs

root@acheron:~# rpcinfo 192.168.2.90
program version netid address service owner
100000 2 tcp 0.0.0.0.0.111 portmapper unknown
100000 2 udp 0.0.0.0.0.111 portmapper unknown
100024 1 udp 0.0.0.0.181.197 status unknown
100024 1 tcp 0.0.0.0.130.85 status unknown
100005 1 udp 0.0.0.0.137.115 mountd unknown
100005 1 tcp 0.0.0.0.211.125 mountd unknown
100005 2 udp 0.0.0.0.137.115 mountd unknown
100005 2 tcp 0.0.0.0.211.125 mountd unknown
100005 3 udp 0.0.0.0.137.115 mountd unknown
100005 3 tcp 0.0.0.0.211.125 mountd unknown

root@acheron:~# showmount -e 192.168.2.90
Export list for 192.168.2.90:
/media/hdd (everyone)

root@acheron:~# mount.nfs 192.168.2.90:/media/hdd /media/test/ -v
mount.nfs: timeout set for Wed Dec 2 23:45:39 2020
mount.nfs: trying text-based options 'vers=4.2,addr=192.168.2.90,clientaddr=192.168.2.2'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4.1,addr=192.168.2.90,clientaddr=192.168.2.2'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4.0,addr=192.168.2.90,clientaddr=192.168.2.2'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'addr=192.168.2.90'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Program not registered
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: portmap query failed: RPC: Program not registered
mount.nfs: requested NFS version or transport protocol is not supported
 
D

diverman

Vu+ Newbie
I'm author of the linked thread, and yeah, there's no solution - I just give up and stick with Samba. It works fine.
 
komodo

komodo

Vu+ User
diverman said:
I'm author of the linked thread, and yeah, there's no solution - I just give up and stick with Samba. It works fine.
Click to expand...

Ah :) OK, I didn't notice you are the author :)

Hmm, I know It is a solution but I would be happier with NFS. I used NFS on servers for years and it was much faster than samba.

Anyway it's strange that even authors of BH do not have any solution. Is NFS so rarely used ?
 
Shiro

Shiro

BH-C
The nfs server in Bh is designed to work between 2 box and it works fine.
We have checked.

upload_2020-12-8_18-14-48.png

upload_2020-12-8_18-15-9.png

upload_2020-12-8_18-15-33.png

root@vuzero:~# df
Filesystem 1K-blocks Used Available Use% Mounted on
ubi0:rootfs 197604 117548 80056 59% /
devtmpfs 157584 0 157584 0% /dev
tmpfs 157688 340 157348 0% /run
tmpfs 157688 56 157632 0% /var/volatile
192.168.10.241:/media/hdd
30016560 13329424 16687136 44% /media/net/Sharename
root@vuzero:~#

upload_2020-12-8_18-16-43.png

upload_2020-12-8_18-17-4.png
 
D

dpeddi

Administrator
You forgot to say that is a fresh installation of bh 3.1.0

NFS is a very fast protocol but sometime is difficult to configure.

Since it seems you are a power user, i suggest you to check /usr/bin/nfs_server_script.sh and fine tune your mount.nfs command. probably it should be enough to add "-o vers=3" to your mount command and/or try to add your ip box to /etc/hosts on your pc
 
komodo

komodo

Vu+ User
dpeddi said:
You forgot to say that is a fresh installation of bh 3.1.0

NFS is a very fast protocol but sometime is difficult to configure.

Since it seems you are a power user, i suggest you to check /usr/bin/nfs_server_script.sh and fine tune your mount.nfs command. probably it should be enough to add "-o vers=3" to your mount command and/or try to add your ip box to /etc/hosts on your pc
Click to expand...
Shiro said:
The nfs server in Bh is designed to work between 2 box and it works fine.
We have checked.

View attachment 49730

View attachment 49731

View attachment 49735

root@vuzero:~# df
Filesystem 1K-blocks Used Available Use% Mounted on
ubi0:rootfs 197604 117548 80056 59% /
devtmpfs 157584 0 157584 0% /dev
tmpfs 157688 340 157348 0% /run
tmpfs 157688 56 157632 0% /var/volatile
192.168.10.241:/media/hdd
30016560 13329424 16687136 44% /media/net/Sharename
root@vuzero:~#

View attachment 49736

View attachment 49737
Click to expand...

Thanks for your time Shiro.
Maybe that's the problem you are on 3.1.0 as dpeddi said. I am still on 3.0.7. So maybe I should upgrade to 3.1.0 to test NFS and I'll see.

And as for dpeddi. I know NFS is more complicated than samba, but I have never had such problems to setup NFS.
Btw "-o vers=3" does nothing.
As you can see in my first post the mount command is trying all versions from 4.2 to 3 both TCP and UDP but without success.
 
komodo

komodo

Vu+ User
SOLVED :)

So finaly I can announce that I am connected to my NFS server on VU+ :)

It was a long run but it's working.

So what have I done.

First of all, after Shiro reported that it's working between two BH boxes I have tried mount NFS locally from my box itself. And it worked.
Then I have tried mount from my PC and again no success. So I have checked what options BH uses for mount command.
I have tried add these options to my mount command and it connects without problem.

So, make long story short, I have tried adding options one by one and finally I ended up with these

mount -t nfs 192.168.2.90:/media/hdd /media/test/ -o proto=tcp,port=2049

To be honest I don't know why I have to put these options but, at least on my Debian Testing it's ok.

So maybe "diverman" could try now and report if it's ok or not ? :)

Again, thank you all for your time
 
You must log in or register to reply here.
Top