[Solved] NFS-Storage mount error 500 after Update

[Kalle Wisch]

Hi to all Proxmox fans!

I updated to the latest Version of Proxmox and after that
I could not mount same nfs share as before.
'mount error: mount.nfs: an incorrect mount option was specified (500)'

Working nfs mounting:
pveversion -v
proxmox-ve-2.6.32: 3.1-114 (running kernel: 2.6.32-26-pve)
pve-manager: 3.1-24 (running version: 3.1-24/060bd5a6)
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-24-pve: 2.6.32-111
pve-kernel-2.6.32-22-pve: 2.6.32-107
pve-kernel-2.6.32-14-pve: 2.6.32-74
pve-kernel-2.6.32-26-pve: 2.6.32-114
pve-kernel-2.6.32-23-pve: 2.6.32-109
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-2
pve-cluster: 3.0-8
qemu-server: 3.1-8
pve-firmware: 1.0-23
libpve-common-perl: 3.0-9
libpve-access-control: 3.0-8
libpve-storage-perl: 3.0-18
pve-libspice-server1: 0.12.4-2
vncterm: 1.1-6
vzctl: 4.0-1pve4
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.1-1

Not working nfs mounting:
pveversion -v
proxmox-ve-2.6.32: 3.1-121 (running kernel: 2.6.32-27-pve)
pve-manager: 3.1-43 (running version: 3.1-43/1d4b0dfb)
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-27-pve: 2.6.32-121
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-24-pve: 2.6.32-111
pve-kernel-2.6.32-25-pve: 2.6.32-113
pve-kernel-2.6.32-22-pve: 2.6.32-107
pve-kernel-2.6.32-26-pve: 2.6.32-114
pve-kernel-2.6.32-23-pve: 2.6.32-109
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.5-1
pve-cluster: 3.0-12
qemu-server: 3.1-15
pve-firmware: 1.1-2
libpve-common-perl: 3.0-13
libpve-access-control: 3.0-11
libpve-storage-perl: 3.0-19
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-6
vzctl: 4.0-1pve4
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.7-4
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.2-1

If I try it on prompt:
root@proxmox:~# mount.nfs -v NFS-SERVER:/Sicherung /mnt/pve/NAS-NFS/ -o vers=3,nolock -vvv
mount.nfs: timeout set for Wed Feb 19 15:31:20 2014
mount.nfs: trying text-based options 'vers=3,nolock,addr=NFS-SERVER'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying NFS-SERVER prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying NFS-SERVER prog 100005 vers 3 prot UDP port 45924

cat /etc/pve/storage.cfg
dir: local
path /var/lib/vz
content images,iso,vztmpl,rootdir

nfs: NFS-NAS
path /mnt/pve/NFS-NAS
server NFS-SERVER
export /Sicherung
options vers=3
content backup
maxfiles 1

Any ideas?

Greets

 

[Kalle Wisch]

Re: NFS-Storage mount error 500 after Update

Ok.

When I change storage.cfg to
options vers=3,nolock
it works again.

 

[h9k]

Re: NFS-Storage mount error 500 after Update

I had the same problem, except I did not have an NFS share before, I configured it freshly.
But adding nolock to storage.cfg worked.
Thanks for sharing your solution!

 

[Miguel Moreira]

I have something similar


Create storage failed: error with cfs lock 'file-storage_cfg': mount error: mount.nfs: access denied by server while mounting 192.168.1.15:/mnt/NFS (500).

Somebody have idea?

 

[joulester]

I have something similar


Create storage failed: error with cfs lock 'file-storage_cfg': mount error: mount.nfs: access denied by server while mounting 192.168.1.15:/mnt/NFS (500).

Somebody have idea?

same problem here. Any solution's yet?

Edit: solvet it with command "insecure" on the server side. was some error about illegal port.
is this a bad solution?

 

[wolfgang]

Proxmox VE 3.x is not more supported, so please update to a supported version.