mount.nfs: No such device

[travishardiman]

Hi, I'm trying to create an nfs share but I can't seem to connect to it.

Code:

❯ sudo mount -vvv -t nfs 192.168.1.7:/mnt/pool/PlexData/ /mnt/Plex
mount.nfs: timeout set for Sun Jun 11 13:20:52 2023
mount.nfs: trying text-based options 'vers=4.2,addr=192.168.1.7,clientaddr=192.168.1.90'
mount.nfs: mount(2): No such device
mount.nfs: No such device

 

[travishardiman]

NFS is enabled and these are the settings:

 

[sretalla]

You aren't being clear about where you're mounting it.

Is that in a plex jail? (seems we're on CORE here)

Is it from an external box (linux?)?

Maybe you need to think about permissions or disabling NFSV4 (enables NFSv3)

 

[travishardiman]

The client PC I am trying to use to mount it is a framework laptop running Pop!_OS 22.04 LTS (jammy).

TrueNAS CORE 13.0-U5.1 and it is in a plex jail.

I have tried unchecking NFSv4 and specifying the v3 option but I get similar messages:

Code:

❯ sudo mount -vvv -t nfs -o vers=3 192.168.1.7:/mnt/pool/PlexData/ /mnt/Plex
mount.nfs: timeout set for Mon Jun 12 08:39:02 2023
mount.nfs: trying text-based options 'vers=3,addr=192.168.1.7'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.1.7 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.1.7 prog 100005 vers 3 prot UDP port 725
mount.nfs: mount(2): No such device
mount.nfs: No such device

If I run showmount I can see it:

Code:

❯ showmount -e 192.168.1.7
Export list for 192.168.1.7:
/mnt/pool/PlexData  192.168.1.0

In the nfs settings I have the mountall set to root:wheel.

 

[kwerti]

hi did you solve this issue?

 

[kwerti]

my issue was solved through this link

https://www.linuxquestions.org/questions/linux-networking-3/nfs-client-mount-nfs-mount-2-no-such-device-4175610087/

my client was running alpine linux 3.18.3. somehow kernel got upgraded to "6.1.50-0-lts" but was looking for NFS modules in "/lib/modules/6.1.49-0-lts".

nextcloud:/mnt# modprobe nfs
modprobe: FATAL: Module nfs not found in directory /lib/modules/6.1.49-0-lts

all I did was reboot the server and made sure rpc.statd was running

modprobe nfs
rc-service rpc.statd start
rc-status

 

[travishardiman]

hi did you solve this issue?

I didn't.

all I did was reboot the server and made sure rpc.statd was running

Thanks I'll give that a try!

 

[travishardiman]

my issue was solved through this link



my client was running alpine linux 3.18.3. somehow kernel got upgraded to "6.1.50-0-lts" but was looking for NFS modules in "/lib/modules/6.1.49-0-lts".



all I did was reboot the server and made sure rpc.statd was running

My plex server is using the standard FreeBSD 13.1-RELEASE-p7 and the client I'm using to connect is Pop!_OS 22.04 LTS.

Running `modprobe nfs` on the client just has empty output, modprobe doesn't exist for FreeBSD, rc-service isn't available for either distro.

*BUT* it does appear to be working now!

```
❯ sudo mount -vvv -t nfs 192.168.1.7:/mnt/pool/PlexData/ /mnt/Plex
mount.nfs: timeout set for Sat Sep 2 23:48:48 2023
mount.nfs: trying text-based options 'vers=4.2,addr=192.168.1.7,clientaddr=192.168.1.90'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4,minorversion=1,addr=192.168.1.7,clientaddr=192.168.1.90'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4,addr=192.168.1.7,clientaddr=192.168.1.90'
mount.nfs: mount(2): Protocol not supported
Created symlink /run/systemd/system/remote-fs.target.wants/rpc-statd.service → /lib/systemd/system/rpc-statd.service.
mount.nfs: trying text-based options 'addr=192.168.1.7'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.1.7 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.1.7 prog 100005 vers 3 prot UDP port 778
```