Getting error on each drive when doing parity sync

[delgadot2040]

Hey all,

 

I been having an odd one the past few days regarding my drives.  First i noticed one drive was making some noise during a scheduled parity check. I looked at the server and noticed it was only going at like 5mbps for the check when i usually hit around 120-150mbps. I saw the log and it said it was one of my white label WD shucked drives. so i thought maybe its just crapping out on me. removed it from the array and tried again parity sync with it unassigned. now the same log error appeared on a new seagate drive... at least this time the speed started about 70mbps now at 140, but it cant be the drive.  something else is going on here and im not sure what.  this is what the log looks like during parity sync.  the only thing the changed between the attempts was first it was ata5, and once unassigned it became ata2.  i have attached my diagnostics. 

 

i tried unplugging all cables and putting them back but got the same results

 

Quote

Apr  1 21:25:59 PCserver kernel: ata2.00: failed command: READ FPDMA QUEUED
Apr  1 21:25:59 PCserver kernel: ata2.00: cmd 60/10:e0:70:53:3a/02:00:01:00:00/40 tag 28 ncq dma 270336 in
Apr  1 21:25:59 PCserver kernel:         res 40/00:e8:80:55:3a/00:00:01:00:00/40 Emask 0x50 (ATA bus error)
Apr  1 21:25:59 PCserver kernel: ata2.00: status: { DRDY }
Apr  1 21:25:59 PCserver kernel: ata2.00: failed command: READ FPDMA QUEUED
Apr  1 21:25:59 PCserver kernel: ata2.00: cmd 60/b0:e8:80:55:3a/01:00:01:00:00/40 tag 29 ncq dma 221184 in
Apr  1 21:25:59 PCserver kernel:         res 40/00:e8:80:55:3a/00:00:01:00:00/40 Emask 0x50 (ATA bus error)
Apr  1 21:25:59 PCserver kernel: ata2.00: status: { DRDY }
Apr  1 21:25:59 PCserver kernel: ata2.00: failed command: READ FPDMA QUEUED
Apr  1 21:25:59 PCserver kernel: ata2.00: cmd 60/c8:f0:a8:58:3a/03:00:01:00:00/40 tag 30 ncq dma 495616 in
Apr  1 21:25:59 PCserver kernel:         res 40/00:e8:80:55:3a/00:00:01:00:00/40 Emask 0x50 (ATA bus error)
Apr  1 21:25:59 PCserver kernel: ata2.00: status: { DRDY }
Apr  1 21:25:59 PCserver kernel: ata2.00: failed command: READ FPDMA QUEUED
Apr  1 21:25:59 PCserver kernel: ata2.00: cmd 60/00:f8:b0:5d:3a/04:00:01:00:00/40 tag 31 ncq dma 524288 in
Apr  1 21:25:59 PCserver kernel:         res 40/00:e8:80:55:3a/00:00:01:00:00/40 Emask 0x50 (ATA bus error)
Apr  1 21:25:59 PCserver kernel: ata2.00: status: { DRDY }
Apr  1 21:25:59 PCserver kernel: ata2: hard resetting link
Apr  1 21:26:01 PCserver kernel: ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Apr  1 21:26:01 PCserver kernel: ata5.00: configured for UDMA/33
Apr  1 21:26:05 PCserver kernel: ata6: link is slow to respond, please be patient (ready=0)
Apr  1 21:26:05 PCserver kernel: ata2: link is slow to respond, please be patient (ready=0)
Apr  1 21:26:09 PCserver kernel: ata6: COMRESET failed (errno=-16)
Apr  1 21:26:09 PCserver kernel: ata6: hard resetting link
Apr  1 21:26:09 PCserver kernel: ata2: COMRESET failed (errno=-16)
Apr  1 21:26:09 PCserver kernel: ata2: hard resetting link

 

System Information

Model:Custom

M/B:Micro-Star International Co., Ltd. Z590 PRO WIFI (MS-7D09) Version 1.0 s/n 07D0910_L31E243506

BIOS:American Megatrends International, LLC. Version 1.90 Dated 06/06/2023

CPU:11th Gen Intel® Core™ i9-11900KF @ 3.50GHz

HVM:Enabled

IOMMU:Enabled

Cache:L1 Cache: 384 KiB, L1 Cache: 256 KiB, L2 Cache: 4 MiB, L3 Cache: 16 MiB

Memory:32 GiB DDR4 (max. installable capacity 64 GiB)

Network:eth0: 1000 Mbps, full duplex, mtu 1500

Kernel:Linux 6.1.82-Unraid x86_64

OpenSSL:1.1.1v

 

 

pcserver-diagnostics-20240401-2125.zip

Edited April 2 by delgadot2040

[JorgeB]

Looks more like a power/connection issue, check/replace cables, both power and SATA, for both disks.

[delgadot2040]

14 hours ago, JorgeB said:

Looks more like a power/connection issue, check/replace cables, both power and SATA, for both disks.

just checked on the status of the parity sync and its 67% done going 141mbps. so that looks normal but the log says this now

Quote

