NFS mounting issues

[Viktor Jaep]

I also tried Victa Jaep new backupmon.sh that implemented those changes

curl --retry 3 "https://raw.githubusercontent.com/ViktorJp/BACKUPMON/develop/backupmon.sh" -o "/jffs/scripts/backupmon.sh" && chmod 755 "/jffs/scripts/backupmon.sh"

Still error bad file descriptor.
Reverted back to unchanged backupmon.sh

Can you try this:

mkdir -m 755 -p "/var/lib/nfs"
modprobe nfs nfsv3
portmap

...then try your mount statement

 

[pedeb04]

Can you try this:

mkdir -m 755 -p "/var/lib/nfs"
modprobe nfs nfsv3
portmap

...then try your mount statement

Still the same, bad file descriptor.

server /etc/exports
I've tried
/srv/nfsshared 192.168.50.0/24(rw,root_squash,anonuid=1000,anongid=1000)
/srv/nfsshared 192.168.50.0/24(rw,no_root_squash,anonuid=1000,anongid=1000)
/srv/nfsshared 192.168.50.0/24(rw,root_squash)

 

[Jeffrey Young]

What are the permissions on your server? Try setting 777 as a tes (allow everything for everyone).

 

[Jeffrey Young]

Also make sure your NAS allows nvfv3 connections.

 

[Jeffrey Young]

I just remembered.... I believe I read in the changelog for 1006 firmware that NFS is broken. I am away from home now for a few days, I will check later. I am running 388 codebase on my ax86u pro.

 

[pedeb04]

Changed permissions to 777 on server /srv/sfsshared, nfsv3 is enabled by default on server. no change.

 

[bennor]

I just remembered.... I believe I read in the changelog for 1006 firmware that NFS is broken. I am away from home now for a few days, I will check later. I am running 388 codebase on my ax86u pro.

The 3006.102.x Asus-Merlin Change Log only mentions NFS not supported on WiFi 7 devices.

3006.102.1 (28-Jun-2024)
...
- NOTE: Wifi 7 devices don't support NFS (issue with new
toolchain), QoS classification page (issue with
TrendMicro BWDPI) or Wifi Radar (not updated by
Broadcom).

 

[Jeffrey Young]

The 3006.102.x Asus-Merlin Change Log only mentions NFS not supported on WiFi 7 devices.

Ok. Thanks @bennor I knew I read something about NFS not working on something. You saved me looking it up.

@pedeb04 , I am afraid that I am out of ideas. Bad file descriptor is usually a sign that a permission issue exists. Mind me asking what you are using as a NAS?

Using the modified steps from above, I am able to mount an NFS share that I have set up as a test on a Ubuntu 22.04 bare metal machine. I'll send you my export contents later today when home. I do use a couple other options, but I doubt they would make a difference.

 

[pedeb04]

I am using Ubuntu server 24.04 and my Desktop is Ubuntu 24.04
When I mount the nfs share on the server from the desktop I notice the nfsvers=4.2

peter@nuc:~$ nfsstat -m
/mnt/nfs from 192.168.50.46:/srv/nfsshared
 Flags:    rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.50.175,local_lock=none,addr=192.168.50.46

If I try to mount using nfsvers=3 from the desktop but it times out.
I've tried to find a way to change/configure the server nfs export share to nfs3 with no luck so far. I'm thinking this is where the issue is.

 

[Jeffrey Young]

I am using Ubuntu server 24.04 and my Desktop is Ubuntu 24.04
When I mount the nfs share on the server from the desktop I notice the nfsvers=4.2

peter@nuc:~$ nfsstat -m
/mnt/nfs from 192.168.50.46:/srv/nfsshared
 Flags:    rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.50.175,local_lock=none,addr=192.168.50.46

If I try to mount using nfsvers=3 from the desktop but it times out.
I've tried to find a way to change/configure the server nfs export share to nfs3 with no luck so far. I'm thinking this is where the issue is.

I figured it was going to be a server/permission issue. Not a lost exercise as we learned that some additional steps to get NFS working on the router with some models may be required.

Give this a try -

On your server, add the insecure option to your export line.

NFSv3 uses port 2049 (I think) primarily and port 111 is used by portmap. NFVv4 consolidated the port usage to just port 2049. In secure mode, NFSv4 prevents any port usage below port 1024. To allow NFSv3, you need to tell the server to allow port 111, which is the insecure option. This is a very rough description (getting ready to head out for the week - best I could google for now).

 

[Jeffrey Young]

Also, if you are using a firewall on your server, try turning it off. Your firewall may be blocking Port 111.