Settings -> Remote -> (NFS|SMB) on a Sinology NAS

aqua-calc

@gskger Yes, we did. As a matter of fact,the same NFS is mounted as "NFS virtual disk storage" via XCP-NG control center, with no problems.

We're trying to move away from our own backup script to use XO scheduled backups.

gskger

@aqua-calc What error message do you get when trying to connect the remote to the Synology NFS share? Like others, I am also using a Synology (RS818plus) as a NFS storage and backup target without any issues.

aqua-calc

@gskger

{
  "shortMessage": "Command failed with exit code 32: mount -o  -t nfs 192.168.1.200:/volume1/backup/xenserver16 /run/xo-server/mounts/2fae45cb-d7ad-4fb0-bcc6-896cca5e6684",
  "command": "mount -o  -t nfs 192.168.1.200:/volume1/backup/xenserver16 /run/xo-server/mounts/2fae45cb-d7ad-4fb0-bcc6-896cca5e6684",
  "escapedCommand": "mount -o \"\" -t nfs \"192.168.1.200:/volume1/backup/xenserver16\" \"/run/xo-server/mounts/2fae45cb-d7ad-4fb0-bcc6-896cca5e6684\"",
  "exitCode": 32,
  "stdout": "",
  "stderr": "mount: /run/xo-server/mounts/2fae45cb-d7ad-4fb0-bcc6-896cca5e6684: bad option; for several filesystems (e.g. nfs, cifs) you might need a /sbin/mount.<type> helper program.",
  "failed": true,
  "timedOut": false,
  "isCanceled": false,
  "killed": false
}

gskger

@aqua-calc said in Settings -> Remote -> (NFS|SMB) on a Sinology NAS:

same NFS is mounted

It is probably dumb to ask: you are not trying to connect the same NFS share on the Synology as storage and backup target?

Edit: did not see your post

AtaxyaNetwork

Hi @aqua-calc !

Are you on XOA or XO from sources ?

aqua-calc

@AtaxyaNetwork XO from sources

aqua-calc

@gskger I've tried both -- the same result:

{
  "shortMessage": "Command failed with exit code 32: mount -o  -t nfs 192.168.1.200:/volume1/backup-xo/backup /run/xo-server/mounts/813d5bc2-aaaf-4c9f-8841-64eebad52279",
  "command": "mount -o  -t nfs 192.168.1.200:/volume1/backup-xo/backup /run/xo-server/mounts/813d5bc2-aaaf-4c9f-8841-64eebad52279",
  "escapedCommand": "mount -o \"\" -t nfs \"192.168.1.200:/volume1/backup-xo/backup\" \"/run/xo-server/mounts/813d5bc2-aaaf-4c9f-8841-64eebad52279\"",
  "exitCode": 32,
  "stdout": "",
  "stderr": "mount: /run/xo-server/mounts/813d5bc2-aaaf-4c9f-8841-64eebad52279: bad option; for several filesystems (e.g. nfs, cifs) you might need a /sbin/mount.<type> helper program.",
  "failed": true,
  "timedOut": false,
  "isCanceled": false,
  "killed": false
}

aqua-calc

@aqua-calc The problem is fixed. The XO server was missing NFS utils:

sudo apt install nfs-common

Thank you everyone for responding!

nikade

@aqua-calc said in Settings -> Remote -> (NFS|SMB) on a Sinology NAS:

@aqua-calc The problem is fixed. The XO server was missing NFS utils:
sudo apt install nfs-common
Thank you everyone for responding!

Thanks for sharing the solution!

olivierlambert

@aqua-calc said in Settings -> Remote -> (NFS|SMB) on a Sinology NAS:

nfs-common

I think it's installed in XOA we distribute. If it doesn't, there's a bug somewhere in our way to build it. Can you double check you have this package on a fresh deployed XOA?

Danp

@olivierlambert He's running XO from sources.

olivierlambert

He said:

@aqua-calc said in Settings -> Remote -> (NFS|SMB) on a Sinology NAS:

I've tried both

gskger

@olivierlambert I think that was probably related to my question if he tried to

connect the same NFS share on the Synology as storage and backup target