[PROXMOX CLUSTER] Add NFS resource to Proxmox from a NAS for backup

avaaru

Active Member
Aug 15, 2018
26
3
43
28
I've encountered a synchronization and availability issue when using NFS network storage within a Proxmox VE cluster.

- Environment: Proxmox VE Cluster with 2 nodes (node 01, node 02).
- Storage: Synology NAS shared via NFS.
- Configuration: The connection to the NAS is made through a public IP address.

- Symptom 1: When adding the resource to /etc/pve/storage.cfg, I get the following error:
`create storage failed: storage 'NAS_Sysnalogy_LEGANES' is not online`
The command I'm using to add it is:
pvesm add nfs NAS_Sysnalogy --server IP_NAS --export /volume2/RUTE_NAS --content backup,images,rootdir,iso --options vers=3,soft,timeo=300,proto=tcp


- Symptom 2: The problem isn't related to NAS connectivity or NFS permissions, as a manual mount test (`mount -t nfs IP:/volume2/ROUTE_NAS /mnt/ NAS_Sysnalogy`) works correctly.
If I add it manually, it's added as a DIR within /etc/pve/storage.cfg, and it causes the backups made by Node 1 to be invisible on Node 2, and vice versa, even though it's the same shared resource.


Why can't I add it from Proxmox but I can with the mount command?
I understand that NFS is working correctly and it's not a port or NAS problem since I can add it using mount.
 
Hi,

Do you mount the the correct export path? How about if you get rig the version or options flags?

Could you please also run the `showmount -e IP_NAS` to confirm the exact export?
 
Hello.

Thanks for your reply

If the path is the same as the one I configured in the mount command and I select the NFS 3 protocol, which is the one I have configured on my Synology
1764167211898.png
1764167233295.png

If I run the command showmount -e IP_NAS, it just stays like that, as if it's thinking, and doesn't end up returning anything.

1764167327255.png

However, if I run this mount inside my fstab:

1764167482115.png

It mounts the folder correctly.

1764167649411.png

Do you need any more information?
Hi,

Do you mount the the correct export path? How about if you get rig the version or options flags?

Could you please also run the `showmount -e IP_NAS` to confirm the exact export?
 

Attachments

  • 1764167667776.png
    1764167667776.png
    13.4 KB · Views: 3
Thank you for the output!

If I run the command showmount -e IP_NAS, it just stays like that, as if it's thinking, and doesn't end up returning anything.
Could you please also run the following commands on your PVE node?
Bash:
pvesm nfsscan IP_NAS
rpcinfo -p IP_NAS

And see the output if have any timeout message?
 
After waiting a few minutes, it shows me the following errors:

1764170118009.png

1764170371655.png
 

Attachments

  • 1764170107904.png
    1764170107904.png
    10.6 KB · Views: 0
Thank you for the output!

This show that the NAS isn't answering, please check your NAS or firewall, you can try nmap port 111, 2049 to see if they are allowed from your Proxmox VE node.
 
They are open according to the nmap results. Furthermore, if they weren't open, they wouldn't mount with mount from Proxmox, right?

1764171875986.png

I don't understand why mount doesn't reject the connection but proxmox's NFS does.
 
My command does not specify the version: IP:/volume2/Backup-Proxmox /mnt/NAS_Sysnalogy nfs defaults 0 0

I modified the command for version 3 and it still works. I've attached a screenshot of the mount and ls commands showing that the content is visible.

IP:/volume2/Backup-Proxmox /mnt/NAS_Sysnalogy nfs nfsvers=3 0 0

1764172922631.png