Problem with NFS Server and BH 3.0.2H (Solo2)

[themadrix]

Hi there,

I've just installed BH 3.0.2H, and activated the NFS Server in the blue panel. However, it seems impossible to mount the /media/hdd/movie folder in a Synology NAS or a kodi in a raspberry with openelec using NFS.

The most strange thing is that in the NAS the showmount command lists the folder, and in ssh I do can mount the folder with the mount command. (mount solo2ip:/media/hdd/movie /mylocalfolder)

The problem is that I can't get it working from the NAS (both UI and ssh) or the Openelec UI (adding a nfs folder to the collection.

I tried to create the /etc/exports file, but nothing changed at all. (And of course I also tried to restart the service and the solo2).

Any ideas?

 

[themadrix]

More on this issue...

I tried to reinstall the BH image, and the problem is still there.

I also made an schema of the connections, in case it helps:


Green arrows are NFS connections that work. Red connections are unsuccesful NFS connections.

What gets me puzzled is the green arrow between the Openelec ssh and the solo2. It's the only one that can mount the solo2 hdd.

• Openelec (kodi) interface shows that solo2 shares /media/hdd but can't get no further than that. Same for the kodi running in windows 10.
• NAS interface can't connect to solo2, it tells a message asking to ensure the NFS server is up and sharing.
• NAS shell shows that solo2 is sharing the folder (showmount -e solo2IP returns /media/hdd *), but mount command returns a message telling that the NFS version is not compatible.
• All machines can access by nfs the shared folder in the synology nas.

Does anyone have an idea, or is it simply a bug of the NFS server of the BH latest version?

Thanks a lot in advance.

 

[themadrix]

I tried to mount the folder in a raspbian, and the command goes like this:
sudo mount 192.168.1.145:/media/hdd/movie vuplus
mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
mount.nfs: an incorrect mount option was specified

If I run /usr/sbin/rpcinfo in the solo2, it tells me this:
bash-4.3# /usr/sbin/rpcinfo
program version netid address service owner
100000 4 tcp6 ::.0.111 portmapper superuser
100000 3 tcp6 ::.0.111 portmapper superuser
100000 4 udp6 ::.0.111 portmapper superuser
100000 3 udp6 ::.0.111 portmapper superuser
100000 4 local /var/run/rpcbind.sock portmapper superuser
100000 3 local /var/run/rpcbind.sock portmapper superuser
100003 3 tcp 0.0.0.0.8.1 nfs superuser
100227 3 tcp 0.0.0.0.8.1 - superuser
100003 3 udp 0.0.0.0.8.1 nfs superuser
100227 3 udp 0.0.0.0.8.1 - superuser
100021 1 udp 0.0.0.0.133.250 nlockmgr superuser
100021 3 udp 0.0.0.0.133.250 nlockmgr superuser
100021 4 udp 0.0.0.0.133.250 nlockmgr superuser
100021 1 tcp 0.0.0.0.178.44 nlockmgr superuser
100021 3 tcp 0.0.0.0.178.44 nlockmgr superuser
100021 4 tcp 0.0.0.0.178.44 nlockmgr superuser
100021 1 udp6 ::.156.81 nlockmgr superuser
100021 3 udp6 ::.156.81 nlockmgr superuser
100021 4 udp6 ::.156.81 nlockmgr superuser
100021 1 tcp6 ::.221.55 nlockmgr superuser
100021 3 tcp6 ::.221.55 nlockmgr superuser
100021 4 tcp6 ::.221.55 nlockmgr superuser

And if I run rpc.statd...
bash-4.3# /usr/sbin/rpc.statd
Statd service already running!

WTF is going on??

 

[themadrix]

And more on this... If from the nas I ask the solo2 to tell me what does she have:

root@nas:~# rpcinfo -p 192.168.1.145
program vers proto port service
100000 2 tcp 111
100000 2 udp 111
100024 1 udp 50970
100024 1 tcp 58350
100005 1 udp 41774
100005 1 tcp 57648
100005 2 udp 41774
100005 2 tcp 57648
100005 3 udp 41774
100005 3 tcp 57648

It seems nfs is not running!!! How's that possible? May the solo2 have a nfs server up but not 'published'? I do not understand anything.