2026-05-26 09:22:08.926 T:4008 debug <general>: NFS: version: 4

2026-05-26 09:22:08.929 T:4008 error <general>: NFS: Failed to mount nfs share: / (mount_cb: NFS4: SETCLIENTID (path /) failed with NFS4ERR_MINOR_VERS_MISMATCH(-5))

2026-05-26 09:22:08.940 T:4008 debug <general>: [service.librarywatchdog] not watching <nfs://192.168.1.128/mnt/user/Marks TV/>. does not exist

2026-05-26 09:22:08.940 T:4008 debug <general>: NFS: Context for 192.168.1.128/ not open - get a new context.

Both are configured for V4 in Unraid and Kodi

Share name:

Marks TV

Export:

Yes

Security:

Public

 

Please post the diagnostics.

Sorry. here you go.

tower-diagnostics-20260526-0951.zip

Don't see any obvious issues on the Unraid side; post the output from

exportfs -v

/mnt/user/Alex Media

<world>(async,wdelay,hide,no_subtree_check,fsid=111,anonuid=99,anongid=100,sec=sys,rw,insecure,root_squash,all_squash)

/mnt/user/Blu-Ray Movies

<world>(async,wdelay,hide,no_subtree_check,fsid=100,anonuid=99,anongid=100,sec=sys,rw,insecure,root_squash,all_squash)

/mnt/user/DVR Recordings

<world>(async,wdelay,hide,no_subtree_check,fsid=112,anonuid=99,anongid=100,sec=sys,rw,insecure,root_squash,all_squash)

/mnt/user/E-Books

<world>(async,wdelay,hide,no_subtree_check,fsid=116,anonuid=99,anongid=100,sec=sys,rw,insecure,root_squash,all_squash)

/mnt/user/Extra Movies

<world>(async,wdelay,hide,no_subtree_check,fsid=110,anonuid=99,anongid=100,sec=sys,rw,insecure,root_squash,all_squash)

/mnt/user/HD Backups

<world>(async,wdelay,hide,no_subtree_check,fsid=105,anonuid=99,anongid=100,sec=sys,rw,insecure,root_squash,all_squash)

/mnt/user/Heidis TV

<world>(async,wdelay,hide,no_subtree_check,fsid=108,anonuid=99,anongid=100,sec=sys,rw,insecure,root_squash,all_squash)

/mnt/user/Marks TV

<world>(async,wdelay,hide,no_subtree_check,fsid=107,anonuid=99,anongid=100,sec=sys,rw,insecure,root_squash,all_squash)

/mnt/user/Music

<world>(async,wdelay,hide,no_subtree_check,fsid=102,anonuid=99,anongid=100,sec=sys,rw,insecure,root_squash,all_squash)

/mnt/user/Pictures and Movies

<world>(async,wdelay,hide,no_subtree_check,fsid=109,anonuid=99,anongid=100,sec=sys,rw,insecure,root_squash,all_squash)

/mnt/user/TV Series

<world>(async,wdelay,hide,no_subtree_check,fsid=103,anonuid=99,anongid=100,sec=sys,rw,insecure,root_squash,all_squash)

/mnt/user/appdata

<world>(async,wdelay,hide,no_subtree_check,fsid=113,anonuid=99,anongid=100,sec=sys,rw,insecure,root_squash,all_squash)

That looks normal to me. Does Kodi connect again if you downgrade back to 7.2.4?

Yes, I works fine when i downgrade to 7.2.4 . I first tried 7.2.5 and then when 7.3.0 came out i tried again with no success. Maybe Ill try and swith to V3 and see if that works for now.

If the client is SMB capable, it may also be worth changing it since NFS tends to me more problematic, mostly meaning not as well tested.

I switched client and server side to V3 security and its working again. I've thought about switching to SMB but would need to rescan a 4000+ movie library. Ill probably end up doing that eventually. Thanks for your help.

How are you mounting in Kodi? I had some similar issues a long while back with some NFS hosts connecting to unraid. It might not be the same, but I found I had to add "fstype=nfs4" to the mount point configs.

