[SOLVED] NFS stops working from PVE

[LooneyTunes]

Hi,
I have set up a NFS on a NAS to backup my VMs to. This has worked fine for some time, but a while back I noticed backups failing due to this error

May 22 08:46:33 pve pvestatd[918]: got timeout
May 22 08:46:33 pve pvestatd[918]: unable to activate storage 'net-NFS' - directory '/mnt/pve/net-NFS' does not exist or is unreachable

This is exclusive to PVE, NFS share works fine from other sources, permission hasn't changed since it worked reliably.

I have tried to remove the affected 'net-NFS' storage and reconfigure it, it seemed to help last time, but hung shortly after. If I enter '/mnt/' I can see the pve folder, but if entering that and do a 'ls -la', it won't return the prompt.

Trying to add the storage again in PVE, it refuses to scan the shared folder, and if entered manually gives an error 500, indicating a permissions error, but why all of a sudden? And what can I do?

Please help

 

[dcsapak]

what is your pveversion -v ?
did you recently update to the new 5.15 kernel and have a qnap nas?
if yes, did you see the known issues section here: https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_7.2

• Setups mounting a QNAP NFS share could not be mounted with NFS version 4.1 with kernel pve-kernel-5.15.30-2-pve - the issue has been mitigated in kernels pve-kernel-5.15.35-2 and above.If your QNAP NFS share cannot be mounted upgrade the kernel and reboot.As an alternative mitigation you can explicitly set the NFS version to 4 (not 4.1 or auto).

 

[LooneyTunes]

Hi, thanks for responding. Please find my answers below

what is your pveversion -v ?

# pveversion -v
proxmox-ve: 7.2-1 (running kernel: 5.15.35-1-pve)
pve-manager: 7.2-4 (running version: 7.2-4/ca9d43cc)
pve-kernel-5.15: 7.2-3
pve-kernel-helper: 7.2-3
pve-kernel-5.13: 7.1-9
pve-kernel-5.15.35-1-pve: 5.15.35-3
pve-kernel-5.15.30-2-pve: 5.15.30-3
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-2-pve: 5.13.19-4
ceph-fuse: 15.2.15-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
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.3.1-1
libpve-access-control: 7.1-8
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-1
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-2
libpve-storage-perl: 7.2-4
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.2.1-1
proxmox-backup-file-restore: 2.2.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
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-2
pve-qemu-kvm: 6.2.0-7
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-3
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.4-pve1

did you recently update to the new 5.15 kernel and have a qnap nas?

No, I use a Synology device

 

[dcsapak]

could try the workaround regardless to see if it is the same (or similar) problem?

edit: oh could you also please post the output of 'mount' ?

 

[LooneyTunes]

Hi,

yesterday I had more time to spend on this, and was surprised to find that this was actually due to DNS config on my part. So am happy to say it had nothing to do with PVE this time

 

[zolitacs]

Hi,

yesterday I had more time to spend on this, and was surprised to find that this was actually due to DNS config on my part. So am happy to say it had nothing to do with PVE this time

I have also this problem:

Dec 09 00:00:45 node6 pvestatd[1205]: got timeout
Dec 09 00:00:45 node6 pvestatd[1205]: unable to activate storage 'DEBIAN-10-DEFAULT' - directory '/mnt/pve/DEBIAN-10-DEFAULT' does not exist or is unreachable

Can you send me the solution?

 

[LooneyTunes]

I'd be happy to, but it had nothing to do with PVE at all, but how I was handling local DNS. So best advice is to verify that works the way you need it to - if infact it is due to same reasons. I hope you find a sollution

 

[seuro]

Hi,

yesterday I had more time to spend on this, and was surprised to find that this was actually due to DNS config on my part. So am happy to say it had nothing to do with PVE this time

I'd be happy to, but it had nothing to do with PVE at all, but how I was handling local DNS. So best advice is to verify that works the way you need it to - if infact it is due to same reasons. I hope you find a sollution

Well ?
What was it ?
What was your mistake ?
How did you fix it ?
You have contributed nothing sir, NOTHING.

 

[LnxBil]

You have contributed nothing sir, NOTHING.

Isn't local DNS enough? The server could not be resolved.

If you have a similar problem, try this on you client:

• ping <nfsserver>
• showmount -e <nfsserver>

this on your server:

• showmount -e
• exportfs