We had the same issue with Proxmox VE 6.2-4 on Debian 10 and were able to implement a workaround for this problem.
After some research, we were able to conclude that the problem is an issue with the "showmount" command.
When executing the command "showmount <IP of NAS>" we always recieved an error "No route to Host", but we were able to mount the NFS-share using "mount -t nfs <ip>:<path> <mountpoint>" just fine.
Furthermore, the issue only exists on Proxmox 6 (Debian 10), not Proxmox 5 (Debian 9). (Btw: The problem is also reproducable on clean Debian 10 installations without Proxmox being invloved. It works just fine on Debian 9 though).
Nevertheless, we fixed the problem by replacing the
/sbin/showmount file with a custom bash-script that simply echos the output we expect.
First, we installed a fresh version of Proxmox 5, where we knew that
showmountgives a valid output. We ran
showmount <ip> on this installation and wrote the output down.
Next, we went back to our Proxmox 6 installation and renamed
showmount in
/sbin/ to
showmount_orig and created a new file called
showmount (simply using
nano showmount).
This file should be a simple bash script which echos the output we expect.
I.e. the file could look like this:
Bash:
#!/bin/bash
echo "Export list for 192.168.90.10"
echo "/volume5/Proxmox6_Cluster_Test 192.168.40.0/24"
After you save the script, just run
chmod 777 showmount to make it executable.
After we implemented this very hacky fix, all expected export locations were displayed correctly in the Proxmox-Web-UI and we successfully added a working NFS-Synology-Share to our Cluster.
If this solution is too ugly for you, you can simply expand the bash script a bit by adding logic like "if the first parameter is our NFS-IP, echo the valid result; otherwise trigger the real showmount".
I hope this helps anyone
