JorgeB

Is that on all drives or SAS drives only? Currently SMART tests don't work on SAS devices.

Not a good idea to write to multiple array disks at the same time since parity needs to updated for all and it will bottleneck.

first value is current read speed, second current write speed Toggle is on the upper right corner.

On the diags, loads.txt Start by stopping all those writes, you can see real-time disk activity on the GUI

Well, in the latest diags it's not writing to 10 array disks, but it's still writing to 8, so very slow performance is expected, simultaneous writes to more than 1 array disk will always be slow.

Start the array and it should mount, if it doesn't post new diags.

Please post the diagnostics: Tools -> Diagnostics

CPU should be enough, posting the diagnostics during a move might provide some clues.

Parity can't help with filesystem corruption, which was the main problem here.

Completely unrelated to this report, one of you cache devices is dropping offline: Apr 20 21:45:20 microserver kernel: ata6: EH complete Apr 20 21:45:22 microserver kernel: ata6: limiting SATA link speed to 1.5 Gbps Apr 20 21:45:22 microserver kernel: ata6.00: exception Emask 0x10 SAct 0x8000000 SErr 0x280100 action 0x6 frozen Apr 20 21:45:22 microserver kernel: ata6.00: irq_stat 0x08000000, interface fatal error Apr 20 21:45:22 microserver kernel: ata6: SError: { UnrecovData 10B8B BadCRC } Apr 20 21:45:22 microserver kernel: ata6.00: failed command: READ FPDMA QUEUED Apr 20 21:45:22 microserver kernel: ata6.00: cmd 60/00:d8:98:3e:32/01:00:01:00:00/40 tag 27 ncq dma 131072 in Apr 20 21:45:22 microserver kernel: res 40/00:dc:98:3e:32/00:00:01:00:00/40 Emask 0x10 (ATA bus error) Apr 20 21:45:22 microserver kernel: ata6.00: status: { DRDY } Apr 20 21:45:22 microserver kernel: ata6: hard resetting link Apr 20 21:45:24 microserver kernel: ata6: SATA link down (SStatus 1 SControl 310) Apr 20 21:45:24 microserver kernel: ata6: hard resetting link Apr 20 21:45:26 microserver kernel: ata6: SATA link down (SStatus 1 SControl 310) Apr 20 21:45:26 microserver kernel: ata6: hard resetting link Apr 20 21:45:29 microserver kernel: ata6: SATA link down (SStatus 1 SControl 310) Apr 20 21:45:29 microserver kernel: ata6.00: disabled ATA6 is MTFDDAK256MAM-1K12_1318093908F1, it wasn't even assigned at server start, but since it's part of the pool it was still being used, looks more like a cable/connection issue, see here for more info and how to better monitor the pool for errors. If more help is needed please start a thread on the general support forum.

In that case do it.

It's normal for some drives, firmware related.

Never a good sign, still very far from the threshold, hard call to make, since RMA drives are usually refurbished, and at best 50/50 chance they will fail soon.

Strange, then you should post in the UD plugin support thread to see what's confusing it.

That seems unlikely, FreeNAS creates a 2GB partition before the main one, likely the large partition was reformatted to ntfs but the smaller one remains, please post output of: fdisk -l /dev/sdh

For the csrf errors: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=545988

We'd need the diags before rebooting, grab them if it happens again.

Could be the typical Ryzen issues, also see here.

Does it make a difference if you leave the default gateway for eth 1 blank?

use -L

Check filesystem on both: https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui

Known problem with the 9230 and VT-d enable, this works for some.

Yes, memtest doesn't detect every type of error, though one that happens as frequently as you say should be detected. Try a single RAM channel like I mentioned, in case the CPU has issues with one of them.

It doesn't mention downgraded because it's reporting the same x4 as the link capability, which is wrong.

If it's mounted read-only it won't affect parity, though it will affect rebuild speed if being accessed regularly.