Adding a Synology NFS share to Proxmox is straightforward once three things agree: the NAS export path, the Proxmox node's IP permission, and the storage content types. Proxmox can mount the export itself, so you do not need a separate /etc/fstab entry.
Before you begin
Use a stable IP address for both the NAS and Proxmox node. On the Synology side:
- Enable NFS under Control Panel → File Services → NFS.
- Create or select the shared folder.
- Open Edit → NFS Permissions and allow the Proxmox node or a tightly scoped LAN subnet.
- Note the exact mount path shown by Synology, such as /volume1/proxmox.
Avoid granting access to an entire network if only one node needs it. NFS trusts network and host configuration, so keep it on a trusted LAN or isolated storage VLAN.
Add the share in the Proxmox web interface
Go to Datacenter → Storage → Add → NFS, then complete these fields:
- ID: A short unique name, such as synology-backups.
- Server: The Synology IP address. Proxmox recommends an IP unless your DNS is highly reliable.
- Export: Select the exact Synology export.
- Content: Enable only what belongs there: backups, ISO images, container templates, snippets, VM disk images, or container root directories.
- Nodes: Restrict the storage if not every cluster node can reach the NAS.
Click Add. The storage should appear under the node without editing /etc/fstab.
CLI equivalent
First discover exports:
pvesm nfsscan SYNOLOGY_IP
Then add one. This example is intended for backups and ISO images:
pvesm add nfs synology-backups \
--server SYNOLOGY_IP \
--export /volume1/proxmox \
--content backup,iso
Check the resulting configuration:
pvesm status
grep -A8 '^nfs: synology-backups' /etc/pve/storage.cfg
findmnt /mnt/pve/synology-backups
Test before trusting it with backups
Create a small test backup or upload an ISO through Proxmox. Then verify from the Synology that the file exists in the expected directory.
For backup storage, run one manual vzdump and restore it to a disposable VM or container. A green backup job proves that a file was written; a test restore proves that the backup is useful.
Troubleshooting
The export list is empty
Check NFS permissions on Synology, confirm the node IP is allowed, and verify that the NAS firewall permits NFS traffic. From Proxmox:
rpcinfo -p SYNOLOGY_IP
showmount -e SYNOLOGY_IP
Permission denied
The usual cause is a Synology squash or mapping rule that does not match Proxmox's expected ownership. Review the export's Squash setting and permissions rather than applying broad write permissions to the entire share.
Storage hangs when the NAS is unavailable
NFS retries can make a node appear stuck during an outage. Proxmox supports custom mount options, but soft mounts can produce I/O errors and should be considered only with a clear understanding of the data-integrity tradeoff. For VM disks, reliable networking and a highly available NAS matter more than a quick timeout.
The official Proxmox storage guide documents the NFS backend and pvesm options. Next, see how to resize a Debian VM disk and add swap.