[SOLVED] Cannot mount NFS share anymore

[Lucas Rey]

Dear community, I'm in trouble with mounting NFS share, previously it worked fine.

From CLI I got:

# mount -v -t nfs 192.168.10.6:/mnt/tank/backup_vm_proxmox /mnt
mount.nfs: timeout set for Mon May 16 08:04:22 2022
mount.nfs: trying text-based options 'vers=4.2,addr=192.168.10.6,clientaddr=192.168.10.2'
mount.nfs: mount(2): Permission denied
mount.nfs: access denied by server while mounting 192.168.10.6:/mnt/tank/backup_vm_proxmox

The error seem indicates a server permission error, but from any other server I can mount it without any issue, and NFS permission allow 192.168.10.0/24 network. Same error from GUI.

# pvesm nfsscan 192.168.10.6
/mnt/tank/backup_vm_proxmox 192.168.10.0

The issue is starting while I update the pve-kernel to 5.15, but I got it also booting proxmox with previous kernel version 5.13.
As I wrote, I tried to mount the same NFS share from 3 servers and I got no issue.
For now I moved the share to SAMBA, so my VMs, having disk on NAS, can start without issue.

IMPORTANT: Yesteday I updated TrueNAS from v12 to v13. TrueNAS is the machine that handle the NFS Server.
I don't know if this could be the root cause, yesterday I rebooted TrueNAS and Proxmox doesn't have any issue on NFS, the issue appear after today I reboot Proxmox itself.

My PVE Version:

pveversion -v
proxmox-ve: 7.2-1 (running kernel: 5.13.19-6-pve)
pve-manager: 7.2-3 (running version: 7.2-3/c743d6c1)
pve-kernel-5.15: 7.2-3
pve-kernel-helper: 7.2-3
pve-kernel-5.13: 7.1-9
pve-kernel-5.11: 7.0-10
pve-kernel-5.4: 6.4-4
pve-kernel-5.15.35-1-pve: 5.15.35-3
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-4-pve: 5.13.19-9
pve-kernel-5.13.19-3-pve: 5.13.19-7
pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-5.13.19-1-pve: 5.13.19-3
pve-kernel-5.11.22-7-pve: 5.11.22-12
pve-kernel-5.11.22-5-pve: 5.11.22-10
pve-kernel-5.11.22-4-pve: 5.11.22-9
pve-kernel-5.11.22-3-pve: 5.11.22-7
pve-kernel-5.11.22-2-pve: 5.11.22-4
pve-kernel-5.4.124-1-pve: 5.4.124-1
pve-kernel-5.4.73-1-pve: 5.4.73-1
ceph-fuse: 14.2.21-1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: residual config
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-8
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.1-6
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-1
libpve-storage-perl: 7.2-2
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.12-1
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.1.8-1
proxmox-backup-file-restore: 2.1.8-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-10
pve-cluster: 7.2-1
pve-container: 4.2-1
pve-docs: 7.2-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.4-2
pve-ha-manager: 3.3-4
pve-i18n: 2.7-1
pve-qemu-kvm: 6.2.0-6
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-2
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.4-pve1

Any clue?
Thank you
Lucas

 

[StreetPiet]

Maybe it is a similar Problem to this: Some Users lost the NFS connection to their QNAP NAS after Upgrading to Proxmox VE 7.2-3. Maybe take a look at this Thread: https://forum.proxmox.com/threads/issue-after-upgrade-to-7-2-3.109003/page-2#post-469160

 

[Lucas Rey]

SOLVED:
It seems that TrueNAS introduced a new security level on version 13. Not sure why Proxmox can't handle this new security while other systems doesn't have any issue with it. I'm investingating. In the meantime I just disable this extra security setting on TrueNAS itself.

Now the /etc/exports on TrueNAS looks like:

V4: / -sec=sys
/mnt/tank/backup_vm_proxmox -quiet -mapall="root":"wheel"

While before was:

V4: / -sec=krb5:krb5i:krb5p
/mnt/tank/backup_vm_proxmox -quiet -mapall="root":"wheel"