@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?

@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 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.

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.

@Danp i did not have this notifcation is that limited to the pro version?

@Danp intersting im used to a pop up that says a reboot is required, such as in ubuntu and others. is there a pop up telling me that a reboot is required somewhere that i missed or does every patch need a reboot?

alright ive got some updates, and it seems to have been simpler then i expected. you can mark this as fixed.

rebooting the pool master fixed the problem, as simple as that.

as a question to the support team do i need to reboot the master every time i add somthing to the pool or just in this case? maybe becuase it was a new pool master? edit: turns out i needed to reboot to apply updates leading to there being a version conflit with the master and slaves.

i was reluctant to reboot the master as it was hosting the tools and services i wanted to keep with high uptime. i also assumed it was not requied.
i went through lot of threads before making this one and i dislike that some of them end with out proper explainations below is the full story:

---

the true nature of the isuse is this:
i bought 3 servers total, 1 master(qky), 1 slave(serverB), and later i got another server to act as a nas(NAS).

i tryed to add the server B to the pool as a slave long time ago about 6 mouths, at that time it was having the same error as ive describe above in this ticket. because this is a side project for me and i wasent my priority at the time so the can got kicked down the road. i turned server B off to save power then did more urgent things. i did not reboot the master at anypoint when i added server b and left it runnning nearly 24/7 for those 6 months.

6 months later i decide i need a nas and bought a server with large storage to act as one. i also make sure that the hardware is compatable with the current master. as thats what i thought was the problem with server B.

once i added the nas server to the pool it would not leave maintance mode or detach from the pool just as described above. i did try to make the NAS slave leave the pool through the xoa interface and through the xe pool-eject in the command line, but this did not work with the error 'nonetype object has no attribute xenapi' and in general the xapi was not working. i turned the servers off when i was not working on them as i wanted to save power if they wernt funtcional but never the master as it was hosting. i rebooted the master while the NAS slave was off. i turned on server b which did not show up on the pool. after i turned on the NAS server and found it was now connected and no longer in maintenance mode.

i decided after connecting it to the pool that i perfer having the NAS not be on the pool as i want to be focused on the job of being the NAS and backup storage, ill try to get it to leave the pool now and act indepeneantly again. however i thought i get it working as a pool first as was the same problem as with server b and so id have the option to pool it if i wanted, so i started this thread.

im now going to work on fixing server b and connect it to the pool. but that seems to have a completely diffrent set of problem (it dosent even show up in the host-list), for that ill try to fix it my self before making another thread. hopfully its simple as ive now confirmed that the pool can be made.

@Danp sure ill do that right now, i tryed this before on the slave and it gave me the error: 'nontype object has to atterbute xenapi'.
but i havent done it form the masters end.

if it does eject ill still need to add it to the pool correctly and get it working as thats the end goal, but ill try this now.

@Danp here the host list:
the host is the one named qkyliepo the added server is called NAS

i can eject the master from the pool but its running services right now. is that going to cause disruption?

@Danp there a lot of log as every few seconds it trys to restart xapi, among them are claims its unable to find host uuid and it cant reach the host, this is likly because i tryed to make it leave the pool after it didnt work. however i cant make it leave the pool as it tell me xapi isnt working

if you want i can send you the logs but youll have to tell me which ones as there is a lot of repeat errors every few seconds