JorgeB

That and also check that the power supply idle control is correctly set

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173

Then use an old flash drive as the single array device.

Log is spammed with ssh related text, reboot to clear it add the disk to parity2 and post new diags after the problem occurs.

Check here.

That means the new config wasn't properly made, try again, you need to click apply in the end.

You ca use the mover, it will require an intermediate move to the array, VMs must be off, VM services also if you're also moving that.

Number of reas/writes are basically meaningless, they can vary a lot for identical devices with same activity, e.g., after a parity check.

No idea, never seen anything similar before, but I believe it can only be hardware related.

After the rebuild should be enough, unless you see any issues.

Array needs to be started but it can be spun down, and remain so while you start the VM, assuming the VM vdisk is on a pool or unassigned device.

ATA errors are in the syslog, like these: Aug 17 14:06:48 The-Dark-Tower kernel: ata4: link is slow to respond, please be patient (ready=0) Aug 17 14:06:50 The-Dark-Tower kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Aug 17 14:06:50 The-Dark-Tower kernel: ata4.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Aug 17 14:06:50 The-Dark-Tower kernel: ata4.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Aug 17 14:06:50 The-Dark-Tower kernel: ata4.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Aug 17 14:06:50 The-Dark-Tower kernel: ata4.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Aug 17 14:06:50 The-Dark-Tower kernel: ata4.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Aug 17 14:06:50 The-Dark-Tower kernel: ata4.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Aug 17 14:06:50 The-Dark-Tower kernel: ata4.00: configured for UDMA/133 Less than before so far, but hey followed the parity disk, so that suggests a device problem.

Wait for the btrfs operation to stop, then stop array, unassign the 2Tb device (leave it unassigned for now), start array, wait for btrs balance to finish once more, after that is done you can stop the array and create a new pool.

Swap parity with disk3 and to see where the problem goes.

Still ATA errors, did you replace both cables or just check/reconnect?

Disable bonding, then configure eth1 with a static IP, different subnet.

Unlikely that a dying flash drive would make Unraid crash without anything being logged, but you can replace it if you want: https://wiki.unraid.net/Manual/Changing_The_Flash_Device

If the BIOS is correctly set and the crashes started out of the blue without anything relevant logged in the syslog it points to a hardware issue.

Check here to make sure you're using the correct "power supply idle control" setting.

@SpencerJplease check this when possible.

Since cache is NVMe don't see how having the array on the HBA would interfere with downloads to the cache device, are you sure this is reproducible, i.e., if you change the disks to the HBA again you start having the issue again. https://wiki.unraid.net/index.php/File_System_Conversion

That looks more hardware related, especially if it happens with both v6.10 and v6.11, but try going back to v6.9 to confirm if it's still stable there.

Please try booting in safe mode to see if there's any difference.

Also make sure this is correctly set.

Not sure it's possible with that plugin, I use the IPMI plugin and that one can alert you, but the board must have IPMI.