Unable to mount NFS Remote for backups while storage and ISO NFS SR's work perfectly

Bub

Hello Friends,

I am testing a fresh install of xcpng 8.3 with community XO

while I am able to mount both ISO NFS SR and VDI NFS SR from both Synology and Qnap NAS boxes, on the same subnet, I am unable to mount any NFS remotes for backups from the same two NAS boxes.
The error log is:
remote.test
{
"id": "d43307ac-afc3-42cb-89af-3892f1fe592c"
}
{
"shortMessage": "Command failed with exit code 32: mount -o -t nfs 192.168.221.20:/LAB-NFS /run/xo-server/mounts/d43307ac-afc3-42cb-89af-3892f1fe592c",
"command": "mount -o -t nfs 192.168.221.20:/LAB-NFS /run/xo-server/mounts/d43307ac-afc3-42cb-89af-3892f1fe592c",
"escapedCommand": "mount -o "" -t nfs "192.168.221.20:/LAB-NFS" "/run/xo-server/mounts/d43307ac-afc3-42cb-89af-3892f1fe592c"",
"exitCode": 32,
"stdout": "",
"stderr": "mount.nfs: failed to prepare mount: Operation not permitted
",
"failed": true,
"timedOut": false,
"isCanceled": false,
"killed": false,
"message": "Command failed with exit code 32: mount -o -t nfs 192.168.221.20:/LAB-NFS /run/xo-server/mounts/d43307ac-afc3-42cb-89af-3892f1fe592c
mount.nfs: failed to prepare mount: Operation not permitted
",
"name": "Error",
"stack": "Error: Command failed with exit code 32: mount -o -t nfs 192.168.221.20:/LAB-NFS /run/xo-server/mounts/d43307ac-afc3-42cb-89af-3892f1fe592c
mount.nfs: failed to prepare mount: Operation not permitted

at makeError (/etc/xen-orchestra/node_modules/execa/lib/error.js:60:11)
at handlePromise (/etc/xen-orchestra/node_modules/execa/index.js:118:26)
at NfsHandler._sync (/etc/xen-orchestra/@xen-orchestra/fs/src/_mount.js:68:7)"

}

Thinking of permissions issue, I went ahead and tried to mount the same qnap nfs folder with the same permissions settings I am using for the XO remote onto an UnRaid server, which worked on the first try, leading me to believe I'm missing something on xcp or XO end.

Any ideas to point me to the correct direction would be appreciated.
FYI I used web gui for everything.

Pilow

@Bub indeed, permissions issues.

What IP do you authorize for your NFS export ?

remember, SR and ISOsr are accessed by the XCP host IP...

but, NFS Remote is accessed by XO/XOA IP address !

Danp

Hi,

Make sure that the XOA VM has been granted the rights to mount the NFS share and create subdirectories.

Dan

Bub

This post is deleted!

Bub

@Pilow said in Unable to mount NFS Remote for backups while storage and ISO NFS SR's work perfectly:

It was. Both the host ip and the xoa.
Thanks for the super fast replies guys!
I got an idea, I'm going to try and investigate, the XOA is running in a container. I'm going to test if the passthrough of the container manager network may be blocking the NFS.

Bub

-= Update =-
Tried to expose the Unraid server container to the host network, everything seemed perfect and pings work both ways, while nfs still giving me the same error only for mounting remotes (both from QNAP and the same host Unraid server.

I decided to install another fresh XCP-ng host server just to eliminate my first host configuration, but I got the same result, remotes would not mount.

The last idea was to remove the XOA container VM running on the Unraid server and download the prebuilt XOA VM image directly from the XCP-ng host. This gave me a timeout error when trying to mount off QNAP with permissions set to both the new XOA IP and the XCP-ng host IP.
remote.test
{
"id": "7903a500-ee84-43dc-bd3e-b6c7abe8381b"
}
{
"shortMessage": "Command failed with exit code 32: mount -o hard -t nfs 192.168.45.20:/LAB-NFS /run/xo-server/mounts/7903a500-ee84-43dc-bd3e-b6c7abe8381b",
"command": "mount -o hard -t nfs 192.168.45.20:/LAB-NFS /run/xo-server/mounts/7903a500-ee84-43dc-bd3e-b6c7abe8381b",
"escapedCommand": "mount -o hard -t nfs "192.168.45.20:/LAB-NFS" "/run/xo-server/mounts/7903a500-ee84-43dc-bd3e-b6c7abe8381b"",
"exitCode": 32,
"stdout": "",
"stderr": "mount.nfs: Connection timed out",
"failed": true,
"timedOut": false,
"isCanceled": false,
"killed": false,
"message": "Command failed with exit code 32: mount -o hard -t nfs 192.168.45.20:/LAB-NFS /run/xo-server/mounts/7903a500-ee84-43dc-bd3e-b6c7abe8381b
mount.nfs: Connection timed out",
"name": "Error",
"stack": "Error: Command failed with exit code 32: mount -o hard -t nfs 192.168.45.20:/LAB-NFS /run/xo-server/mounts/7903a500-ee84-43dc-bd3e-b6c7abe8381b
mount.nfs: Connection timed out
at makeError (/opt/xo/xo-builds/xen-orchestra-202511150402/node_modules/execa/lib/error.js:60:11)
at handlePromise (/opt/xo/xo-builds/xen-orchestra-202511150402/node_modules/execa/index.js:118:26)
at NfsHandler._sync (/opt/xo/xo-builds/xen-orchestra-202511150402/@xen-orchestra/fs/src/_mount.js:68:7)"
}

BUT
If I configured a completely unsecured public NFS share on the Unraid server, I then managed to get it mounted successfully. (using the XOA vm running on the XCP-ng host.

When I changed the share to Private with granting permissions to the IP of the host and the XOA VM IPs, I get permissions denied yet again.

At this point, I'm at a loss, there must be a way to grant access to an IP and make it work with remote. Clearly, I know how to grant permissions as the NFS SR and the Unraid mount of the secured NFS from QNAP are working with no issues.

Must be something stupid I'm missing.

Pilow

@Bub try to manually mount the NFS share in cli on the xoa
and activate debug (-vvv if I remember)

sometimes there is more obvious reasons , and the step where it is failing that can be seen this way

try the exact cli mount that you see failing in the error log