Hello,
I have a vim4 and vim3p.
I want to use nfs client on vim4 but on ubuntu 22 and 20 there is some failure, on vim3 its working fine.
By default nfs is not charged in kernel so i get error but when i modprobe nfs and try to mount i get this error
mount.nfs: Protocol not supported
I check all days to find a solution like
-o ver=3
I also tried with nfs4 its always the same problem
Of course i install the package nfs-common
Do anyone have a idea or something to help me
Thanks
Can you share me the test method so I can check on my side.
I have a similar problem:
I need to mount some folders that are hosted on my Qnap 412-ts.
Usually to mount those folder i run
sudo mount -t nfs 192.168.0.100:/share/Multimedia /mounting/point -v
if i run the command on my vim4 i receive:
mount.nfs: timeout set for Tue Jun 21 09:21:49 2022
mount.nfs: trying text-based options 'vers=4.2,addr=192.168.0.100,clientaddr=192.168.0.13'
mount.nfs: mount(2): No such device
mount.nfs: No such device
i use the same command on my kali linux pc and on my raspberry pi and in both cases it works without any issue. On Khadas it seems impossibile to mount any nfs folder.
Have you got any suggestion?
Thanks in advance
Can you load the nfs modules before that?
$ sudo modprobe nfs
$ sudo mount -t nfs 192.168.0.100:/share/Multimedia /mounting/point -v
khadas@Khadas:~$ sudo modprobe nfs
khadas@Khadas:~$ sudo mount -t nfs 192.168.0.100:/share/Multimedia /home/khadas/qnap/ -v
mount.nfs: timeout set for Tue Jun 21 09:34:30 2022
mount.nfs: trying text-based options 'vers=4.2,addr=192.168.0.100,clientaddr=192.168.0.13'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4,minorversion=1,addr=192.168.0.100,clientaddr=192.168.0.13'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4,addr=192.168.0.100,clientaddr=192.168.0.13'
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.0.100'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.0.100 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.0.100 prog 100005 vers 3 prot UDP port 30000
mount.nfs: mount(2): Protocol not supported
mount.nfs: Protocol not supported
This works for me:
$ sudo modprobe nfs
$ sudo modprobe nfsv4
$ sudo mount -t nfs 192.168.31.251:/volume1/SHARING /mnt -v
$ ls /mnt/
Misc '#recycle' Templates Test Tools
$ df -h
Filesystem Size Used Avail Use% Mounted on
tmpfs 796M 11M 786M 2% /run
/dev/rootfs 29G 3.4G 25G 12% /
tmpfs 3.9G 0 3.9G 0% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 3.9G 8.0K 3.9G 1% /tmp
tmpfs 796M 76K 796M 1% /run/user/117
tmpfs 796M 68K 796M 1% /run/user/1000
192.168.31.251:/volume1/SHARING 3.5T 597G 3.0T 17% /mnt
khadas@Khadas:~$ sudo mount -t nfs 192.168.0.100:/Multimedia /home/khadas/qnap/ -v
mount.nfs: timeout set for Tue Jun 21 10:07:38 2022
mount.nfs: trying text-based options 'vers=4.2,addr=192.168.0.100,clientaddr=192.168.0.13'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4,minorversion=1,addr=192.168.0.100,clientaddr=192.168.0.13'
despite the log where you can find the error “protocol not supported” the folder is mounted correctly
This log seems not harmly, can you check your mount point whether it successd?
$ df -h
it works, i can read and write in the mounted folder
khadas@Khadas:~$ df -h
192.168.0.100:/Multimedia 11T 5.1T 5.9T 47% /home/khadas/qnap
Yeah its working, i think i miss to modprobe nfsv4
Ton of thanks i was blocked for few days …