Trouble mounting SMB or NFS Remote backup target for XCPNG

MisterPipps · December 19, 2023, 11:25pm

Hello, I decided to give XCPNG a try last night after using Proxmox for years.

I set up everything using Tom’s XCPNG Youtube playlist for installation, setting up XO from Sources, and also his video on backups.

The problem I’m having is that when I go to create a remote in XO I get a weird vague “invalid parameters” error and then when I click enable on the remotes page I get a different error “remote is disabled”.

My NAS (Truenas Scale 10.10.10.20) is on the same subnet as the XCPNG Host (10.10.10.21) and XO (10.10.10.236). The only difference in my setup from the XO from sources video is I’m running Debian 12 and using the updated script from GitHub.

remote.test
{
“id”: {
“enabled”: true,
“error”: “""”,
“name”: “VM Backups”,
“url”: “smb://xcpng:PASSWORD@WORKGROUP\\10.10.10.20\VMBackup\u0000”
}
}
{
“code”: 10,
“data”: {
“errors”: [
{
“instancePath”: “/id”,
“schemaPath”: “#/properties/id/type”,
“keyword”: “type”,
“params”: {
“type”: “string”
},
“message”: “must be string”
}
]
},
“message”: “invalid parameters”,
“name”: “XoError”,
“stack”: “XoError: invalid parameters
at Module.invalidParameters (/opt/xo/xo-builds/xen-orchestra-202312190054/packages/xo-common/api-errors.js:26:11)
at Xo.call (file:///opt/xo/xo-builds/xen-orchestra-202312190054/packages/xo-server/src/xo-mixins/api.mjs:92:22)
at Api.#callApiMethod (file:///opt/xo/xo-builds/xen-orchestra-202312190054/packages/xo-server/src/xo-mixins/api.mjs:441:19)”
}

remote.test
{
“id”: “34829a29-86f1-4899-ae0e-643e07d68e02”
}
{
“message”: “remote is disabled”,
“name”: “Error”,
“stack”: “Error: remote is disabled
at _class2.getRemoteWithCredentials (file:///opt/xo/xo-builds/xen-orchestra-202312190054/packages/xo-server/src/xo-mixins/remotes.mjs:191:13)
at _class2.testRemote (file:///opt/xo/xo-builds/xen-orchestra-202312190054/packages/xo-server/src/xo-mixins/remotes.mjs:105:20)
at Api.#callApiMethod (file:///opt/xo/xo-builds/xen-orchestra-202312190054/packages/xo-server/src/xo-mixins/api.mjs:445:20)”
}

I’ve tried destroying and rebuilding the VM Backup dataset, removing spaces/underscores, changing punctuation, creating new user credentials, and adding permissions. I can’t seem to get it to play nice for me.

Am I missing something? Or am I just being an idiot and looking over something simple?

MisterPipps · December 19, 2023, 11:27pm

Since this is a fresh account, the forums won’t let me post more than one screenshot per post.

MisterPipps · December 19, 2023, 11:28pm

xMAXIMUSx · December 19, 2023, 11:32pm

When you created the dataset did you select the “share type” as SMB?

MisterPipps · December 19, 2023, 11:33pm

Also, I know my Truenas Scale SMB shares work because I can access them and I was even able to connect my ISO Library to XCPNG. So it’s functional there at least.

MisterPipps · December 19, 2023, 11:37pm

Yes, everytime I recreated the dataset I made sure to check that it was set up as SMB dataset. I’ve also tried setting up the remote using different SMB shares I had running, no dice.

xMAXIMUSx · December 19, 2023, 11:40pm

In your screenshot it looks like the syntax is wrong. You put 10.10.10.20\VMBackup in the address portion of the the config. You need to put VMBackup in the Subfolder section.

Also you don’t need to specify the WORKGROUP for the user.

MisterPipps · December 19, 2023, 11:47pm

I was following along with Tom’s video and from what I can see, it wants the share to be at the top. Tom goes on to specify the subfolder for niche use. Also the WORKGROUP thing is automatically entered in when I enter my info.

This is what the form looks like when entering info for SMB share.

and then this is the portion of Tom’s video where I followed along. (Link is set to timestamp)

I’d throw more screenshots, but this account is still too fresh and is preventing me from doing so.

MisterPipps · December 19, 2023, 11:55pm

This is also stated in the Xen Orchestra docs

That being said, I’ve tried all manner of changing the syntax too, but to no result.

MisterPipps · December 20, 2023, 12:11am

@LTS_Tom Any suggestions? Should I try redoing my XO VM from scratch?

Everything else seeeeeeems to be working correctly, but I haven’t tried messing around with too much else before getting backups up and running.

Paul · December 20, 2023, 8:29am

Why not setup NFS share for backups

LTS_Tom · December 20, 2023, 9:45am

NFS is better for backups, especially if you are going to use the store backup as multiple data blocks instead of a whole VHD file.

MisterPipps · December 20, 2023, 9:03pm

That’s what I hear, but in this example, I was just following your example in the video since you used SMB. When I’m trying something new I usually follow whatever guide step by step to understand how and why they made their choices and then tinker with it afterward.

That being said, I think I tried doing NFS a couple of times as well with no luck, but I didn’t try very hard. How do you get around XCPNG not asking for credentials when setting up the NFS share?

LTS_Tom · December 20, 2023, 9:16pm

XO does not have an option for credentials when setting up NFS.

MisterPipps · December 20, 2023, 9:47pm

Okay, so I created a new NFS (Generic) dataset with the name VM_Backups, setup the NFS share and I’m getting the same error.

“Invalid Parameters”

remote.test
{
“id”: {
“enabled”: true,
“error”: “""”,
“name”: “VM Backups”,
“url”: “nfs://10.10.10.20:/VM_Backups”
}
}
{
“code”: 10,
“data”: {
“errors”: [
{
“instancePath”: “/id”,
“schemaPath”: “#/properties/id/type”,
“keyword”: “type”,
“params”: {
“type”: “string”
},
“message”: “must be string”
}
]
},
“message”: “invalid parameters”,
“name”: “XoError”,
“stack”: “XoError: invalid parameters
at Module.invalidParameters (/opt/xo/xo-builds/xen-orchestra-202312190054/packages/xo-common/api-errors.js:26:11)
at Xo.call (file:///opt/xo/xo-builds/xen-orchestra-202312190054/packages/xo-server/src/xo-mixins/api.mjs:92:22)
at Api.#callApiMethod (file:///opt/xo/xo-builds/xen-orchestra-202312190054/packages/xo-server/src/xo-mixins/api.mjs:441:19)”
}

And then when I press to “Enable” I get “Remote is disabled”

remote.test
{
“id”: “6a318aba-2bbf-404c-9ac3-71a142c9bb13”
}
{
“message”: “remote is disabled”,
“name”: “Error”,
“stack”: “Error: remote is disabled
at _class2.getRemoteWithCredentials (file:///opt/xo/xo-builds/xen-orchestra-202312190054/packages/xo-server/src/xo-mixins/remotes.mjs:191:13)
at _class2.testRemote (file:///opt/xo/xo-builds/xen-orchestra-202312190054/packages/xo-server/src/xo-mixins/remotes.mjs:105:20)
at Api.#callApiMethod (file:///opt/xo/xo-builds/xen-orchestra-202312190054/packages/xo-server/src/xo-mixins/api.mjs:445:20)”
}

MisterPipps · December 20, 2023, 10:03pm

After you and Tom suggested NFS, I tried setting one up again, but no dice.

I stumbled on your post where you had a similar issue. For yours though, your problem was because you had a dedicated connection to Truenas that wasn’t mapped in XOA right?

I’m just trying to connect over LAN. My Truenas Scale and XCPNG are both connected over individual 10gbe SFP+'s to LAN.

There shouldn’t be anything special network-wise that I need to do right?

xMAXIMUSx · December 20, 2023, 11:21pm

What kind of permissions did you set on the dataset? For giggles, set it wide open and test it again.

MisterPipps · December 21, 2023, 12:06am

@xMAXIMUSx @Paul

So I went ahead and just recreated my XOA VM from scratch like I was suggesting in the beginning and we’re making progress now.

XCPNG accepted what my input for NFS, but now I have a new error which seems like it might be a permissions thing. Just wanted to update.

remote.test
{
“id”: “22444441-5078-42cd-b45f-0290f9de8ae6”
}
{
“shortMessage”: “Command failed with exit code 32: mount -o -t nfs 10.10.10.20:/VM_Backups /run/xo-server/mounts/22444441-5078-42cd-b45f-0290f9de8ae6”,
“command”: “mount -o -t nfs 10.10.10.20:/VM_Backups /run/xo-server/mounts/22444441-5078-42cd-b45f-0290f9de8ae6”,
“escapedCommand”: “mount -o "" -t nfs "10.10.10.20:/VM_Backups" "/run/xo-server/mounts/22444441-5078-42cd-b45f-0290f9de8ae6"”,
“exitCode”: 32,
“stdout”: “”,
“stderr”: “mount.nfs: access denied by server while mounting 10.10.10.20:/VM_Backups”,
“failed”: true,
“timedOut”: false,
“isCanceled”: false,
“killed”: false,
“message”: “Command failed with exit code 32: mount -o -t nfs 10.10.10.20:/VM_Backups /run/xo-server/mounts/22444441-5078-42cd-b45f-0290f9de8ae6
mount.nfs: access denied by server while mounting 10.10.10.20:/VM_Backups”,
“name”: “Error”,
“stack”: “Error: Command failed with exit code 32: mount -o -t nfs 10.10.10.20:/VM_Backups /run/xo-server/mounts/22444441-5078-42cd-b45f-0290f9de8ae6
mount.nfs: access denied by server while mounting 10.10.10.20:/VM_Backups
at makeError (/opt/xo/xo-builds/xen-orchestra-202312201600/node_modules/execa/lib/error.js:60:11)
at handlePromise (/opt/xo/xo-builds/xen-orchestra-202312201600/node_modules/execa/index.js:118:26)
at NfsHandler._sync (/opt/xo/xo-builds/xen-orchestra-202312201600/@xen-orchestra/fs/src/_mount.js:68:7)”
}

MisterPipps · December 21, 2023, 2:15am

Another update, for shits and grins I tried the SMB share again after redoing my XOA VM and what it works!

Still having some issues with NFS. As far as I can tell, it should be wide open so I’m not sure what to do there. I’ll probably keep playing with it and see what happens.

At the very least, if anyone gets a super vague error like I had when I started, we know there might be an issue with the VM installation. OR at least something that would be fixed alongside redoing the VM from scratch.

Paul · December 21, 2023, 8:34am

I would check the path of NFS share, it does not appear to be correct.

You need to enter the exact path from Truenas server - Sharing - Unix Shares (NFS)

Prefix the address with the server ip address

Permissions on the truenas data set

I would not point NFS and NFS remotes to the same location on the truenas. Create different shares for the type of remotes you want to use - as above I would NFS and not SMB