June 9, 20251 yr I have been having issues with my parity and one other drive that keep giving the same error. The log from the drive shows this for both:Jun 9 05:46:52 Kosmos kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozenJun 9 05:46:52 Kosmos kernel: ata1.00: failed command: FLUSH CACHE EXTJun 9 05:46:52 Kosmos kernel: ata1.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 22Jun 9 05:46:52 Kosmos kernel: ata1.00: status: { DRDY }Jun 9 05:46:52 Kosmos kernel: ata1: hard resetting linkJun 9 05:46:57 Kosmos kernel: ata1: link is slow to respond, please be patient (ready=0)Jun 9 05:47:02 Kosmos kernel: ata1: COMRESET failed (errno=-16)Jun 9 05:47:02 Kosmos kernel: ata1: hard resetting linkJun 9 05:47:08 Kosmos kernel: ata1: link is slow to respond, please be patient (ready=0)Jun 9 05:47:12 Kosmos kernel: ata1: COMRESET failed (errno=-16)Jun 9 05:47:12 Kosmos kernel: ata1: hard resetting linkJun 9 05:47:18 Kosmos kernel: ata1: link is slow to respond, please be patient (ready=0)Jun 9 05:47:47 Kosmos kernel: ata1: COMRESET failed (errno=-16)Jun 9 05:47:47 Kosmos kernel: ata1: limiting SATA link speed to 3.0 GbpsJun 9 05:47:47 Kosmos kernel: ata1: hard resetting linkJun 9 05:47:52 Kosmos kernel: ata1: COMRESET failed (errno=-16)Jun 9 05:47:52 Kosmos kernel: ata1: reset failed, giving upJun 9 05:47:52 Kosmos kernel: ata1.00: disable deviceJun 9 05:47:52 Kosmos kernel: ata1: EH completeJun 9 05:47:52 Kosmos kernel: sd 1:0:0:0: [sdb] tag#23 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=123sJun 9 05:47:52 Kosmos kernel: sd 1:0:0:0: [sdb] tag#23 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00Jun 9 05:47:52 Kosmos kernel: I/O error, dev sdb, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 2Jun 9 05:47:52 Kosmos kernel: sd 1:0:0:0: [sdb] tag#4 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0sJun 9 05:47:52 Kosmos kernel: sd 1:0:0:0: [sdb] tag#4 CDB: opcode=0x8a 8a 00 00 00 00 01 00 2d 8e 78 00 00 00 08 00 00Jun 9 05:47:52 Kosmos kernel: I/O error, dev sdb, sector 4297952888 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0Jun 9 05:47:52 Kosmos kernel: I/O error, dev sdb, sector 4297952888 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0Jun 9 05:50:09 Kosmos kernel: sd 1:0:0:0: [sdb] tag#19 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0sJun 9 05:50:09 Kosmos kernel: sd 1:0:0:0: [sdb] tag#19 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00I have also added the diagnostics. I have changed the cables already and gonna reconnect all the power cables properly as well. Would anyone have any idea of what the issue could be? kosmos-diagnostics-20250609-1029.zip
June 9, 20251 yr Author Yes, using two sata power splitters to get power to all the drives. Just ordered a new power supply with enough sata connections to see if that will fix the issues.
June 21, 20251 yr Author So I have changed the power supply, changed the sata cables, ran SMART tests on all the drives, but they keep giving me the same issues. A couple hours after finishing parity syncing, one of the drives gives a drive error. They are always the same kinda drive errors. The latest one today is the parity drive that I just changed for a brand new one I had still around and the error it's giving me is:Jun 21 13:54:17 Kosmos kernel: ata2: SATA max UDMA/133 abar m2048@0x8f932000 port 0x8f932180 irq 131 lpm-pol 0Jun 21 13:54:17 Kosmos kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)Jun 21 13:54:17 Kosmos kernel: ata2.00: supports DRM functions and may not be fully accessibleJun 21 13:54:17 Kosmos kernel: ata2.00: ATA-10: ST5000LM000-2AN170, 0001, max UDMA/133Jun 21 13:54:17 Kosmos kernel: ata2.00: 9767541168 sectors, multi 0: LBA48 NCQ (depth 32), AAJun 21 13:54:17 Kosmos kernel: ata2.00: Features: TrustJun 21 13:54:17 Kosmos kernel: ata2.00: supports DRM functions and may not be fully accessibleJun 21 13:54:17 Kosmos kernel: ata2.00: configured for UDMA/133Jun 21 13:54:17 Kosmos kernel: sd 2:0:0:0: [sdb] 9767541168 512-byte logical blocks: (5.00 TB/4.55 TiB)Jun 21 13:54:17 Kosmos kernel: sd 2:0:0:0: [sdb] 4096-byte physical blocksJun 21 13:54:17 Kosmos kernel: sd 2:0:0:0: [sdb] Write Protect is offJun 21 13:54:17 Kosmos kernel: sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00Jun 21 13:54:17 Kosmos kernel: sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUAJun 21 13:54:17 Kosmos kernel: sd 2:0:0:0: [sdb] Preferred minimum I/O size 4096 bytesJun 21 13:54:17 Kosmos kernel: sdb: sdb1Jun 21 13:54:17 Kosmos kernel: sd 2:0:0:0: [sdb] Attached SCSI diskJun 21 13:55:42 Kosmos emhttpd: online: ST5000LM000-2AN170_WCJ9LKDM (sdb) 512 9767541168Jun 21 13:55:42 Kosmos sudo: root : TTY=console ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/hdparm -S 241 -B 129 /dev/sdbJun 21 13:55:42 Kosmos emhttpd: /bin/lsblk -lnbo TYPE,NAME,START,SIZE /dev/sdb 2>&1Jun 21 13:55:42 Kosmos emhttpd: disk sdb 5000981078016Jun 21 13:55:42 Kosmos emhttpd: part sdb1 64 5000981028352Jun 21 13:55:42 Kosmos emhttpd: device sdb partition: sdb1 type: gpt start: 64 size: 4883770532, code: 0xee (3)Jun 21 13:55:42 Kosmos kernel: mdcmd (1): import 0 sdb 64 4883770532 0 ST5000LM000-2AN170_WCJ9LKDMJun 21 13:55:42 Kosmos kernel: md: import disk0: (sdb) ST5000LM000-2AN170_WCJ9LKDM size: 4883770532 Jun 21 13:55:43 Kosmos emhttpd: read SMART /dev/sdbJun 21 16:32:13 Kosmos kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozenJun 21 16:32:13 Kosmos kernel: ata2.00: failed command: FLUSH CACHE EXTJun 21 16:32:13 Kosmos kernel: ata2.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 14Jun 21 16:32:13 Kosmos kernel: ata2.00: status: { DRDY }Jun 21 16:32:13 Kosmos kernel: ata2: hard resetting linkJun 21 16:32:18 Kosmos kernel: ata2: link is slow to respond, please be patient (ready=0)Jun 21 16:32:23 Kosmos kernel: ata2: hard resetting linkJun 21 16:32:28 Kosmos kernel: ata2: link is slow to respond, please be patient (ready=0)Jun 21 16:32:33 Kosmos kernel: ata2: hard resetting linkJun 21 16:32:39 Kosmos kernel: ata2: link is slow to respond, please be patient (ready=0)Jun 21 16:33:08 Kosmos kernel: ata2: limiting SATA link speed to 3.0 GbpsJun 21 16:33:08 Kosmos kernel: ata2: hard resetting linkJun 21 16:33:13 Kosmos kernel: ata2: hardreset failedJun 21 16:33:13 Kosmos kernel: ata2: reset failed, giving upJun 21 16:33:13 Kosmos kernel: ata2.00: disable deviceJun 21 16:33:13 Kosmos kernel: ata2: EH completeJun 21 16:33:13 Kosmos kernel: sd 2:0:0:0: [sdb] tag#17 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=124sJun 21 16:33:13 Kosmos kernel: sd 2:0:0:0: [sdb] tag#17 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00Jun 21 16:33:13 Kosmos kernel: I/O error, dev sdb, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0Jun 21 16:33:13 Kosmos kernel: sd 2:0:0:0: [sdb] tag#15 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0sJun 21 16:33:13 Kosmos kernel: sd 2:0:0:0: [sdb] tag#15 CDB: opcode=0x8a 8a 00 00 00 00 00 e9 08 f2 f0 00 00 00 08 00 00Jun 21 16:33:13 Kosmos kernel: I/O error, dev sdb, sector 3909677808 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0Jun 21 16:33:13 Kosmos kernel: I/O error, dev sdb, sector 3909677808 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0Jun 21 16:33:13 Kosmos kernel: sd 2:0:0:0: [sdb] tag#18 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0sJun 21 16:33:13 Kosmos kernel: sd 2:0:0:0: [sdb] tag#18 CDB: opcode=0x8a 8a 00 00 00 00 00 e9 08 f2 f8 00 00 00 08 00 00Jun 21 16:33:13 Kosmos kernel: I/O error, dev sdb, sector 3909677816 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0Jun 21 16:33:13 Kosmos kernel: I/O error, dev sdb, sector 3909677816 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0Jun 21 16:33:14 Kosmos kernel: sd 2:0:0:0: [sdb] tag#19 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0sJun 21 16:33:14 Kosmos kernel: sd 2:0:0:0: [sdb] tag#19 CDB: opcode=0x8a 8a 00 00 00 00 00 00 00 00 40 00 00 00 18 00 00Jun 21 16:33:14 Kosmos kernel: I/O error, dev sdb, sector 64 op 0x1:(WRITE) flags 0x0 phys_seg 3 prio class 0Jun 21 16:33:14 Kosmos kernel: sd 2:0:0:0: [sdb] tag#20 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0sJun 21 16:33:14 Kosmos kernel: sd 2:0:0:0: [sdb] tag#20 CDB: opcode=0x8a 8a 00 00 00 00 00 00 00 00 c0 00 00 00 20 00 00Jun 21 16:33:14 Kosmos kernel: I/O error, dev sdb, sector 192 op 0x1:(WRITE) flags 0x0 phys_seg 4 prio class 0Jun 21 16:35:47 Kosmos kernel: sd 2:0:0:0: [sdb] tag#21 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0sJun 21 16:35:47 Kosmos kernel: sd 2:0:0:0: [sdb] tag#21 CDB: opcode=0x8a 8a 00 00 00 00 00 00 00 3a e8 00 00 00 08 00 00Jun 21 16:35:47 Kosmos kernel: I/O error, dev sdb, sector 15080 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0Jun 21 16:50:48 Kosmos emhttpd: spinning down /dev/sdbJun 21 16:50:48 Kosmos emhttpd: sdspin /dev/sdb down: 5Jun 21 16:50:48 Kosmos kernel: sd 2:0:0:0: [sdb] tag#10 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0sJun 21 16:50:48 Kosmos kernel: sd 2:0:0:0: [sdb] tag#10 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e0 00Jun 21 16:50:48 Kosmos kernel: sd 2:0:0:0: [sdb] tag#12 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0sJun 21 16:50:48 Kosmos kernel: sd 2:0:0:0: [sdb] tag#12 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 94 00I am running out of ideas of what the issue could be. Would anyone be able to shed some insight on the issues?
June 22, 20251 yr That still looks like a power/connection problem, or a controller problem, post the full diags to take another look.
June 22, 20251 yr Author This is the latest diagnostics file. I appreciate the help! kosmos-diagnostics-20250622-1232.zip
June 22, 20251 yr Parity dropped offline, so there's no SMART, but swap both cables with a different disk and try again, if the error follows the disk, that's likely the problem
November 29, 2025Nov 29 Did you ever get this fixed?I am currently experiencing the exact same issues I have also changed the drive itself, psu, sata cable and use a different sata port.I am absolutely at my whits end
November 29, 2025Nov 29 Author Changing one of the drives for a new one fixed my issue. I'd recommend following the advice from @JorgeB above to see if it is an issue with a specific drive or with a sata or power cable.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.