I've had some recurring issues with drives that I've tried resolving myself, but figured it might be time to ask people that know more than me. I initially noticed it by hearing odd noises coming from a drive in the server (I'd describe it as a kick, then a scrabble). No errors show on the array on the Main page, but stuff shows up in the logs like:

May  9 16:03:36 Tower kernel: ata5.00: irq_stat 0x00400000, PHY RDY changed
May  9 16:03:36 Tower kernel: ata5: SError: { Persist PHYRdyChg 10B8B }
May  9 16:03:36 Tower kernel: ata5.00: failed command: READ FPDMA QUEUED
May  9 16:03:36 Tower kernel: ata5.00: cmd 60/28:88:58:b7:06/00:00:f4:01:00/40 tag 17 ncq dma 20480 in
May  9 16:03:36 Tower kernel:         res 40/00:00:20:b7:06/00:00:f4:01:00/40 Emask 0x10 (ATA bus error)
May  9 16:03:36 Tower kernel: ata5.00: status: { DRDY }
May  9 16:03:36 Tower kernel: ata5.00: failed command: READ FPDMA QUEUED
May  9 16:03:36 Tower kernel: ata5.00: cmd 60/20:a0:80:b7:06/00:00:f4:01:00/40 tag 20 ncq dma 16384 in
May  9 16:03:36 Tower kernel:         res 40/00:00:20:b7:06/00:00:f4:01:00/40 Emask 0x10 (ATA bus error)
May  9 16:03:36 Tower kernel: ata5.00: status: { DRDY }
May  9 16:03:36 Tower kernel: ata5.00: failed command: READ FPDMA QUEUED
May  9 16:03:36 Tower kernel: ata5.00: cmd 60/28:a8:a0:b7:06/00:00:f4:01:00/40 tag 21 ncq dma 20480 in
May  9 16:03:36 Tower kernel:         res 40/00:00:20:b7:06/00:00:f4:01:00/40 Emask 0x10 (ATA bus error)
May  9 16:03:36 Tower kernel: ata5.00: status: { DRDY }
May  9 16:03:36 Tower kernel: ata5.00: failed command: READ FPDMA QUEUED
May  9 16:03:36 Tower kernel: ata5.00: cmd 60/28:b0:f8:19:3a/00:00:f4:01:00/40 tag 22 ncq dma 20480 in
May  9 16:03:36 Tower kernel:         res 40/00:00:20:b7:06/00:00:f4:01:00/40 Emask 0x10 (ATA bus error)
May  9 16:03:36 Tower kernel: ata5.00: status: { DRDY }
May  9 16:03:36 Tower kernel: ata5.00: failed command: READ FPDMA QUEUED
May  9 16:03:36 Tower kernel: ata5.00: cmd 60/60:b8:c8:b7:06/00:00:f4:01:00/40 tag 23 ncq dma 49152 in
May  9 16:03:36 Tower kernel:         res 40/00:00:20:b7:06/00:00:f4:01:00/40 Emask 0x10 (ATA bus error)
May  9 16:03:36 Tower kernel: ata5.00: status: { DRDY }
May  9 16:03:36 Tower kernel: ata5: hard resetting link
May  9 16:03:42 Tower kernel: ata5: link is slow to respond, please be patient (ready=0)
May  9 16:03:46 Tower kernel: ata5: found unknown device (class 0)
May  9 16:03:46 Tower kernel: ata5: softreset failed (device not ready)
May  9 16:03:46 Tower kernel: ata5: hard resetting link
May  9 16:03:48 Tower kernel: ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May  9 16:03:48 Tower kernel: ata5.00: supports DRM functions and may not be fully accessible
May  9 16:03:48 Tower kernel: ata5.00: supports DRM functions and may not be fully accessible
May  9 16:03:48 Tower kernel: ata5.00: configured for UDMA/33
May  9 16:03:48 Tower kernel: ata5: EH complete
May  9 16:03:51 Tower kernel: ata5.00: exception Emask 0x10 SAct 0x18 SErr 0x90300 action 0xe frozen

 

I've tried swapping drives, changing the SATA controller for a SAS to SATA card, changed SATA cables, swapped power extenders, etc. I'm open to trying some of those steps again, just want to outline what I've tried. I'm currently running 6.12.6 but this has happened across multiple versions, and I've attached my diagnostics. Thank you to anyone who helps look at this.

tower-diagnostics-20240509-1606.zip

8 hours ago, johnmanyjohns said:

I've had some recurring issues with drives

Is this with multiple drives? It's not logged as a disk problem, by 

 

8 hours ago, johnmanyjohns said:

swapped power extenders

do you mean splitters? If yes what kind are you using?