Edited May 27May 27 by warpspeed

11 hours ago, warpspeed said:

How are you mounting in Kodi? I had some similar issues a long while back with some NFS hosts connecting to unraid. It might not be the same, but I found I had to add "fstype=nfs4" to the mount point configs.

Manually in kodi

nfs://192.168.1.128/mnt/user/

So i just add that to my Kodi sources config file? or advanced settings?

Thank you.

Use autofs or fstab rather than doing it in Kodi

autofs is best

Hello, I would like to pitch in.

This morning I updated Unraid from 7.2.6 to 7.3.1, and I can't access my NFS shares, and SMB is out of the question.

I use CachyOS on my PC, and SMB and Dolphin file manager have some weird shennanigans in which they corrupt data when transfering cause of some cache stuff, it's a bug. That's why I moved over to NFS. Well I know it's not a CachyOS problem cause I also have a NFS connection in the same network to a Synology NAS, and that works flawless. I haven't touched the fstab file, but "sudo mount -a" returns: mount.nfs: Connection refused for "server.ip". I've tried restarting and checking NFS settings and share settings on Unraid, but I haven't found anything useful. I'm considering reverting to 7.2.6. Any Clues? Thanks

23 minutes ago, YoussefAFdez said:

Hello, I would like to pitch in.

This morning I updated Unraid from 7.2.6 to 7.3.1, and I can't access my NFS shares, and SMB is out of the question.

I use CachyOS on my PC, and SMB and Dolphin file manager have some weird shennanigans in which they corrupt data when transfering cause of some cache stuff, it's a bug. That's why I moved over to NFS. Well I know it's not a CachyOS problem cause I also have a NFS connection in the same network to a Synology NAS, and that works flawless. I haven't touched the fstab file, but "sudo mount -a" returns: mount.nfs: Connection refused for "server.ip". I've tried restarting and checking NFS settings and share settings on Unraid, but I haven't found anything useful. I'm considering reverting to 7.2.6. Any Clues? Thanks

Update in my own message, I followed https://www.reddit.com/r/unRAID/comments/1mev15l/nfs_suddenly_stopped_working/, and managed to get it working again, something weird that might happen from time to time I guess, I can connect again.

When browsing shares it times out and I'm getting a lot of these errors. I guess its time to switch to slow SMB 🙄

May 29 08:50:28 Tower kernel: svc: svc_tcp_read_marker nfsd RPC fragment too large: 30997541

May 29 08:50:28 Tower kernel: svc: svc_tcp_read_marker nfsd RPC fragment too large: 16777216

May 29 08:50:28 Tower kernel: svc: svc_tcp_read_marker nfsd RPC fragment too large: 30997541

May 29 08:50:28 Tower kernel: svc: svc_tcp_read_marker nfsd RPC fragment too large: 30997541

May 29 08:50:28 Tower kernel: svc: svc_tcp_read_marker nfsd RPC fragment too large: 16777216

May 29 08:50:28 Tower kernel: svc: svc_tcp_read_marker nfsd RPC fragment too large: 1008207064

Edited May 29May 29 by mhaaland

I'm having none of those problems. The only issue I have right now is when I turn on Exclusive Shares, they don't show up in NFS. But that's easily mitigated by turning off Exclusive Shares.

i upgraded to unraid 7.3.1had the same issue and kodi gave me this error.

NFS: Failed to mount nfs share: / (mount_cb: NFS4: SETCLIENTID (path /) failed with NFS4ERR_MINOR_VERS_MISMATCH(-5))

Switched back to nfsv3 in unraid and in kodi and its working again.

I have been using NFS v3 since Unraid v6. With the announcement about v4 support in 7.3.1 I had the same problem as the OP ie Kodi v21.3 can't connect to Unraid NFS server using NFS v4 (NFS v3 continues to work fine. Note that after changing the Kodi client to use v4, the Library source was also edited to exclude the physical path to the share root, as I understand is necessary with NFS v4)

