[SOLVED] mount.nfs: Protocol not supported

A

Andrey G

Active Member
Sep 21, 2017
5
1
41
39
Hello.
I try to connect my NAS folder to Proxmox as NFS share.
NAS: Thecus N2310. It supports sharing folder via NFS. It is configured via web, but command line (linux) is also available. (IP 192.168.10.3)
Proxmox:
proxmox-ve: 4.4-94 (running kernel: 4.4.35-1-pve)
pve-manager: 4.4-18 (running version: 4.4-18/ef2610e8)
pve-kernel-4.4.35-1-pve: 4.4.35-77
pve-kernel-4.4.21-1-pve: 4.4.21-71
pve-kernel-4.4.76-1-pve: 4.4.76-94
lvm2: 2.02.116-pve3
corosync-pve: 2.4.2-2~pve4+1
libqb0: 1.0.1-1
pve-cluster: 4.0-52
qemu-server: 4.0-111
pve-firmware: 1.1-11
libpve-common-perl: 4.0-96
libpve-access-control: 4.0-23
libpve-storage-perl: 4.0-76
pve-libspice-server1: 0.12.8-2
vncterm: 1.3-2
pve-docs: 4.4-4
pve-qemu-kvm: 2.7.1-4
pve-container: 1.0-101
pve-firewall: 2.0-33
pve-ha-manager: 1.0-41
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u3
lxc-pve: 2.0.7-4
lxcfs: 2.0.6-pve1
criu: 1.6.0-1
novnc-pve: 0.5-9
smartmontools: 6.5+svn4324-1~pve80
rpcinfo -p 192.168.10.3
program vers proto port service
100000 4 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
100021 1 udp 37725 nlockmgr
100021 3 udp 37725 nlockmgr
100021 4 udp 37725 nlockmgr
100021 1 tcp 51125 nlockmgr
100021 3 tcp 51125 nlockmgr
100021 4 tcp 51125 nlockmgr
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100005 1 udp 20048 mountd
100005 1 tcp 20048 mountd
100005 2 udp 20048 mountd
100005 2 tcp 20048 mountd
100005 3 udp 20048 mountd
100005 3 tcp 20048 mountd
100024 1 udp 38468 status
100024 1 tcp 42577 status
pvesm nfsscan 192.168.10.3
/raid0/data/_NAS_NFS_Exports_/test2 192.168.10.90
/raid0/data/_NAS_NFS_Exports_/010-anessi *
/raid0/data/_NAS_NFS_Exports_ *
When I try to add nas storage via web gui I receive mount error: mount.nfs: Protocol not supported (500).
When I try manually mount nfs, I get the same:
mount.nfs 192.168.10.3:/raid0/data/_NAS_NFS_Exports_/010-anessi /mnt/pve/nas -wv -o vers=3
mount.nfs: timeout set for Thu Sep 21 12:29:56 2017
mount.nfs: trying text-based options 'vers=3,addr=192.168.10.3'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.10.3 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.10.3 prog 100005 vers 3 prot UDP port 20048
mount.nfs: mount(2): Protocol not supported
mount.nfs: Protocol not supported
But from Ubuntu host I mount this share successfully.
What I do wrong with Proxmox?
 
Last edited:
Found in /var/log/syslog
nfsv4: disagrees about version of symbol module_layout
same for nfsv3
any ideas?
 
Andrey G said:
Found in /var/log/syslog
nfsv4: disagrees about version of symbol module_layout
same for nfsv3
any ideas?
Click to expand...
Hi

this is typically a outdated kernel .... message loading nfs ...
modinfo should read:
Code: 
 modinfo nfs
