__nonSENSE

This did the trick for me.

Update: Renaming the libvirt.img file so that it gets recreated did the trick! I was able to Enable VMs and start the array without having any disk read errors on the array's disks. I even managed to create a new VM and start it and no issues have been recorded so far. Thanks a lot @JorgeB and @trurl

Alright, I am rebuilding now. Won't be able to test the libvirt rename fix until Sunday. I'll report back if it worked. Thanks in any case for all your help so far!

OK, I will try that. I will only lose the VMs configs, correct? On another note: My Disk2 is showing as "Disabled (contents emulated)". Should I follow the guide to rebuild the drive onto itself, or is there a quicker way to restore it to the array? (I don't like to take shortcuts, but this is the 2nd rebuild within a day I would have to do)

With "Enable VMs: No", there are no issues / read errors after array start.

I am also reluctant to keep starting the array in this state, because it puts my disks into error state which I need to rebuild.

I had auto-start of disks disabled since the beginning. I always manually start the array Could this point to something other than the VMs starting being the issue (if the VMs aren't started after all)? I would love to post more diagnostics, but the process just errors.

6.10.3 also seems to auto-start the VMs, maybe I need to go back further?

OK, I will try that. Is there any dangers / things to be aware of when downgrading to an earlier Unraid version?

Some progress; I enabled the AMD-V flag and was able to start the array without any errors as long as the VMs are not enabled. I assume this is expected, as turning on VMs and starting the array will also auto-start some of the VMs (at least one of which have a SATA controller passed through, if I understood correctly?). The next step would be to keep the VMs from auto-starting, but as far as I understood, this is not a feature that is available anymore post 6.9? What do you suggest I should do? Can I somehow get rid of the VM definitions without having the VM manager enabled?

I am currently in maintenance mode, rebuilding a drive, and I have disabled the AMD-V flag. Should I reenable it before I post the screenshot of System Devices or is it OK to post it now with the flag disabled? In case it does not matter, here is the current list:

I was able to confirm that the AMD-V flag is indeed causing the issues. Could this be an issue due to a defective unit? I have read up a bit and saw that other users have used this same motherboard with Unraid. Is there anything else I could try?

Hi, I recently switched out my motherboard and CPU (from x570 Aorus Elite with 3900X to TUF Gaming Plus Wifi 2700X); the CPU is a bit older but the mainboard is brand new. After switching the hardware and booting unraid, I tried starting the array. I was greeted with millions of disk errors across all disks. I rebooted, and upgraded my BIOS (unrelated). When I started up again, the array was fine when running through the parity check (0 errors). I noticed that AMD-V was disabled (again), so I enabled it and rebooted. Upon starting the array, 2 of the 4 disks were reporting errors again during the parity check (millions). Any advice would be appreciated. Thanks! tower-diagnostics-20221221-1417.zip