The Kodi log reports, NFS4: SETCLIENTID (path /) failed with NFSv4ERR_MINOR_VERS_MISMATCH (-5) after a connect failure. On the server, the "/proc/fs/nfsd/versions" file has
+3 +4 -4.0 -4.1 -4.2
perhaps consistent with the Kodi failure message if Kodi v21.3 can only support v4.0 of NFS v4.

Is there any way to allow NFS v4.0 on Unraid ?

(While Unraid & Kodi are on the same Gigabit LAN, when I was using SMB on Unraid v6, it wasn't possible to play 2160p movies without pausing, stuttering & loss of audio. NFS v3 allowed such movies to be watchable. I was hoping for additional performance benefits, compared to NFS v3, with v4)

Edited June 1Jun 1 by anwsmh

As I've previously posted, I'm using NFSv4 just fine with Kodi.

What I'm doing:

Using autofs or fstab directly on the host, don't configure NFS directly from Kodi itself. i.e. do not do it in the GUI, do it from the command line using fstab or autofs (autofs recommended, it's more resilient)

Then set Kodi to use the NFS mounted path for media

Set unraid NFS Max Protocol setting to NFSv4.

I have my unraid shares using 'sec=sys,anonuid=99,anongid=100,all_squash'

Using fstab, I have the mounts basically using defaults

Using autofs, I found I had to add 'fstype=nfs4' to the NFS config

Exclusive Shares disabled

Edited June 1Jun 1 by warpspeed

1 hour ago, warpspeed said:

As I've previously posted, I'm using NFSv4 just fine with Kodi.

What I'm doing:

Using autofs or fstab directly on the host, don't configure NFS directly from Kodi itself. i.e. do not do it in the GUI, do it from the command line using fstab or autofs (autofs recommended, it's more resilient)

Then set Kodi to use the NFS mounted path for media

Set unraid NFS Max Protocol setting to NFSv4.

I have my unraid shares using 'sec=sys,anonuid=99,anongid=100,all_squash'

Using fstab, I have the mounts basically using defaults

Using autofs, I found I had to add 'fstype=nfs4' to the NFS config

Exclusive Shares disabled

Just now, anwsmh said:

  1 hour ago, warpspeed said:

As I've previously posted, I'm using NFSv4 just fine with Kodi.
What I'm doing:

Using autofs or fstab directly on the host, don't configure NFS directly from Kodi itself. i.e. do not do it in the GUI, do it from the command line using fstab or autofs (autofs recommended, it's more resilient)

Thank you warpspeed. I will give it a try although my Kodi is on an unfamiliar platform (Kodi for Android) and I am not sure I can get at autofs.
Apparently there is no autofs in Android (and the A distro I am using is nailed down by Amazon), so I can't use your suggestion. From AI,

"No, Android does not have a native equivalent to autofs for mounting NFS shares.

Unlike standard Linux distributions, Android lacks the autofs daemon and does not support on-demand mounting of NFS shares out of the box. Accessing NFS on Android requires manual intervention or third-party workarounds, and almost always requires root access"

Edited June 1Jun 1 by anwsmh

Perhaps the variant of Android you're using only works with NFSv3.

I'm using Kodi on Debian based systems.

i.e. not a fault of unraid, but rather an Android system limitation

Edited June 1Jun 1 by warpspeed

2 hours ago, warpspeed said:

Perhaps the variant of Android you're using only works with NFSv3.

I'm using Kodi on Debian based systems.

i.e. not a fault of unraid, but rather an Android system limitation

I agree, not Unraid's fault. Iits only happening on my 21.3 Coreelec Kodi builds. Firestick Android is working fine. Not sure why everything changed after version 7.2.4 though? I can play movie files from my library using NFS but when i try to add or browse a shares or update the library it cannot connect and Unraid spits out these errors.

Jun 1 08:03:21 Tower kernel: svc: svc_tcp_read_marker nfsd RPC fragment too large: 1416127776

Jun 1 08:03:21 Tower kernel: svc: svc_tcp_read_marker nfsd RPC fragment too large: 891879424

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.

Edited June 1Jun 1 by dedi

5 hours ago, dedi said:

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):

What about the NFS version setting in the NFS settings in the unraid GUI?