Apr  2 16:17:26 PCserver kernel: ata6.00: exception Emask 0x50 SAct 0x7cc0 SErr 0x4890800 action 0xe frozen
Apr  2 16:17:26 PCserver kernel: ata6.00: irq_stat 0x0d400040, interface fatal error, connection status changed
Apr  2 16:17:26 PCserver kernel: ata6: SError: { HostInt PHYRdyChg 10B8B LinkSeq DevExch }
Apr  2 16:17:26 PCserver kernel: ata6.00: failed command: READ FPDMA QUEUED
Apr  2 16:17:26 PCserver kernel: ata6.00: cmd 60/40:30:10:f6:de/05:00:0f:04:00/40 tag 6 ncq dma 688128 in
Apr  2 16:17:26 PCserver kernel:         res 40/00:68:90:0b:df/00:00:0f:04:00/40 Emask 0x50 (ATA bus error)
Apr  2 16:17:26 PCserver kernel: ata6.00: status: { DRDY }
Apr  2 16:17:26 PCserver kernel: ata6.00: failed command: READ FPDMA QUEUED
Apr  2 16:17:26 PCserver kernel: ata6.00: cmd 60/40:38:50:fb:de/05:00:0f:04:00/40 tag 7 ncq dma 688128 in
Apr  2 16:17:26 PCserver kernel:         res 40/00:68:90:0b:df/00:00:0f:04:00/40 Emask 0x50 (ATA bus error)
Apr  2 16:17:26 PCserver kernel: ata6.00: status: { DRDY }
Apr  2 16:17:26 PCserver kernel: ata6.00: failed command: READ FPDMA QUEUED
Apr  2 16:17:26 PCserver kernel: ata6.00: cmd 60/40:50:90:00:df/05:00:0f:04:00/40 tag 10 ncq dma 688128 in
Apr  2 16:17:26 PCserver kernel:         res 40/00:68:90:0b:df/00:00:0f:04:00/40 Emask 0x50 (ATA bus error)
Apr  2 16:17:26 PCserver kernel: ata6.00: status: { DRDY }
Apr  2 16:17:26 PCserver kernel: ata6.00: failed command: READ FPDMA QUEUED
Apr  2 16:17:26 PCserver kernel: ata6.00: cmd 60/80:58:d0:05:df/00:00:0f:04:00/40 tag 11 ncq dma 65536 in
Apr  2 16:17:26 PCserver kernel:         res 40/00:68:90:0b:df/00:00:0f:04:00/40 Emask 0x50 (ATA bus error)
Apr  2 16:17:26 PCserver kernel: ata6.00: status: { DRDY }
Apr  2 16:17:26 PCserver kernel: ata6.00: failed command: READ FPDMA QUEUED
Apr  2 16:17:26 PCserver kernel: ata6.00: cmd 60/40:60:50:06:df/05:00:0f:04:00/40 tag 12 ncq dma 688128 in
Apr  2 16:17:26 PCserver kernel:         res 40/00:68:90:0b:df/00:00:0f:04:00/40 Emask 0x50 (ATA bus error)
Apr  2 16:17:26 PCserver kernel: ata6.00: status: { DRDY }
Apr  2 16:17:26 PCserver kernel: ata6.00: failed command: READ FPDMA QUEUED
Apr  2 16:17:26 PCserver kernel: ata6.00: cmd 60/40:68:90:0b:df/05:00:0f:04:00/40 tag 13 ncq dma 688128 in
Apr  2 16:17:26 PCserver kernel:         res 40/00:68:90:0b:df/00:00:0f:04:00/40 Emask 0x50 (ATA bus error)
Apr  2 16:17:26 PCserver kernel: ata6.00: status: { DRDY }
Apr  2 16:17:26 PCserver kernel: ata6.00: failed command: READ FPDMA QUEUED
Apr  2 16:17:26 PCserver kernel: ata6.00: cmd 60/40:70:d0:10:df/05:00:0f:04:00/40 tag 14 ncq dma 688128 in
Apr  2 16:17:26 PCserver kernel:         res 40/00:68:90:0b:df/00:00:0f:04:00/40 Emask 0x50 (ATA bus error)
Apr  2 16:17:26 PCserver kernel: ata6.00: status: { DRDY }
Apr  2 16:17:26 PCserver kernel: ata6: hard resetting link
Apr  2 16:17:31 PCserver kernel: ata6: link is slow to respond, please be patient (ready=0)
Apr  2 16:17:36 PCserver kernel: ata6: COMRESET failed (errno=-16)
Apr  2 16:17:36 PCserver kernel: ata6: hard resetting link
Apr  2 16:17:41 PCserver kernel: ata6: link is slow to respond, please be patient (ready=0)
Apr  2 16:17:42 PCserver kernel: ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Apr  2 16:17:42 PCserver kernel: ata6.00: configured for UDMA/133
Apr  2 16:17:42 PCserver kernel: ata6: EH complete

as i thought the issues just keeps shifting to every ata, now at number 6. it cant be that every cable is messed up right?

 

 

[delgadot2040]

just reading up a bit and now am questioning if this is the source of my problem?

this is how im powering every drive in my case thru a 750w PSU

 

if this is likely the reason for the issue, can someone recomend me a proper or better alternative to use for 6 drives?

[itimpi]

If using SATA->SATA power splitters then you do not want to split a SATA connection more than 2 way as the host end is limited by the current carrying capacity of its SATA connector.   If using Molex->SATA then you can get away with a 4-way split.