Tried to do a parity check. First one after adding a few new drives a month ago.

I added two 18TB-drives, use one as a parity drive and one in the array. The old parity drive (6TB) is now in the array as well.
Everything seemed to work fine, until I started a parity check and it stopped at 14%, with kb/s-speeds and an estimated end in 7000 days.

 

I tried to pause and cancel the parity check without success. Tried to stop the docker image and that looks like it works (it says No in the enable docker image settings), but all apps and plugins keep on running. Tried to reboot the whole system, without success. About half of all new files since the newly added drives are not visible either in unraid or in network shared drive in windows.

 

In Main under Array devices the Parity drive says it's reading data at 1GB/s, been like that for 12 hours.

All cpu cores are at 100%, also for 12 hours.

 

Checked log and all it says is 

Jan  8 09:49:03 Tower kernel: md: disk0 read error, sector=664128888
Jan  8 09:49:03 Tower kernel: md: disk0 read error, sector=2931121040
Jan  8 09:49:03 Tower kernel: md: disk0 read error, sector=4399641472

 

disk0 is the parity drive.

 

Is there anything I can do besides running a hard power off on the actual machine? And switching the parity drive for a new one?

tower-diagnostics-20230109-0938.zip

Edited January 9, 20233 yr by Tobasama
more info

Jan  7 08:02:34 Tower kernel: ata11.00: qc timeout (cmd 0xec)
Jan  7 08:02:34 Tower kernel: ata11.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Jan  7 08:02:34 Tower kernel: ata11.00: revalidation failed (errno=-5)
Jan  7 08:02:34 Tower kernel: ata11: hard resetting link
Jan  7 08:02:34 Tower kernel: ata12.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Jan  7 08:02:34 Tower kernel: ata12.00: revalidation failed (errno=-5)
Jan  7 08:02:34 Tower kernel: ata12: hard resetting link
Jan  7 08:02:35 Tower kernel: ata12: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jan  7 08:02:35 Tower kernel: ata11: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jan  7 08:02:46 Tower kernel: ata12.00: qc timeout (cmd 0xec)
Jan  7 08:02:46 Tower kernel: ata11.00: qc timeout (cmd 0xec)
Jan  7 08:02:46 Tower kernel: ata12.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Jan  7 08:02:46 Tower kernel: ata12.00: revalidation failed (errno=-5)
Jan  7 08:02:46 Tower kernel: ata12: limiting SATA link speed to 3.0 Gbps
Jan  7 08:02:46 Tower kernel: ata12: hard resetting link
Jan  7 08:02:46 Tower kernel: ata11.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Jan  7 08:02:46 Tower kernel: ata11.00: revalidation failed (errno=-5)
Jan  7 08:02:46 Tower kernel: ata11: limiting SATA link speed to 3.0 Gbps
Jan  7 08:02:46 Tower kernel: ata11: hard resetting link
Jan  7 08:02:47 Tower kernel: ata12: SATA link up 6.0 Gbps (SStatus 133 SControl 320)
Jan  7 08:02:47 Tower kernel: ata11: SATA link up 6.0 Gbps (SStatus 133 SControl 320)
Jan  7 08:02:52 Tower kernel: ata13: COMRESET failed (errno=-16)
Jan  7 08:02:52 Tower kernel: ata13: limiting SATA link speed to 3.0 Gbps
Jan  7 08:02:52 Tower kernel: ata13: hard resetting link
Jan  7 08:02:58 Tower kernel: ata13: COMRESET failed (errno=-16)
Jan  7 08:02:58 Tower kernel: ata13: reset failed, giving up
Jan  7 08:02:58 Tower kernel: ata13.00: disable device
Jan  7 08:02:58 Tower kernel: ata13: EH complete

 

Problems with all 3 disks connected to the Marvell controller, including some dropping offline, those controllers are not recommended and if you can I suggest replacing it with a recommended model.