filename:       /lib/modules/4.10.17-3-pve/kernel/fs/nfs/nfs.ko
license:        GPL
author:         Olaf Kirch <okir@monad.swb.de>
alias:          nfs4
alias:          fs-nfs4
alias:          fs-nfs
srcversion:     A4D41D66D76225578FFA720
depends:        fscache,sunrpc,lockd
intree:         Y
vermagic:       4.10.17-3-pve SMP mod_unload modversions
parm:           callback_tcpport:portnr
parm:           callback_nr_threads:Number of threads that will be assigned to the NFSv4 callback channels. (ushort)
parm:           nfs_idmap_cache_timeout:int
parm:           nfs4_disable_idmapping:Turn off NFSv4 idmapping when using 'sec=sys' (bool)
parm:           max_session_slots:Maximum number of outstanding NFSv4.1 requests the client will negotiate (ushort)
parm:           max_session_cb_slots:Maximum number of parallel NFSv4.1 callbacks the client will process for a given server (ushort)
parm:           send_implementation_id:Send implementation ID with NFSv4.1 exchange_id (ushort)
parm:           nfs4_unique_id:nfs_client_id4 uniquifier string (string)
parm:           recover_lost_locks:If the server reports that a lock might be lost, try to recover it risking data corruption. (bool)
parm:           enable_ino64:bool
parm:           nfs_access_max_cachesize:NFS access maximum total cache length (ulong)

[\code]
 
My is
Code: 
filename:       /lib/modules/4.4.35-1-pve/kernel/fs/nfs/nfs.ko
license:        GPL
author:         Olaf Kirch <okir@monad.swb.de>
alias:          nfs4
alias:          fs-nfs4
alias:          fs-nfs
srcversion:     E8CE5FE61CAC2E37CFFD876
depends:        fscache,sunrpc,lockd
intree:         Y
vermagic:       4.4.35-1-pve SMP mod_unload modversions
parm:           callback_tcpport:portnr
parm:           nfs_idmap_cache_timeout:int
parm:           nfs4_disable_idmapping:Turn off NFSv4 idmapping when using 'sec=sys' (bool)
parm:           max_session_slots:Maximum number of outstanding NFSv4.1 requests the client will negotiate (ushort)
parm:           send_implementation_id:Send implementation ID with NFSv4.1 exchange_id (ushort)
parm:           nfs4_unique_id:nfs_client_id4 uniquifier string (string)
parm:           recover_lost_locks:If the server reports that a lock might be lost, try to recover it risking data corruption. (bool)
parm:           enable_ino64:bool
parm:           nfs_access_max_cachesize:NFS access maximum total cache length (ulong)
How can I upgrade to nfs newest version?
 
Andrey G said:
My is
Code: 
filename:       /lib/modules/4.4.35-1-pve/kernel/fs/nfs/nfs.ko
license:        GPL
author:         Olaf Kirch <okir@monad.swb.de>
alias:          nfs4
alias:          fs-nfs4
alias:          fs-nfs
srcversion:     E8CE5FE61CAC2E37CFFD876
depends:        fscache,sunrpc,lockd
intree:         Y
vermagic:       4.4.35-1-pve SMP mod_unload modversions
parm:           callback_tcpport:portnr
parm:           nfs_idmap_cache_timeout:int
parm:           nfs4_disable_idmapping:Turn off NFSv4 idmapping when using 'sec=sys' (bool)
parm:           max_session_slots:Maximum number of outstanding NFSv4.1 requests the client will negotiate (ushort)
parm:           send_implementation_id:Send implementation ID with NFSv4.1 exchange_id (ushort)
parm:           nfs4_unique_id:nfs_client_id4 uniquifier string (string)
parm:           recover_lost_locks:If the server reports that a lock might be lost, try to recover it risking data corruption. (bool)
parm:           enable_ino64:bool
parm:           nfs_access_max_cachesize:NFS access maximum total cache length (ulong)
How can I upgrade to nfs newest version?
Click to expand...

strange i bet your modinfo would issue a error ...

so to find out the module complaining "disagrees about version of symbol module_layout" ... by dmesg

perhaps a "apt-get update && apt-get dist-upgrade " will solve your problem ....
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back