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

  • Solved
  • Minor

Hello,

 

I've been trying for a while to mount a NFS drive on another server using NFS v4.2. And every time, it fallback 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, completely 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)

 

 

It looks like an oversight in either Unraid configuration of NFS Mount or missing kernel config or some issue in slackware ? It's hard to say what's the cause, since Unraid support v4.1 and v4.2 as a Server which lead me to think its configuration issue somewhere.

 

I've asked for support to confirm the issue before opening this ticket.

 

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.