[SOLVED] nfs mount error

B

BP2010

Member
Proxmox Subscriber
Jan 31, 2019
36
2
13
54
Hi,

I have setup a folder on my Synology NAS to backup my ProxMox server. Everything worked perfect until I had to change the location of my NAS.
I got a new IP Address and an error:

mount error: mount.nfs: access denied by server while mounting 192.168.1.142:/volume1/Ordination (500)

I changed the IP address at /etc/pve/storage.cfg


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

lvmthin: local-lvm
thinpool data
vgname pve
content images,rootdir

nfs: Backup
export /volume1/Ordination
path /mnt/pve/Backup
server 192.168.1.142
content backup
maxfiles 5

zfspool: ZFS-MCW-Pool
pool myPool/MCW
content rootdir,images
sparse 0




pveversion -v
proxmox-ve: 6.0-2 (running kernel: 5.0.21-1-pve)
pve-manager: 6.0-6 (running version: 6.0-6/c71f879f)
pve-kernel-5.0: 6.0-7
pve-kernel-helper: 6.0-7
pve-kernel-4.15: 5.4-8
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.18-9-pve: 4.15.18-30
ceph-fuse: 12.2.12-pve1
corosync: 3.0.2-pve2
criu: 3.11-3
glusterfs-client: 5.5-3
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.11-pve1
libpve-access-control: 6.0-2
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-4
libpve-guest-common-perl: 3.0-1
libpve-http-server-perl: 3.0-2
libpve-storage-perl: 6.0-7
libqb0: 1.0.5-1
lvm2: 2.03.02-pve3
lxc-pve: 3.1.0-64
lxcfs: 3.0.3-pve60
novnc-pve: 1.0.0-60
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.0-7
pve-cluster: 6.0-7
pve-container: 3.0-5
pve-docs: 6.0-4
pve-edk2-firmware: 2.20190614-1
pve-firewall: 4.0-7
pve-firmware: 3.0-2
pve-ha-manager: 3.0-2
pve-i18n: 2.0-2
pve-qemu-kvm: 4.0.0-5
pve-xtermjs: 3.13.2-1
qemu-server: 6.0-7
smartmontools: 7.0-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.1-pve2



But the error still appears.

Obviously, I am doing something wrong. Is there another place where I have to change the ip address? Any help would be appreciated.

Thanks,
Bernd
 
Where else you might need to specify an IP is at the NAS, as it may be restricting access to clients.

You have shell access to the NAS? Looks like Synology is running Linux. If so, show whats in /etc/exports on the NAS.

Run # pvesm nfsscan 192.168.1.142
 
  • Like
Reactions: ColonelBundy
Hi, thank you for your help! I am sorry for my late reply (I have no remote access).

root@proxmoxserver:~# pvesm nfsscan 192.168.1.142
/volume1/Ordination 192.168.1.18

/etc/exports:
/volume1/Ordination 192.168.1.18(rw,async,no_wdelay,no_root_squash,insecure_locks,sec=sys,anonuid=1025,anongid=100)


I changed the entry in /etc/exports to:
/volume1/Ordination 192.168.1.142(rw,async,no_wdelay,no_root_squash,insecure_locks,sec=sys,anonuid=1025,anongid=100)


pvesm nfsscan 192.168.1.142 shows now
/volume1/Ordination 192.168.1.142

But still no success:
mount error: mount.nfs: access denied by server while mounting 192.168.1.142:/volume1/Ordination (500)

Bernd
 
The IP to your PVE node is 192.168.1.18 ?
I am assuming your last modification restricted the export to your NFS server only (may as well have been localhost) if it is 192.168.1.142
Try opening the export to your entire network to troubleshoot:

/volume1/Ordination 192.168.1.0/24(rw,async,no_wdelay,no_root_squash,insecure_locks,sec=sys,anonuid=1025,anongid=100)

This is my working export:
/raid50vol/pve/iso 10.10.0.0/24(rw,async,insecure,all_squash,anonuid=101001,anongid=101001,no_subtree_check)
 
The IP of the PVE node is 192.168.1.140
The IP of the NFS is 192.168.1.142

The former IP of the NFS was 192.168.1.18

I made the changes but the error is still the same:
mount error: mount.nfs: access denied by server while mounting 192.168.1.142:/volume1/Ordination (500)

This are the synology settings:

1570372030107.png
 
BP2010 said:
sorry guys, I found the problem. It was a really stupid mistake. The IP address was blocked by the nfs server
Thank you for your help!!
Click to expand...
Hi,
I'm having the same issue. Would you mind sharing, how you solved it? I already added the Proxmox IP in the Synology firewall rules. This doesn't help?!

Solved: I had a space within the folder name on the Synology. That caused the problem.
 
Last edited:
  • Like
Reactions: JBredal
The solution is go to the Synology, edit folder NFS you share, go to tab NFS permision and add all IP Proxmox Host Server.
 
cyberoot said:
The solution is go to the Synology, edit folder NFS you share, go to tab NFS permision and add all IP Proxmox Host Server.
Click to expand...
bless you!!! wasted a good deal of time trying to figure out why I was getting the error smh lol
 
I am still having the issue...Proxmox will not mount it but Synology is setup with the IP of the PVE, privilege is r/w, squash is no mapping, and security is sys. I also have enable async and allow users to access mounted subfolders enabled.
 
Proxmox is doing a regular NFS mount as a Linux client. SSH into your Proxmox and try to mount your nfs server directly:
mkdir /tmp/test
mount nfs_ip:/path /tmp/test

If that doesn't work, then PVE wont be able to mount either. You can run a few commands to help you :
showmount -a [nfs_ip]
rpcinfo [nfs_ip]
/usr/sbin/rpcinfo -T tcp [nfs ip] nfs 3
/usr/sbin/rpcinfo -T tcp [nfs ip] nfs 4

If none (or some) of this not working, come back and provide actual data. Or, you can ask on synology forum for assistance with NFS mounting. They may be more aware of logs/messages that can assist.

good luck

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
Not wanting to high jack this thread. also battling to get NFS configured at the datacenter level.

I get the attached error.
I'm using TrueNAS, I've configured it to allow all hosts on my 2 primary vlans.
if I ssh onto pmox1 and try and cd /mnt/pve/nfs then fails.times out
if i try and do mkdir then it says already exist.
i'm doing this as root.
<newest 8,x version of Proxmox>

fYI I tried the above, simple linux mount, the mount worked...
I then went onto my TrueNAS and did a touch x inside the directory, came back to Proxmox and did a ls, it hung. closed session, restarted nfs, logged back into pmox node, cd /tmp/test and did a ls, saw my file. went back into Proxmox UI, tried to configure, hung, came back to terminal, did ls, hanging...

G

Screenshot 2024-11-06 at 10.13.17.png
 
Last edited:
Eventually got it to mount, it even created the various sub directories based on the file types i picked to use the nfs for...
when uploading a iso, it's err:

this is past hair pull out... ;(

Error 500: unable to activate storage &#39;nfs&#39; - directory &#39;/mnt/pve/nfs&#39; does not exist or is unreachable

G
 
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back