JorgeB

Docker image is corrupt, delete and re-create.

Unfortunately that's what most likely happened, just by starting the array with VT-d enable for a few minutes can be enough to corrupt some data, and usually anything btrfs is the first to go since it's much more susceptible to kernel memory corruption. Note that if you need vt-d you can upgrade to v6.10.3-rc1, I'm confident that the corruption issue that affects mostly same vintage HP servers is resolved.

Unraid doesn't run SMART tests automatically, even for SATA drives, but note that a parity check is basically the same as an extended SMART test, so if any issues are detected there you can look at the SMART reports, for SAS devices look manly at the "Elements in grown defect list" and "Total Uncorrected Errors".

That's very weird, don't remember seeing anything similar before, you could try backing up current libvirt.img, then creating a new one (note that all VMs will be gone from the VM page, not from the server), then see if just starting the service with a new libvirt is normal, if yes create a new test VM and again check if it still starts normally, you can always restore the old ilibvirt if/when needed.

That was a good idea. Don't forget that you'll need to run a correcting parity check.

Run it again with the --rebuild-tree flag, note that it will take a few hours.

You don't need HTTPS to enable disk encryption.

Not seeing any shfs issues in the log.

Couple of things to try: Delete/rename /boot/config/network.cfg and reboot, it will default to DHCP. Iif SSL is enable edit config/ident.cfg on the flash drive and change USE_SSL from "yes" to "no", then reboot. Also you only have one NIC, right?

You should post the diagnostics grabbed when the issue is occurring.

If I understand this correctly, there can't be DMAR errors, since there's no DMA remapping, from the pdf linked above, pass-through mode is the one on the right:

You can also update to v6.10.3-rc1 and use it with VT-d enabled.

Jun 12 13:44:11 AKserver kernel: REISERFS error (device md1): vs-5150 search_by_key: invalid format found in block 1159198912. Fsck? Check filesystem on disk1. P.S. also a good idea to convert all existing reiserfs disks to XFS, reiser is not recommended for a long time.

Like mentioned either the rebuild finished and the disk is green, or did didn't and it's orange (invalid), Unraid only changes the status to green after the rebuild finished successfully.

Post new diags, there might be some filesystem corruption, some data loss might also have occurred due to the previous issues.

Yes, that was already visible in your first diags, there are some recovery options here, but based on the error I'm not very optimist they will work, you might need to re-format and restore form backups, if available.

Just boot the server and check the drive status, green ball means the rebuild finish before the crash, orange triangle means it didn't, it will rebuild from the beginning at next array start.

You can only use btrfs raid1 for pools.

Go to the board BIOS and see if there's an option to disable the Bluetooth module.

See if the docker has a support thread/page/discord, it would be the best place to ask:

Jun 11 19:48:10 TuringTower kernel: BTRFS: device fsid 253ded62-2620-46f7-a31b-57d06b615a7c devid 2 transid 2260338 /dev/sdd scanned by udevd (1205) Jun 11 19:48:10 TuringTower kernel: BTRFS: device fsid 253ded62-2620-46f7-a31b-57d06b615a7c devid 1 transid 2260338 /dev/sdc1 scanned by udevd (1197) Device 2 doesn't have a partition, it's using the whole device, looks like the older release for some reason accepted that, assuming the pool is redundant you could unassign sdd (cache2), start the array, let the pool balance to single device, then re-add the other one, it might be needed to completely wipe the other device before re-adding.

Nothing obvious, but even the services seem to be taking a lot of time to start, try booting in safe mode to rule out any plugin interference.

You should update to v6.10.3-rc1, iommu=pt is the default, re-enable VT-d in the BIOS if disabled.

Best bet would be getting a true HBA, like an LSI, besides the issue you're having now you will also run into issues in the future if for example you need to replace that controller with a different model.

You have link on eth1 but not on eth0, either swap the LAN cable to the other NIC or boot using GUI mode and go to Settings -> Network Settings -> Interface rules and make eth1 eth0