XOA 'requested NFS version or transport protocol is not supported' with true nas core remote, when it should be able to support it.
-
this is a dual post with the true nas core forum as im not sure were the error lies,
ive just set up a nfs server on a 'true nas core' and all guides should indecate that 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.
-
@thomas-wood some more details i posted in the true nas forum,
here’s a overview of the details, if theres a config flie that i might be able to read that would be helpfull: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'
This guide was for truenas scale and i also followed the documentation guide ofr setting up an nfs for ture nas core as a compliment.there are some changes in 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.
-
you might have a look at this topic:
nfs sr connection problemThere we also discussed a NFS problem between XOA and TN Core. Maybe there is something in as a hint in the right direction for you.
-
Why are you doing this with TrueNAS Core? It has reached end of life.
-
@lawrencesystems honestly just because poeple reconmended it and its the first result in most search results, i didnt think true nas scale was needed as i dont need that amount of storage for my smaller setup.
i hadnt heard anything about it being at end of life before so i didnt think its an issue, it seem it being supported intill 2026, but changing, likly to true nas scale, is still an option at this state. would you Recommend changing?
even still it should be possible to at least set up a nfs with out the problems im having.also Strangely ehough the video i Mentioned in the details post is yours. did you set up somthing to check or is it just Coincidence.
good videos btw. -
@thomas-wood Yes, go with TrueNAS Scale. Also, TrueNAS Scale will be called TrueNAS Community with the next version 25 release.
-
@lawrencesystems that somthing i will do then.
however im going to try and fix this problems before nuking it. and since i started this thread ill like to make a ending thats more then just uninstall truenas core. as thats better for anyone else that reads this in the future. (i hate finding dead end threads for my problem).is it better to add the nfs as a sr instead of a remote? wont it not then be avalable to the rest of the pool? will i need to read it every time i add a host if its an sr?
basicly what the difference? -
@thomas-wood "Remotes" are for XO backups and SR are for VM Storage. Once you add a SR to a pool it's available to all hosts. Also, all hosts should be able to access the IP of the NFS server before setting that up.
I have a video explaining storage in XCP-ng here:
https://youtu.be/xTo1F3LUhbE?si=QHYkABgElsEVOj6H
