JorgeB

Almost certainly there was something else, like a docker or plugin, using the array.

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

Connect that drive to the onboard SATA controller, swap with another one if needed, might be a compatibility issue with the controller.

11:55:06 AM md1 0.80 0.80 5.00 0.00 7.25 7.58 487712.50 36.32 11:55:06 AM md2 0.20 0.00 0.20 0.00 1.00 0.15 0.00 14.76 11:55:06 AM md4 3.60 29.60 32.00 0.00 17.11 8.55 1527.72 100.00 11:55:06 AM md5 12.00 96.80 32.00 0.00 10.73 9.18 750.15 100.00 11:55:06 AM md6 4.60 59.20 0.00 0.00 12.87 0.04 7.61 3.34 11:55:06 AM md7 3.40 44.80 0.00 0.00 13.18 0.03 8.71 2.90 11:55:06 AM md9 0.20 0.80 0.00 0.00 4.00 288.34 34519.00 100.00 These suggest some activity going on to the array besides the parity check, as that should no register on the md devices, especially disks 4, 5 and 9.

Kind of strange results, don't usually see usage on the MD devices, you have more than 1 at 100%, all SMR disks, but not all SMR disks are the same, server load is also very high, likely due to i/o wait, pause the check and run the diskspeed docker.

Sorry, first install the systat package from nerd pack.

Constant ATA errors on ATA1 and ATA2: Jan 2 09:53:28 Tower kernel: ata1.00: link online but device misclassified Jan 2 09:53:28 Tower kernel: ata1: link online but 1 devices misclassified, device detection might fail Jan 2 09:53:29 Tower kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jan 2 09:53:29 Tower kernel: ata2.00: link online but device misclassified Jan 2 09:53:29 Tower kernel: ata2: link online but 1 devices misclassified, retrying Jan 2 09:53:29 Tower kernel: ata2: reset failed (errno=-11), retrying in 10 secs Jan 2 09:53:39 Tower kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jan 2 09:53:39 Tower kernel: ata1.00: link online but device misclassified Jan 2 09:53:39 Tower kernel: ata1: link online but 1 devices misclassified, retrying Jan 2 09:53:39 Tower kernel: ata1: reset failed (errno=-11), retrying in 10 secs Jan 2 09:53:39 Tower kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jan 2 09:53:39 Tower kernel: ata2.00: link online but device misclassified Jan 2 09:53:39 Tower kernel: ata2: link online but 1 devices misclassified, retrying Jan 2 09:53:39 Tower kernel: ata2: reset failed (errno=-11), retrying in 35 secs Jan 2 09:53:49 Tower kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jan 2 09:53:49 Tower kernel: ata1.00: link online but device misclassified Probably the SSDs, try connecting them in the other controller.

Please post the diagnostics, ideally before rebooting.

You mean the latest sas2flash didn't work?

Please post output of: sar -dp 5 5

These are normal.

Pool is fine, and don't see any other issues in the log.

Doesn't look like a disk problem, might be controller/power/connection related, see if the affected disks have something in common, like a controller or power cable/splitter, if not it could be the PSU.

ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 200 200 051 - 29 200 Multi_Zone_Error_Rate ---R-- 200 200 000 - 1 Both these attributes should be 0 on a healthy WD drive, doesn't means the disk is about to fail but if one or both keep increasing there will likely be more read errors soon.

Doesn't look like a disk problem, replace/swap both cables to rule them out and if the emulated disk is mounting correctly rebuild on top.

Please report UD issues in the existing plugin support thread:

You can get much more than that with SATA disks, see turbo write, I get between 100 and 200MB/s+, depending if I'm writing to the outer or inner sectors of the disks, SAS disks are not going make much (if any) difference with Unraid.

I would like to see diags after that.

For me it was the Dolby Atmos Home Theater upgrade. Happy New Year!

Did you try booting in safe mode?

If a different computer boots with the same flash it suggests a hardware problem.

Changed Status to Closed Changed Priority to Other

That is not the mover, if the share is set to cache=yes and it runs out of space data will overflow to the array: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=537383

Mover runs on the set schedule: Settings -> Scheduler

Writes are always done to one data device plus parity, and they will be limited by the slowest of the two. Tthough there's no official array SSD support yet, they work, and work faster that disks, if you use good SSDs, I get close to 400MB/s on my small SSD array.