@kagbasi-ngc I figured out what the problem was, so wanted to post it for the benefit of the community.

The root cause for me ended up being a firewall issue on the Windows Server where I was running the NFS server role. While I hadn't made any changes to the firewall, the profile of the network interface connected to the management network had changed from Domain to Public/Private, thus, Windows Defender Firewall applied the most restrictive settings since it saw that the NIC wasn't connected to the Domain profile (even though it physically was).

This post on Serverfault (https://serverfault.com/a/647201/189248) clued me in and I looked at the Network Location Awareness service (NLA). It was set automatic and was running, so I restarted it and this reverted the profile of the NIC back to Domain and caused Windows Defender Firewall to apply the previously configured rules.

It is important to note that this situation won't be common, as most of you won't be running your NAS on a dual-homed domain controller that is also running the DHCP server role. Hope this helps someone.

@Prilly Looks like @lawrencesystems has a good explainer video on YouTube at https://youtu.be/weVoKm8kDb4?si=QH93rOKaXLglrIbS

Check it out when you get a chance, thanks.

@tjkreidl said in Force Remove a NFS Storage Repository:

@kagbasi-ngc See if this thread can help you out:
https://xcp-ng.org/forum/topic/6618/how-to-remove-this-sr-nfs-storage/

A BIG THANK YOU! This was quite helpful, and helped me resolve my issued.

Here's what I ended up doing (after reading the post you shared):

• STEP 1: On each host, I ran the mount command (without any parameters).

• STEP 2: I identified the mount point of the SR in question - for me it was /run/sr-mount/<SR-UUID>

• STEP 3: On each host, I unmounted the NFS share with umount -lf /run/sr-mount/<SR-UUID>

• STEP 4: From the pool master, I identified the UUID of the PBDs with xe pbd-list sr-uuid=<SR-UUID>

• STEP 5: While still on the pool master, I unplugged each PBD with xe pbd-unplug uuid=<PBD-UUID> force=true (I had three to unplug, adjust accordingly)

• STEP 6: I confirmed in Xen Orchestra that the status of each host connection had changed to Disconnected

• STEP 7: From the pool master, I forgot the SR with xe sr-forget uuid=<SR-UUID>

Hope this helps someone out there. Thanks again @tjkreidl

@lsouai-vates Duly noted.

If amd when you do get a moment, could you have a look at https://xcp-ng.org/forum/post/94297 and offer up any guidance on how I can stop the debug log entries and also the double timestamp entries in the audit.log file?

Thank you.

@ThasianXi Thanks, I will checkout the resources you've shared. I already figured out the XCP-ng side and wanted to get the XO side as well.

Thanks again.

@nathanael-h Yeah, I've already done that several times and no luck.

What I'm gonna try now is see if I can boot it with the Windows installation disk, go into recovery and access the WinPE command line, and see if I can run xenbootfix.exe to clean out the guest tools/drivers.

If that doesn't work, I'll just blow away the VM and start over. I just hate doing this, cos it doesn't give us the chance to figure out why this happened.

@olivierlambert Cool, I'll run the other two when I get back. I'll kick them off simultaneously.

@olivierlambert No sir, I have not. I'll try that and report back shortly.

Thanks to both of you, I adjust accordingly.

The strange thing is that, I have an open ticket and the way I've always corresponded with the team is by simply replying to that email and it's always gotten through. This is the first time I've seen that bounce (which suggests a change somewhere).

No worries though, I'll just log into the helpdesk portal and add a comment directly to the ticket.

@Chico008 Seems like you're duplicating your inquiries. As I suggested in the previous thread, I think your memberOf is missing the full DN of the group.

ENVIRONMENT:

HOSTS: XCP-ng v8.3 on HP ProLiant DL360p Gen8
XOCE: commit d7fe4

Does Xen Orchestra support AlmaLinux 10 in UEFI mode?

I ask because I am able to boot the AlmaLinux 9.6 DVD/ISO without any issues, however, the v10 DVD/ISO fails to get past this point:

I also noticed that there is no AlmaLinux 10 listed in the template drop-down list when creating a new VM. I have confirmed the integrity of the downloaded ISO (hashes match): SHA256: 6c443f462b3993d15192a7c43ba8dfa3f232514db47d38796dab007a7455ae1a

SHA256 Hash from XCP-ng point of view:

SHA256 Hash from the storage system's point of view (TrueNAS):

@olivierlambert Agreed. Thanks, still, for pinging them again.

Today being Friday, I'll be in the lab for a bit, troubleshooting other issues unrelated to Xen Orchestra. Would be nice to work on this as well.

No worries, though, I'll sit tight and exercise patience.

@olivierlambert Any word from the team on this?

Good-day Folks,

An idea came to mind recently, to display the Xen Orchestra dashboard on a large screen in a NOC. So I wanted to see if it were possible to pass a user's authentication token to any of the URLs in Xen Orchestra to accomplish this.

For example, if the Dashboard can be reached at https://xoa.local/#/dashboard/overview, how can I pass the authentication token?

I've already tried https://xoa.local/#/dashboard/overview&authenticationToken=xxxxxx and it didn't work.

Is this even supported, currently?

@Forza Good point. I need to apply the latest patches anyway, so I'll be rebooting the pool later today anyway.

@Forza thanks for the caution. I wondered about that as well, so I initially tried with just -f and it didn't work. So this is what ended up working for me.

Perhaps one of the developers from the Vates team can chime in as to how best to handle such a situation properly; where the NFS Server is simple no longer online to support the normal unmounting routine.

@tjkreidl said in Force Remove a NFS Storage Repository:

@kagbasi-ngc See if this thread can help you out:
https://xcp-ng.org/forum/topic/6618/how-to-remove-this-sr-nfs-storage/

A BIG THANK YOU! This was quite helpful, and helped me resolve my issued.

Here's what I ended up doing (after reading the post you shared):

• STEP 1: On each host, I ran the mount command (without any parameters).

• STEP 2: I identified the mount point of the SR in question - for me it was /run/sr-mount/<SR-UUID>

• STEP 3: On each host, I unmounted the NFS share with umount -lf /run/sr-mount/<SR-UUID>

• STEP 4: From the pool master, I identified the UUID of the PBDs with xe pbd-list sr-uuid=<SR-UUID>

• STEP 5: While still on the pool master, I unplugged each PBD with xe pbd-unplug uuid=<PBD-UUID> force=true (I had three to unplug, adjust accordingly)

• STEP 6: I confirmed in Xen Orchestra that the status of each host connection had changed to Disconnected

• STEP 7: From the pool master, I forgot the SR with xe sr-forget uuid=<SR-UUID>

Hope this helps someone out there. Thanks again @tjkreidl

Good-day folks,

I have an old NFS storage repository that was previously hosted on a Windows Server 2016 machine running NFS Server for Windows, that is being stubborn and I would like to remove it forcefully, along with anything related to it. The NFS Server is no longer online, so the connection isn't alive and I suspect the removal is failing because XOA can't unmount it.

I have tried being nice by clicking the Disconnect from all hosts button, but the tasks sits there for several hours then mocks me and disappears. I have tried to unplug the connection from each host, one at a time, same results - the wheel spins for some time then goes away.

Any assistance would be greatly appreciated, thanks.

My Environment:

Hosts: 3-node XCP-ng Pool v8.3.0
XOA: v5.106.4 build 20250604
Environment: Airgapped

@olivierlambert You got it, I'll do that. Thank you.

@olivierlambert Understood, however, I'm failing to see what part of my posting was irrelevant to the topic at hand. I was merely sharing what I'd experienced as well and providing context.

I thought this was the kind of feedback expected of community members, who want to see this project flourish?