Nfs mount don't work after kodi v19.1 migration

Hy,
I can´t mount my nfs remote device,

If I run

sudo mount -t nfs 192.168.100.155:/media/hdd /media/hdd

from terminal I have no answer from several minutes and I have to press Ctrl+c to regain cursor

I use Vero 4k +

Thanks in advance.

  1. Maybe something changed in the network, we suggest to check your network with iperf3. Please read this howto
    [How To] Check Network Performance with iperf3

  2. What is the output of showmount -e 192.168.100.155

1 Like

Aside from what @fzinken said, try opening a second SSH into the vero and running sudo dmesg | tail -20 before and during executing the mount command in the first SSH session, see if something pops up during.

Also check the IP address of the Vero using ip a show eth0 | grep "inet " to match it with the output of the showmount command. This SHOULD not be the case as an update like this wouldn’t alter the MAC address of the Vero and therefore not mess with any DHCP stuff, but maybe you had given the vero a static IP directly instead of using a DHCP reservation?

Thanks, fzinken and Jahey,

The network works fine the problem begin just after migration.
showmount didn’t work
osmc@osmc:/media$ showmount -e 192.168.100.155
clnt_create: RPC: Unable to receive
The dmesg output didn’t change durint mount process

osmc@osmc:~$ sudo dmesg | tail -20
[75354.074053] hdmitx: video: Aspect ratio set to 0x02/0x08
[75619.559963] audio_dsp: buf=0
[75619.560041] audio_dsp: IEC958_mode_raw=0
[75619.560086] audio_dsp: IEC958_mode_codec= 0, IEC958 type 2 CH PCM
[75619.560089] audio_dsp: last mode 0,now 0
[75619.560196] hdmitx: hdmitx: config: audio_on
[75619.560201] hdmitx: audio: configure on
[75619.615749] hdmitx: sysfs set hdmi_ch to 0
[75730.555828] audio_dsp: buf=0
[75730.555839] audio_dsp: IEC958_mode_raw=0
[75730.555899] audio_dsp: IEC958_mode_codec= 0, IEC958 type 2 CH PCM
[75730.555904] audio_dsp: last mode 0,now 0
[75730.556140] hdmitx: hdmitx: config: audio_on
[75730.556149] hdmitx: audio: configure on
[75730.644571] hdmitx: video: Aspect ratio set to 0x02/0x08
[75730.651958] hdmitx: sysfs set hdmi_ch to 0
[77735.730955] hdmitx: video: Aspect ratio set to 0x02/0x08
[77735.731477] hdmitx: video: Aspect ratio set to 0x02/0x08
[77742.980760] hdmitx: video: Aspect ratio set to 0x02/0x08
[77742.981299] hdmitx: video: Aspect ratio set to 0x02/0x08

I have added to my server a SMB mountpoint and I cound use it from osmc without problems.

Usually that error is followed by a code though? :slight_smile:

What is the output from this command on the Vero?

rpcinfo -p 192.168.100.155

Can you run the showmount command on the NFS server?

showmount -e localhost

Cheers!

Hi, these are the outputs

osmc@osmc:~$ rpcinfo -p 192.168.100.155
program vers proto port service
100000 4 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 38319 status
100024 1 tcp 34335 status
100003 3 tcp 2049 nfs
100003 3 udp 2049 nfs
100021 1 udp 43788 nlockmgr
100021 3 udp 43788 nlockmgr
100021 4 udp 43788 nlockmgr
100021 1 tcp 42447 nlockmgr
100021 3 tcp 42447 nlockmgr
100021 4 tcp 42447 nlockmgr
100005 1 udp 38382 mountd
100005 1 tcp 51253 mountd
100005 2 udp 40986 mountd
100005 2 tcp 41389 mountd
100005 3 udp 39656 mountd
100005 3 tcp 32939 mountd

osmc@osmc:~$ showmount -e localhost
clnt_create: RPC: Program not registered

Thanks.

Could you provide some context here? Has it ever worked? What’s the NFS server?

Please also provide full logs – grab-logs -A – and post the URL.

With regard to this:

you should run it on the NFS server, as @Jahey specified.

Thanks dillthedog,

Te server is a Zgemma h7s with OS Openpli, the NFS server works perfectly, now I can mount and use it from ubuntu and windows PCs without problems. As previously mentioned it stopped working just after migration.

This is the output from NFS server
root@h7:~# showmount -e localhost
clnt_create: RPC: Timed out
I don’t know what would be the problem hear, may be caused because the NFS server was mounted with Openpli plugin wizard.

This is the log after reboot osmc:
https://paste.osmc.tv/ikuxinaray

Also I have configured other nfs server in my ubuntu machine and osmc hasn’t been able to mount it the same above problem.

Hi,

That looks like a problem with the nfs server on ubuntu, on the server whats the output of:

systemctl status nfs-kernel-server

Thanks Tom.

1 Like

If I put that against my own NFS server (Pi running Raspbian Buster):

   program vers proto   port  service
    100000    4   tcp    111  portmapper
    100000    3   tcp    111  portmapper
    100000    2   tcp    111  portmapper
    100000    4   udp    111  portmapper
    100000    3   udp    111  portmapper
    100000    2   udp    111  portmapper
    100005    1   udp  45121  mountd
    100005    1   tcp  32867  mountd
    100005    2   udp  43584  mountd
    100005    2   tcp  56921  mountd
    100005    3   udp  60851  mountd
    100005    3   tcp  41781  mountd
    100024    1   udp  41741  status
    100024    1   tcp  51157  status
    100003    3   tcp   2049  nfs
    100003    4   tcp   2049  nfs
    100227    3   tcp   2049
    100003    3   udp   2049  nfs
    100227    3   udp   2049
    100021    1   udp  39661  nlockmgr
    100021    3   udp  39661  nlockmgr
    100021    4   udp  39661  nlockmgr
    100021    1   tcp  44213  nlockmgr
    100021    3   tcp  44213  nlockmgr
    100021    4   tcp  44213  nlockmgr

There’s one difference: I have more nfs lines, more specifically for v4 (indicated by the second column called “vers”) , whereas you “only” have v3 running as highest, whilst having other processes for v4 running.

Maybe autodetect says that v4 is available due to what is running v4, but then fails to actually mount due to what is not running v4?

So, next to what Tom asked, could you try forcing the NFS client into v3?

sudo mount -t nfs -o nfsvers=3 192.168.100.155:/media/hdd /media/hdd

Regards

Hi,

I’m able to connect to nfs4 server no problem.

Please provide the output of this command (needs to be run on (192.168.100.155)

systemctl status nfs-kernel-server

As advised by @dillthedog above, showmount -e localhost needs to be run on 192.168.100.155

Would only run showmount -e localhost on the vero4k, if this is now where you are trying to run the server. If this the case?

Thanks Tom.

Thank you very much to the all community for the help, what was wrong was the Openpli nfs server, it worked fine when I connected form Ubuntu but no from OSMC. I reconfigured the nfs server and now works fine.

What I can understand is why it mess up just when I migrate to new osmc version.

bye.

Might be due to the nfs client, now defaulting to version 4, but not in the older version?

Glad to see you got it working! :blush: