Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Unraid (6.12.4) not supporting mounting NFS v4.x

Featured Replies

Hello,

 

I've been trying for a while to mount a nfs drive on another server using nfs v4.2. And everytime, it fallsback to v4.0.
This is really strange since the NFS server configured by Unraid has no issue talking in the v4.2 protocol.

 

Example of mount command:

root@Tower:~# mount -vvvv dolma:/Backs-Movies /tmp/test/
mount.nfs: timeout set for Tue Sep 12 21:01:32 2023
mount.nfs: trying text-based options 'vers=4.2,addr=192.168.42.12,clientaddr=192.168.42.57'
mount.nfs: mount(2): Invalid argument
mount.nfs: trying text-based options 'vers=4,minorversion=1,addr=192.168.42.12,clientaddr=192.168.42.57'
mount.nfs: mount(2): Invalid argument
mount.nfs: trying text-based options 'vers=4,addr=192.168.42.12,clientaddr=192.168.42.57'
dolma:/Backs-Movies on /tmp/test type nfs (rw)

I also tried with another server that I just configured nfs on, completly clean with Raspbian Bookworms.

root@Tower:~# mount -vvvv vpn-mgt:/srv/test /tmp/test/
mount.nfs: timeout set for Tue Sep 12 21:14:18 2023
mount.nfs: trying text-based options 'vers=4.2,addr=192.168.42.8,clientaddr=192.168.42.57'
mount.nfs: mount(2): Invalid argument
mount.nfs: trying text-based options 'vers=4,minorversion=1,addr=192.168.42.8,clientaddr=192.168.42.57'
mount.nfs: mount(2): Invalid argument
mount.nfs: trying text-based options 'vers=4,addr=192.168.42.8,clientaddr=192.168.42.57'
vpn-mgt:/srv/test on /tmp/test type nfs (rw,noatime)

 

 

And if I mount the same share from other machine, no issue using the v4.2 protocol. I'm at a loss, I don't understand why Unraid can't use that protocol for NFS mounts.

Edited by Balor

Solved by Balor

  • Balor changed the title to Unraid (6.12.4) not supporting mounting NFS v4.x
  • Community Expert

You should post this in the Unassigned Devices support thread as it that plugin that handles remote mounts, not the core Unraid system.

  • Author

@itimpiI'm not using Unassigned devices, I'm using good old mount command. The /etc/nfsmount.conf is as it was setup by Unraid 6.12.4.

I'm using docker container with volume that are on NFS drive, I prefer this than having to rely on UD to make the mount point in time for the docker container to use.

 

The version supported by NFS on Unraid is the responsability of LimeTech since those are either kernel config or package configuration.

  • Author

I check with @dlandon and he came to same conclusion as me. The NFS Client of Unraid doesn't supports 4.1 and 4.2 only 3.0 and 4.0.

 

I think that's a bug.

25 minutes ago, Balor said:

I check with @dlandon and he came to same conclusion as me. The NFS Client of Unraid doesn't supports 4.1 and 4.2 only 3.0 and 4.0.

 

I think that's a bug.

Probably more of an oversight, than a bug.

  • 2 months later...
  • Author
  • Solution

Fixed in 6.12.5 (and 6.12.6)

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.