this is a dual post with the XOA forum as im not sure where the error comes form.
ive just set up a nfs server on a ‘true nas core’ and all guides should indecate ive set it up correctly. but XOA is claiming that ‘requested NFS version or transport protocol is not supported’
my understanding is that XOA uses nfs 3.0 but that is what true nas core is set up with.
its likly there some error in some configeration somwhere and i chould do with some help.
I am not well versed with NFS in order to help you, but neither can anyone else without details on how you set it up.
So posting that information would be a good start.
Ya, details matter, I am running xcp-ng/xoa as a host with my iso’s and vm’s stored on Trruenas in an NFS share. It was pretty effortless to do and I had 0 issues deploying the setup.
yep the guide i followed seemed easy most of what i read and checked seemed equally effortless and didnt have any problems i had. and i just chouldnt find any one with my problems.
sure, no problem, is there anything in particular you need, like a config file I can post? in the meantime, here’s a less concise overview of the details:
everything is physical and on premises, not in the cloud.
I followed this video guide as a base: ’ Configuring TrueNAS NFS Share for XCP-ng’ (no links in posts)
This guide was for truenas scale and i also followed the docuemntaion guide for ture nas core as a compliment.
there are some changes to the XOA config, i added the NFS as a remote instead of a single hosts storage, but after i tried the other way, as outlined in the video, i had the same problem.
the xoa host is dell PowerEdge R720xd with xcp-ng with xoa to manage it, I’m intending to upgrade to a pool but want to back up before I truly start messing with it. i set up the truenas core server in a separate machine, a PowerEdge T330 tower with a bunch of hdd’s. to act as a long term storage for the backups. It’s tower so I can just pick it up and move it.
Everything is using the latest versions of the software. the true nas core is a fresh install on bare metal, it fresh enough that a full wipe and re-install is still an option. After setting up a pool, a dataset, and a user I changed the permissions to write for the sharing dataset. I then set up a nfs share in the sharing tab, choose the correct dataset and path. It then enabled the nfs service and I checked the services tab and it is enabled.
Then set up the xoa remote, went to setting-remote, put the type to NFS, the path, ip address, port, which returned a no response error, corrected the ip address. The guides end here and it seems its works with no problems for most people. But I got the ‘requested-nfs-version-or-transport-protocol-is-not-supported’ error with “exitCode”: 32
Its likely I failed the set up or missed an step somewhere as what I wanted wasent exactly covered
In summary to my knowledge:
Dataset is right.
Sharing is right
Permission are correct even lowered security, included ‘all dirs’, no authorized network and all permissions to test if that’s the error – no change. Cannot ‘apply permissions recursively’ as option doesn’t save (?).
Nfs is enabled in the services tab. Even tried changing to nfsv4, didn’t fix it. (xoa uses nfsv3)
No one seems to be having this issue in the forums history.
Quick fixes ive already tried:
Rebooted both, doesn’t help.
Command line from both servers has responses from a ping meaning they can see each other, not likely network related but I’ve got an open mind here
Command ‘showmount -a’ shows the mount on the xoa server with the correct settings, no response form the TrueNasCore shell.
Funny enough I checked google again for researching this problem and now this post is the first response when you google ‘truenas nfs xoa’ at least for me
Basically I’m stumped here, if you need more info ill happy provide.
The unusual thing is that it mounts subdirectories. I assume that means recursive might be needed.
Can you document that error vs what expected from documentation.
What specific version of TrueNAS are you running?
Your host will mount the top-level NFS share you provide initially (example: /share/xen), then create folder(s) inside of that, then mount those directly instead (example: /share/xen/515982ab-476e-17b7-0e61-e68fef8d7d31). This means your NFS server or appliance must be set to allow sub-directory mounts, or adding the SR will fail. In FreeNAS or TrueNAS, this checkbox is called “All dirs” in the NFS share properties.
Perhaps share you NFS settings screen…
Have you tested NFS mounting from aanother client?
Document you NFS share setting with this screenshot:
ill get back to you with those details soon,
the XOA forum surgests i change to true nas scale, this would basicly restart everything, i want to see if i can fix this first. but if i cant ill do that.
I’d generally agree… any fixes will likely be done there. Not that I know of any issues.
