Problem to mount a QNAP over NFS

[ziur]

Good Morning,

In a laboratory with several PROXMOX all with the version mentioned below and that package, it is impossible for me to mount an exposed resource by NFS (tested with version 2 and version 3), I leave you below capture of the error ...

# pveversion --verbose proxmox-ve: 6.2-1 (running kernel: 5.4.34-1-pve) pve-manager: 6.2-4 (running version: 6.2-4/9824574a) pve-kernel-5.4: 6.2-1 pve-kernel-helper: 6.2-1 pve-kernel-5.4.34-1-pve: 5.4.34-2 ceph-fuse: 12.2.11+dfsg1-2.1+b1 corosync: 3.0.3-pve1 criu: 3.11-3 glusterfs-client: 5.5-3 ifupdown: 0.8.35+pve1 ksm-control-daemon: 1.3-1 libjs-extjs: 6.0.1-10 libknet1: 1.15-pve1 libproxmox-acme-perl: 1.0.3 libpve-access-control: 6.1-1 libpve-apiclient-perl: 3.0-3 libpve-common-perl: 6.1-2 libpve-guest-common-perl: 3.0-10 libpve-http-server-perl: 3.0-5 libpve-storage-perl: 6.1-7 libqb0: 1.0.5-1 libspice-server1: 0.14.2-4~pve6+1 lvm2: 2.03.02-pve4 lxc-pve: 4.0.2-1 lxcfs: 4.0.3-pve2 novnc-pve: 1.1.0-1 proxmox-mini-journalreader: 1.1-1 proxmox-widget-toolkit: 2.2-1 pve-cluster: 6.1-8 pve-container: 3.1-5 pve-docs: 6.2-4 pve-edk2-firmware: 2.20200229-1 pve-firewall: 4.1-2 pve-firmware: 3.1-1 pve-ha-manager: 3.0-9 pve-i18n: 2.1-2 pve-qemu-kvm: 5.0.0-2 pve-xtermjs: 4.3.0-1 qemu-server: 6.2-2 smartmontools: 7.1-pve2 spiceterm: 3.1-1 vncterm: 1.6-1 zfsutils-linux: 0.8.3-pve1






Thanks greetings!

 

[Dominic]

I think rpcbind must be available on your server. You should see that in nmap.

PORT     STATE SERVICE
111/tcp  open  rpcbind
2049/tcp open  nfs

 

[ziur]

 

[Dominic]

Have you just changed that or has that already been working before? What is

rpcinfo -p 10.102.23.10

? Permissions for NFS could be an additional problem.

 

[ziur]

Good afternoon,

The permissions in the qnap are the same that I use in others for other clients ...









Thanks greetings!

 

[ziur]

Good afternoon, any more ideas with the latest screenshots attached?

Thanks greetings!

 

[SoMoney]

Good afternoon, any more ideas with the latest screenshots attached?

Thanks greetings!

I had similar issue with when my NFS and Proxmox IP's changed

From the QNAP Under "Edit Shared Folder Permission"
Select the folder you are sharing to proxmox
Select NFS Host Access
Make sure you host/ip/network matched to what you are actually using.

 

[ziur]

I just checked the configuration you mention and I see everything correct, something else that you can think of?

 

[ziur]

Any more ideas?

 

[ziur]

hello?

 

[ziur]

 

[hektop]

Ziur,

I ran into a similar problem as you. I was able to make it work by setting the following on my QNAP. I'm running Proxmox version 7.1-7 and QNAP 4.3.6.1907.

disable NFS v2 and v3
enable NFS v4
set the shared folder squash option as NO_ROOT_SQUASH

 

[ZoliBen]

Ziur,

I ran into a similar problem as you. I was able to make it work by setting the following on my QNAP. I'm running Proxmox version 7.1-7 and QNAP 4.3.6.1907.

disable NFS v2 and v3
enable NFS v4
set the shared folder squash option as NO_ROOT_SQUASH

Thanks a lot hektop, I have a similar setup with a QNAP NFS share mounted as the backup target. Disabling NFSv2 and 3 solved the kernel panic which eventually lead to the proxmox host crashing but the guest VMs still being accessible.

To add something to the topic:

In newer QNAP firmware, NO_ROOT_SQUASH is renamed to SQUASH_NO_USERS. Reference table from QNAP FAQ page below.