[SOLVED] Proxmox 8 can't attache NFSv4 share (Synology) to both nodes, only one can connect.

Sorry that was a typo
Ok, great, those happen. As you can see from the output the "pvesm" command wraps around common Linux NFS utilities, ie "showmount" and "rpcinfo".

You need to figure out why that general Linux command is timing out. Things you can look at and optionally provide to the community:
a) "ip a" from each node
b) icmp ping from each node to your nfs server
c) direct "showmount" and "rpcinfo" from each node
d) you may want to use "nc host port" to test connectivity
e) if all else fails, tcpdump during "pvesm status" or "nfs scan".

Everything so far points to a networking issue, rather than hypervisor problem.

PS "dmesg" is not helpful when troubleshooting Userland issues, you may want to "journalctl -n 100" or "journalctl -f" in a second terminal session.

PPS keep in mind that NFS UDP has been disabled in Linux Kernel at some point, you may want to make sure that you are using TCP

PPPS output of "cat /etc/pve/storage.cfg" is also helpful , even though basic NFS tools are not working.


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
Last edited:
Found the issue in the network. Not a proxmox issue in end.

Thanks for all the comments
 
Last edited:
  • Like
Reactions: bbgeek17

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!