JorgeB

No really, but Unraid only disables a disk when a write fails, one thing you can do is instead of clicking shutdown/reboot on the GUI, first stop the array, disks can't get disable after array is stopped, so if it happens after array stop grab diags then, if not you can reboot or shutdown safely.

No Asmedia controller is being detected, try a different slot if available.

That suggests they are getting disable on shutdown. Yes, see here: https://wiki.unraid.net/Troubleshooting#Re-enable_the_drive You can rebuild both at the same time.

Yep. There could be other issues, but the controller should still be set to AHCI.

Don't see any attempts to run the mover in the log, try again, also make sure mover logging is enable.

Yes, that's pretty low.

Most can also handle 1x8+2x4, that's what I have on one of my servers with a Skylake CPU.

Worth trying if available.

Sorry, can't help with that, best to post in the existing docker support thread.

Please post the diagnostics: Tools -> Diagnostics

Diags are after rebooting so we can't see what happened but both disks looks fine and multiple disks getting disabled at the same time suggest a power/connection problem, replace/swap cables/slots to rule that out and post new diags if it happens again, before rebooting.

Please use the existing plugin support thread:

Replace cables on disk2 then post new diags after array start.

Not really, nothing about why it crashed, it could be a hardware problem, one thing you can try it to boot the server in safe mode with all docker/VMs disable, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.

No valid filesystem in being detected on disk1, are you sure that was a data disk and not parity?

Is it the same after booting in safe mode?

You can try this and then post that log, as well the complete diagnostics.

CRC errors are a connection problem, usually the SATA cable, reallocated sectors no so good, especially on a new disk, but can be OK if it's a low number and remains stable.

You can try, I get close to 1GB/s from my VMs using the virtual NIC, but you're not the first one with this issue, possibly just the different hardware or some configuration setting.

You can't have a vdisk larger than the disk it resides in, each disk is a separate filesystem with Unraid, and no file can span more than one disk, you need to resize or re-create that one.

Replace cables on disk1 then post new diags.

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=480418 Note that latest releases have a bug and cache replacement doesn't work, don't remember any reports about removal not working, but also didn't confirm it's working.

ATA errors on the SSD: Feb 4 17:44:44 Tower kernel: sd 1:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Feb 4 17:44:44 Tower kernel: sd 1:0:0:0: [sdb] tag#0 Sense Key : 0x5 [current] Feb 4 17:44:44 Tower kernel: sd 1:0:0:0: [sdb] tag#0 ASC=0x21 ASCQ=0x4 Feb 4 17:44:44 Tower kernel: sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x2a 2a 00 00 00 cd 20 00 01 a0 00 Feb 4 17:44:44 Tower kernel: print_req_error: I/O error, dev sdb, sector 52512 Feb 4 17:44:44 Tower kernel: BTRFS error (device sdb1): bdev /dev/sdb1 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0 SATA controller is set to IDE, try again after changing it to AHCI.

This would be a board or NVMe issue, try the NVMe device in a different m.2 slot if available.