[SOLVED] mount error: mount.nfs: access denied by server

Lxndr

New Member
Aug 28, 2021
9
3
1
49
Hi everyone,

I'm new here but been using Promox at home for quite sometime, so apologies if this is not the right place to post this, I have an issue accessing my NFS share on a Synology NAS running DSM7 to store my VM backups, Error message being:

mount error: mount.nfs: access denied by server while mounting 10.0.1.2:/volume1/VMBackups


pveversion -v results:

root@pve:~# pveversion -v


proxmox-ve: 7.0-2 (running kernel: 5.11.22-3-pve)


pve-manager: 7.0-11 (running version: 7.0-11/63d82f4e)


pve-kernel-5.11: 7.0-6


pve-kernel-helper: 7.0-6


pve-kernel-5.4: 6.4-5


pve-kernel-5.3: 6.1-6


pve-kernel-5.0: 6.0-11


pve-kernel-5.11.22-3-pve: 5.11.22-7


pve-kernel-5.4.128-1-pve: 5.4.128-2


pve-kernel-5.4.106-1-pve: 5.4.106-1


pve-kernel-5.4.78-2-pve: 5.4.78-2


pve-kernel-4.15: 5.4-8


pve-kernel-5.3.18-3-pve: 5.3.18-3


pve-kernel-5.3.13-1-pve: 5.3.13-1


pve-kernel-5.0.21-5-pve: 5.0.21-10


pve-kernel-5.0.21-1-pve: 5.0.21-2


pve-kernel-4.15.18-20-pve: 4.15.18-46


pve-kernel-4.15.17-1-pve: 4.15.17-9


ceph-fuse: 14.2.21-1


corosync: 3.1.2-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.21-pve1


libproxmox-acme-perl: 1.3.0


libproxmox-backup-qemu0: 1.2.0-1


libpve-access-control: 7.0-4


libpve-apiclient-perl: 3.2-1


libpve-common-perl: 7.0-6


libpve-guest-common-perl: 4.0-2


libpve-http-server-perl: 4.0-2


libpve-storage-perl: 7.0-10


libqb0: 1.0.5-1


libspice-server1: 0.14.3-2.1


lvm2: 2.03.11-2.1


lxc-pve: 4.0.9-4


lxcfs: 4.0.8-pve2


novnc-pve: 1.2.0-3


proxmox-backup-client: 2.0.9-2


proxmox-backup-file-restore: 2.0.9-2


proxmox-mini-journalreader: 1.2-1


proxmox-widget-toolkit: 3.3-6


pve-cluster: 7.0-3


pve-container: 4.0-9


pve-docs: 7.0-5


pve-edk2-firmware: 3.20200531-1


pve-firewall: 4.2-2


pve-firmware: 3.2-4


pve-ha-manager: 3.3-1


pve-i18n: 2.4-1


pve-qemu-kvm: 6.0.0-3


pve-xtermjs: 4.12.0-1


qemu-server: 7.0-13


smartmontools: 7.2-pve2


spiceterm: 3.2-2


vncterm: 1.7-1


zfsutils-linux: 2.0.5-pve1


pvesm nfscan results:

root@pve:~# pvesm nfsscan 10.0.1.2


/volume1/VMBackups 10.0.1.235



Here's an extract from my logs:


ug 28 15:17:12 pve pvestatd[1729]: mount error: mount.nfs: access denied by server while mounting 10.0.1.2:/volume1/VMBackups


Aug 28 15:17:16 pve upsmon[1812]: UPS [theups@localhost>]: connect failed: No such host


Aug 28 15:17:16 pve dhclient[1239]: DHCPDISCOVER on enp4s0f0 to 255.255.255.255 port 67 interval 4


Aug 28 15:17:20 pve dhclient[1239]: No DHCPOFFERS received.


Aug 28 15:17:20 pve dhclient[1239]: No working leases in persistent database - sleeping.


Aug 28 15:17:21 pve upsmon[1812]: UPS [theups@localhost>]: connect failed: No such host


Aug 28 15:17:22 pve pvestatd[1729]: mount error: mount.nfs: access denied by server while mounting 10.0.1.2:/volume1/VMBackups


Cat /etc/exports on Synology:

/volume1/VMBackups 10.0.1.235(rw,async,no_wdelay,no_root_squash,insecure_locks,sec=sys,anonuid=1025,anongid=100)


Not sure where I need to look next in order to resolve this, I've check on both the NAS and Proxmox but don't seem to find the root cause of the issue and everything seems to be setup correctly and knowing this was working a few days ago and no changes or updates have been applied either to the NAS or Proxmox. I may need to reboot the NAS just in case but it's currently doing a backup to the cloud so would need to wait until that completes.

Any ideas of what if the root cause of this?

Appreciate your input.

Thanks

L
 
Whats your storage.cfg entry for this storage look like?

You have some network errors on PVE related to DHCP. I presume you expect this PVE node to have the ip address 10.0.1.235
Verify your PVE ip address is correct?
 
Whats your storage.cfg entry for this storage look like?

You have some network errors on PVE related to DHCP. I presume you expect this PVE node to have the ip address 10.0.1.235
Verify your PVE ip address is correct?
Hi Republicus,

Thanks for taking the time to help, the PVE has a static ip which is 10.0.1.235, the dhcp error is based on an unused nic card installed in the server, I'll need to look into it and take the time to remove the unused card from the server, sorry I thought I had posted the what I had in storage.cfg but I didn't here you go:


dir: local


path /var/lib/vz


content vztmpl,backup,iso





lvmthin: local-lvm


thinpool data


vgname pve


content images,rootdir





lvm: NewDrive


vgname pve


content images,rootdir


shared 0





lvm: Storage


vgname Storage


content images,rootdir


nodes pve


shared 0





nfs: VMBackups


export /volume1/VMBackups


path /mnt/pve/VMBackups


server 10.0.1.2


content images,iso,backup


options vers=4.1


prune-backups keep-all=1


Thanks again for your help
 
Last edited:
Hi again,

Looks like you were correct with the DHCP issue, turns out that my UDM-Pro seems to have an issue with the DHCP reservations, I reboot of the UDM-Pro did the trick.

Thank you for pointing me in the right direction

Issue solved!:)
 

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!

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!