NxKW

I'm daisy-chaining with the PSU’s original SATA power cables. I've switched the drives from one cable to another free one (previously only in use by the single SSD), and the issue has been resolved. Your reply confirms the issue, thanks! I guess I'm buying a new PSU.

Hi all, I’m running into persistent disk I/O errors on my Unraid server and need some help figuring out the cause. I’ve already swapped out major hardware, but the issue remains. Setup: Unraid version: 7.1.4 Motherboard: ASUS PRIME B450M-A II (brand new) Drives: [0:0:0:0]disk SanDisk Cruzer Blade 1.00 /dev/sda 30.7GB [1:0:0:0]disk ATA KINGSTON SA400S3 0100 /dev/sdb 120GB [2:0:0:0]disk ATA TOSHIBA MG09ACA1 0107 /dev/sdc 14.0TB [5:0:0:0]disk ATA ST4000VN006-3CW1 SC60 /dev/sdd 4.00TB [6:0:0:0]disk ATA TOSHIBA MG09ACA1 0107 /dev/sde 14.0TB PSU: Cooler Master MWE 650 White 230V - V2 SATA cables: Tried old and new Problem: Despite installing a new motherboard and replacing the HDDs, I’m still getting recurring errors in syslog. Example errors from syslog: Aug 20 00:00:07 FA2NAS kernel: sd 6:0:0:0: [sde] tag#11 CDB: opcode=0x88 88 00 00 00 00 00 01 bb 43 70 00 00 04 00 00 00 Aug 20 00:00:07 FA2NAS kernel: I/O error, dev sde, sector 20949712 op 0x0:(READ) flags 0x80700 phys_seg 139 prio class 3 Aug 20 00:00:07 FA2NAS kernel: sd 6:0:0:0: [sde] tag#12 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=14s Aug 20 00:00:07 FA2NAS kernel: sd 6:0:0:0: [sde] tag#12 Sense Key : Aborted Command [current] Aug 20 00:00:07 FA2NAS kernel: sd 6:0:0:0: [sde] tag#12 ASC=0x21 ASCQ=0x4 Aug 20 00:00:07 FA2NAS kernel: sd 6:0:0:0: [sde] tag#12 CDB: opcode=0x88 88 00 00 00 00 00 01 bb 48 00 00 00 06 38 00 00 Aug 20 00:00:07 FA2NAS kernel: I/O error, dev sde, sector 20949808 op 0x0:(READ) flags 0x84700 phys_seg 168 prio class 3 Aug 20 00:00:07 FA2NAS kernel: sd 6:0:0:0: [sde] tag#13 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=14s Aug 20 00:00:07 FA2NAS kernel: sd 6:0:0:0: [sde] tag#13 Sense Key : Aborted Command [current] Aug 20 00:00:07 FA2NAS kernel: sd 6:0:0:0: [sde] tag#13 ASC=0x21 ASCQ=0x4 Aug 20 00:00:07 FA2NAS kernel: sd 6:0:0:0: [sde] tag#13 CDB: opcode=0x88 88 00 00 00 00 00 01 bb 4e 38 00 00 03 c8 00 00 Aug 20 00:00:07 FA2NAS kernel: I/O error, dev sde, sector 20952472 op 0x0:(READ) flags 0x80700 phys_seg 120 prio class 3 Aug 20 00:00:08 FA2NAS kernel: ata6: EH complete Aug 20 00:00:08 FA2NAS kernel: ata6.00: exception Emask 0x50 SAct 0x80b02 SErr 0xb0802 action 0xe frozen Aug 20 00:00:08 FA2NAS kernel: ata6.00: irq_stat 0x00400000, PHY RDY changed Aug 20 00:00:08 FA2NAS kernel: ata6.00: failed command: READ FPDMA QUEUED Aug 20 00:00:08 FA2NAS kernel: ata6.00: cmd 60/08:00:d0:00:00:00:40 tag 5 ncq dma 4096 in Aug 20 00:00:08 FA2NAS kernel: res 40/00:00:00:00:00:00:00:00/00 Emask 0x50 (ATA bus error) Aug 20 00:00:08 FA2NAS kernel: ata6.00: status: { DRDY } Aug 20 00:00:08 FA2NAS kernel: ata6.00: failed command: READ FPDMA QUEUED Aug 20 00:00:08 FA2NAS kernel: ata6.00: cmd 60/08:98:00:00:01:00:40 tag 19 ncq dma 4096 in Aug 20 00:00:08 FA2NAS kernel: res 40/00:00:00:00:00:00:00:00/00 Emask 0x50 (ATA bus error) Aug 20 00:00:08 FA2NAS kernel: ata6.00: status: { DRDY } Aug 20 00:00:08 FA2NAS kernel: ata6: hard resetting link Aug 20 00:00:13 FA2NAS kernel: ata6: SATA link down (SStatus 0 SControl 300) Aug 20 00:00:13 FA2NAS kernel: ata6: hard resetting link Aug 20 00:00:18 FA2NAS kernel: ata6: link is slow to respond, please be patient (ready=0) Aug 20 00:00:22 FA2NAS kernel: ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Aug 20 00:00:22 FA2NAS kernel: ata6.00: configured for UDMA/133 Aug 20 00:00:22 FA2NAS kernel: ata6: limiting SATA link speed to 3.0 Gbps Aug 20 00:00:23 FA2NAS kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Aug 20 00:00:23 FA2NAS kernel: ata6.00: configured for UDMA/133 Aug 20 00:00:23 FA2NAS kernel: sd 6:0:0:0: [sde] tag#15 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=15s Aug 20 00:00:23 FA2NAS kernel: sd 6:0:0:0: [sde] tag#15 Sense Key : Aborted Command [current] Aug 20 00:00:23 FA2NAS kernel: sd 6:0:0:0: [sde] tag#15 ASC=0x21 ASCQ=0x4 Aug 20 00:00:23 FA2NAS kernel: sd 6:0:0:0: [sde] tag#15 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Aug 20 00:00:23 FA2NAS kernel: I/O error, dev sde, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 Aug 20 00:00:23 FA2NAS kernel: ata6: EH complete Aug 20 00:00:28 FA2NAS kernel: ata6.00: exception Emask 0x50 SAct 0xe0000 SErr 0x30802 action 0xe frozen Aug 20 00:00:28 FA2NAS kernel: ata6.00: irq_stat 0x00400000, PHY RDY changed Aug 20 00:00:28 FA2NAS kernel: ata6: SError: { RecvComm HostInt PHYRdyChg PHYInt } Aug 20 00:00:28 FA2NAS kernel: ata6.00: failed command: READ FPDMA QUEUED Aug 20 00:00:28 FA2NAS kernel: ata6.00: cmd 60/08:bc:e3:ad/04:00:05:00:40 tag 25 ncq dma 614400 in Aug 20 00:00:28 FA2NAS kernel: res 40/00:00:00:00:00:00:00:00/00 Emask 0x50 (ATA bus error) Aug 20 00:00:28 FA2NAS kernel: ata6.00: status: { DRDY } What I’ve tried so far: Replaced motherboard (new chipset, new controller) Replaced both HDDs with brand new ones Errors persist on the new drives Verified drives are detected correctly by Unraid Questions / next steps I need help with: Has anyone else run into these exact errors in Unraid before? How did you fix it? Could this be caused by bad PSU cables or unstable power? Could this be a SATA cable/port issue? Any other common causes of repeated ATA link resets that I might have overlooked? Diagnostics diagnostics-20250820-0958.zip