15 hours ago, dedi said:

So I run into the same issue with the current version of OSMC.

I solved it with AI, by adding the following lines to /etc/nfs.conf on my Unraid host (file didn't exist before for me):

[nfsd]
vers4.0=y
vers4.1=y
vers4.2=y

Quick console command to add it and restart nfs:

cat << 'EOF' >> /etc/nfs.conf
[nfsd]
vers4.0=y
vers4.1=y
vers4.2=y
EOF
/etc/rc.d/rc.nfsd restart

It worked after rebooting my OSMC.

To make it permanent, place it in the go file (did not test the reboot right now):

cat << 'EOF' >> /boot/config/go

cat << 'INNER_EOF' >> /etc/nfs.conf
[nfsd]
vers4.0=y
vers4.1=y
vers4.2=y
INNER_EOF
/etc/rc.d/rc.nfsd restart
EOF

I hope this is something to setup in the GUI in the future.

This worked for me. Thank you so much!!! Now i need to add to my Go file. Hopefully a permanent fix is in the works.

FYI. I configured Unraid and Kodi for NFS version 4.

Edited June 3Jun 3 by mhaaland
Correction

Unraid 7.2.4 works fine for me, I'm using NFS in windows to mount NFS shares on unraid, once I upgrade to 7.3x the NFS mounts don't work anymore, I downgrade back to 7.2.4 and they start working again, so obviously something has changed. What is the fix, it sounds like something in the 7.3x update has broken somewhere? I'm not using Kodi, I'm just trying to get my mounts back for backups.

Edited August 27Aug 27 by shdwkeeper

Same general issue here: both my fedora NFS mounts and my home assistant mount which uses NFS for backup can no longer connect.

I just upgraded from 7.2.2 to 7.3.3. Everything else seems to be okay, but NFS is cooked.

Would be nice to see some dev responses to this issue, as it should not require user workarounds to make it work again.