Mount NFS share no longer works after upgrade

Hello folks,

I was on OpenWRT 15.05 for a long time and just upgraded to version 18.06.4. Did an upgrade WITHOUT saving any config files, since I wanted a fresh install...

Anyhow, the only thing that doesn't seem to work is mounting an NFS share located on my NAS along side my router.

I know my NFS share isn't NFSv4, but rather v3 or v2. Not sure which though...

I've got the following NFS packages installed on my router:

kmod-fs-nfs - 4.9.184-1
kmod-fs-nfs-common - 4.9.184-1
nfs-utils - 2.3.3-3

My exported NFS share on server looks like:

root@server:~# cat /etc/exports
/mnt/HD/Folder 192.168.2.0/24(rw,all_squash,no_wdelay,insecure_locks,insecure,no_subtree_check,anonuid=1001,anongid=508)

I used to be able to mount my NFS share (only a particular folder within it) from my router using:

mount -t nfs server:/mnt/HD/Folder/DATA/Tinyproxy /www/tinyproxy -o nolock

This no longer works since I'm now getting:

root@OpenWrt:~# mount -t nfs server:/mnt/HD/Folder/DATA/Tinyproxy /www/tinyproxy -o nolock
mount.nfs: Protocol not supported
mount: mounting 192.168.2.2:/mnt/HD/Folder/DATA/Tinyproxy on /www/tinyproxy failed: Protocol not supported

Additionally, here's the verbose mode, and I've also tried forcing version 2...

root@OpenWrt:~# mount.nfs 192.168.2.2:/mnt/HD/Folder/DATA/Tinyproxy /www/tinyproxy -o nolock -v
mount.nfs: timeout set for Thu Sep 26 15:40:10 2019
mount.nfs: trying text-based options 'nolock,vers=4.2,addr=192.168.2.2,clientaddr=192.168.2.1'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'nolock,vers=4,minorversion=1,addr=192.168.2.2,clientaddr=192.168.2.1'
mount.nfs: mount(2): Invalid argument
mount.nfs: trying text-based options 'nolock,vers=4,addr=192.168.2.2,clientaddr=192.168.2.1'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'nolock,addr=192.168.2.2'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.2.2 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.2.2 prog 100005 vers 3 prot UDP port 2049
mount.nfs: mount(2): Protocol not supported
mount.nfs: Protocol not supported

# FORCING NFS v2... 
root@OpenWrt:~# mount.nfs 192.168.2.2:/mnt/HD/Folder/DATA/Tinyproxy /www/tinyproxy -o nolock,vers=2 -v
mount.nfs: timeout set for Thu Sep 26 15:40:40 2019
mount.nfs: trying text-based options 'nolock,vers=2,addr=192.168.2.2'
mount.nfs: prog 100003, trying vers=2, prot=6
mount.nfs: trying 192.168.2.2 prog 100003 vers 2 prot TCP port 2049
mount.nfs: portmap query retrying: RPC: Program/version mismatch
mount.nfs: prog 100003, trying vers=2, prot=17
mount.nfs: trying 192.168.2.2 prog 100003 vers 2 prot UDP port 2049
mount.nfs: portmap query failed: RPC: Program/version mismatch
mount.nfs: Protocol not supported

Any ideas for me ? I can't figure this one out... :frowning:

Many thanks for your help.

Cheers. Pat

1 Like

https://openwrt.org/docs/guide-user/services/nas/nfs.client

mount -t nfs4 192.168.1.101:/share /mnt/point -o nolock
mount -t nfs 192.168.255.124:/share /mnt/point -o nfsvers=3 -o nolock

I tried this.. always getting "mount.nfs: Protocol not supported". ... :frowning:

kmod-fs-nfs-v3 - Kernel module for NFS v3 client support
1 Like

Found it! Turns out I was missing the kmod-fs-nfs-v3 package on my router..

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.