@bvitnik good catch, that form had multiple issues, I just fixed all of them - https://github.com/benapetr/XenAdminQt/commit/4847e85f2403f3c6fd328f17754c91df21c36502 this was one of them 0 benapetr committed to benapetr/XenAdminQt refactor of new SR wizard fixed missing NFS version selector made Test Connection button appear only when we create new SR, not ISO, because xapi doesn't support probe on ISO objects implemented drop-in descriptions when nothing is provided cleaned up some qvariant scraping and invalid creation of XenLib objects (like Host) instead we retrieve them from the cache now

Support tunnel is active but I have troubles to access support "Oops, something went wrong! Don't worry, our team is already on it". I'll keep trying, thanks.

That is a frustrating loop to be in, especially with TrueNAS. Usually, when the VM fails to start after a change, it’s because XCP-ng is trying to pass through a PCI device (like an HBA) that isn't being released properly by the host. Have you checked if the "hide" parameters in your grub config are still correct? Sometimes an update can reset those, and the host grabs the controller before the VM can. Another thing to try is toggling the BIOS/UEFI mode in the VM settings - TrueNAS can be picky about that depending on which version you’re running.

@florent I can confirm that this fixes the issue!

@CodeMercenary As far as I understand it, because its Xen based, it is Numa aware by default.

Nevermind. I forgot your previous post about: You'll need to modify two files (via SSH): /opt/dell/omc/utilities/tui/bin/ome_disk_config.sh /opt/dell/mcsi/appliance/scripts/appliance_ressource.sh In these files, replace /dev/sd with /dev/xvd. I went and made these changes, and now the Data drive is loading after doing the drive scan. I should mention that doing this BEFORE first logging into the OME web interface and completing the initialization seems to be best (no further errors appear once logged in).

Pinging @Team-OS-Platform-Release

Adding @Team-XO-Backend in the loop

On 28c5e I today had it switched from all to none 2 times. Then it stayed at showing none The remote seemed to be OK I updated to 372a2 and at the moment it's showing all Time will tell

@Pilow The backups kept by LTR are just regular backups with a specific tag, which doesn't change how we treat them. If you want to avoid each of your LTR backup to depend on one another, we recommend to set a full backup interval value to your backup job, which will regularly force a full backup. (even without LTR, having an infinite chain of backups can cause problem in the long term, especially if no healthchecks are made)

@MathieuRA said: Hi, regarding your backups which do not appear on the XO5 restore page, I suggest you to open a new topic Forgot to include the link to the new topic https://xcp-ng.org/forum/topic/12040/restore-only-showing-1-vm

Nice catch @vagrantin ! Feel free to open a new thread if you have other problems.

@Pilow said: @ph7 try to put RETENTION to 1 in the schedule, as you are using LTR parameters I was running the shedule with 20 mins backup retention and it is running fine together with the LTR And here is the manual I ran at 14:56 removed [image: 1775140196713-screenshot-2026-04-02-at-16-28-13-backup.png]

@Pilow perfect!

@wgomes yup thanks for bumping this topic, still having the problem too

@DustinB If it hangs right after detecting the disk, it could be a bootloader or filesystem inconsistency from the snapshot state. Can you try booting the VM with a recovery ISO to check disk integrity or rebuild the bootloader?

had the same on one pool that needed 97 updates. RPU was going great, but couldn't migrate VM post-upgrade it is a pool of 2 hosts, second hosts still had 97 patches to pass... even if RPU was finished. we waited 10 min and the 97 patches disappeared, and then we could migrate the VM

Different use cases: Ceph is better with more hosts (at least 6 or 7 minimum) while XOSTOR is better between 3 to 7/8. We might have better Ceph support in the future for large clusters.

I think I added it after the video ^^ (between the recording and the official release)