JorgeB

Please post the diagnostics: Tools -> Diagnostics

Please post diags.

Transid verify errors are usually fatal with btrfs, you can try these recovery options before re-formatting. Edit to add: btrfs restore is likely the best option to recover the data in this case.

Looks more like a connection issue, replace/swap cables to rule them out and rebuild.

At least one data device needs to be assigned, but you can use anything, even an old small flash drive for example.

Try running in safe mode for a few hours with dockers/VMs stopped, if it crashes like that it's likely a hardware problem, if it doesn't start enabling the plugins, dockers and VMs a few at a time.

Cache pool filesystem is corrupt, and you need to be careful with btrfs fsck, it might make things even worse, best way forward is to backup, re-format pool and restore data.

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

Make sure BIOS is up to date, CPU isn't being correctly identified: CPU0: Genuine Intel(R) CPU 0000 @ 2.10GHz (family: 0x6, model: 0x4f, stepping: 0x0) You can try this to see if it catches something, after booting in normal or safe mode.

There should be one explicitly mentioning vt-d, most times it's not on the CPU section.

From what I can find with google i350bb is the sensor for the Intel NIC, AFAIK the LSI HBAs typically used with Unraid don't have a temp sensor, more advanced Megaraid controllers might have.

Unmountable and disabled are two different things, though often related, does the emulated disk mount correctly now? Also good idea to post the diags, especially if you didn't reboot after the disk got disabled.

You need to first find out what's making the server crash, could be related to hardware pass trough, try disabling them all then enabling one at a time, also make sure no CPU and/or RAM overclock.

Yes, it's normal, mostly because xfs now supports reflinking.

Cache1 dropped offline: Feb 7 10:24:38 Tower7 kernel: ata6: hard resetting link Feb 7 10:24:43 Tower7 kernel: ata6: link is slow to respond, please be patient (ready=0) Feb 7 10:24:48 Tower7 kernel: ata6: COMRESET failed (errno=-16) Feb 7 10:24:48 Tower7 kernel: ata6: hard resetting link Feb 7 10:24:53 Tower7 kernel: ata6: link is slow to respond, please be patient (ready=0) Feb 7 10:24:58 Tower7 kernel: ata6: COMRESET failed (errno=-16) Feb 7 10:24:58 Tower7 kernel: ata6: hard resetting link Feb 7 10:25:03 Tower7 kernel: ata6: link is slow to respond, please be patient (ready=0) Feb 7 10:25:33 Tower7 kernel: ata6: COMRESET failed (errno=-16) Feb 7 10:25:33 Tower7 kernel: ata6: limiting SATA link speed to 3.0 Gbps Feb 7 10:25:33 Tower7 kernel: ata6: hard resetting link Feb 7 10:25:38 Tower7 kernel: ata6: COMRESET failed (errno=-16) Feb 7 10:25:38 Tower7 kernel: ata6: reset failed, giving up Feb 7 10:25:38 Tower7 kernel: ata6.00: disabled Likely a cable/connection issue, see here for more info: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=700582

Use for example midnight commander (mc on the console), then copy from the UD device (it will be in /mnt/disks/UD_name) to a user share /mnt/user/share_name

CRC errors are a connection problem, most times the SATA cable, but it can also be the controller, backplane, etc, start by replacing the SATA cable, and note that the attribute doesn't reset, so as long as it doesn't keep increasing the problem is solved.

You're missing a /, newer releases are more strict, should be /mnt/disks/applications/docker/

This won't work, you can replace one of them with the NVMe device and only them remove the other, this can all be done with the pool online, except when stopping/starting the array, instructions for all those procedures are in the FAQ:

Yes, just follow the FAQ instructions.

Doesn't look like a permissions problem, is the copy problem just from Windows or also from within Unraid?

Diags are after rebooting but not seeing anything about a read only disk8, still run a filesystem check on the emulated disk: https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui

That's just for boot selection, it doesn't matter for Unraid, all devices should be assignable.

Check that USB ports are set to 2.0, USB 1.0 is very slow booting, like mentioned UEFI it's not faster.

No, rebuilding can't fix filesystem corruption. Do you mean the disk is disable? If yes you should post the diagnostics.