hypergolic Posted January 1, 2019 Share Posted January 1, 2019 I noticed the parity check that started this morning was running very slow, less than 1MB/s. Looking in syslog I assume this is the cause. How do I identify which disk this is? Thanks! Jan 1 05:59:43 Tower kernel: ata1.00: cmd 25/00:f8:38:99:7c/00:02:03:00:00/e0 tag 3 dma 389120 in Jan 1 05:59:43 Tower kernel: res 50/00:00:37:99:7c/00:00:03:00:00/40 Emask 0x10 (ATA bus error) Jan 1 05:59:43 Tower kernel: ata1.00: status: { DRDY } Jan 1 05:59:43 Tower kernel: ata1: hard resetting link Jan 1 05:59:48 Tower kernel: ata1: link is slow to respond, please be patient (ready=0) Jan 1 05:59:53 Tower kernel: ata1: COMRESET failed (errno=-16) Jan 1 05:59:53 Tower kernel: ata1: hard resetting link Jan 1 05:59:53 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jan 1 05:59:55 Tower kernel: ata1.00: configured for UDMA/33 Jan 1 05:59:55 Tower kernel: ata1: EH complete Jan 1 05:59:55 Tower kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x4890000 action 0xe frozen Jan 1 05:59:55 Tower kernel: ata1.00: irq_stat 0x0c400040, interface fatal error, connection status changed Jan 1 05:59:55 Tower kernel: ata1: SError: { PHYRdyChg 10B8B LinkSeq DevExch } Jan 1 05:59:55 Tower kernel: ata1.00: failed command: READ DMA EXT Jan 1 05:59:55 Tower kernel: ata1.00: cmd 25/00:d8:c8:e2:7c/00:02:03:00:00/e0 tag 6 dma 372736 in Jan 1 05:59:55 Tower kernel: res 50/00:00:c7:e2:7c/00:00:03:00:00/40 Emask 0x10 (ATA bus error) Jan 1 05:59:55 Tower kernel: ata1.00: status: { DRDY } Jan 1 05:59:55 Tower kernel: ata1: hard resetting link Jan 1 06:00:01 Tower kernel: ata1: link is slow to respond, please be patient (ready=0) Jan 1 06:00:05 Tower kernel: ata1: COMRESET failed (errno=-16) Jan 1 06:00:05 Tower kernel: ata1: hard resetting link Jan 1 06:00:05 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jan 1 06:00:07 Tower kernel: ata1.00: configured for UDMA/33 Jan 1 06:00:07 Tower kernel: ata1: EH complete Jan 1 06:00:07 Tower kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x4890000 action 0xe frozen Jan 1 06:00:07 Tower kernel: ata1.00: irq_stat 0x0c400040, interface fatal error, connection status changed Jan 1 06:00:07 Tower kernel: ata1: SError: { PHYRdyChg 10B8B LinkSeq DevExch } Jan 1 06:00:07 Tower kernel: ata1.00: failed command: READ DMA EXT Jan 1 06:00:07 Tower kernel: ata1.00: cmd 25/00:40:b0:14:7d/00:05:03:00:00/e0 tag 12 dma 688128 in Jan 1 06:00:07 Tower kernel: res 50/00:00:af:14:7d/00:00:03:00:00/40 Emask 0x10 (ATA bus error) Jan 1 06:00:07 Tower kernel: ata1.00: status: { DRDY } Jan 1 06:00:07 Tower kernel: ata1: hard resetting link Jan 1 06:00:13 Tower kernel: ata1: link is slow to respond, please be patient (ready=0) Jan 1 06:00:17 Tower kernel: ata1: COMRESET failed (errno=-16) Jan 1 06:00:17 Tower kernel: ata1: hard resetting link Jan 1 06:00:18 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jan 1 06:00:19 Tower kernel: ata1.00: configured for UDMA/33 Jan 1 06:00:19 Tower kernel: ata1: EH complete Jan 1 06:00:19 Tower kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x4890000 action 0xe frozen Jan 1 06:00:19 Tower kernel: ata1.00: irq_stat 0x0c400040, interface fatal error, connection status changed Jan 1 06:00:19 Tower kernel: ata1: SError: { PHYRdyChg 10B8B LinkSeq DevExch } Jan 1 06:00:19 Tower kernel: ata1.00: failed command: READ DMA EXT Jan 1 06:00:19 Tower kernel: ata1.00: cmd 25/00:40:20:58:7d/00:05:03:00:00/e0 tag 13 dma 688128 in Jan 1 06:00:19 Tower kernel: res 50/00:00:1f:58:7d/00:00:03:00:00/40 Emask 0x10 (ATA bus error) Link to comment
JorgeB Posted January 1, 2019 Share Posted January 1, 2019 Please post the diagnostics: Tools -> Diagnostics Link to comment
hypergolic Posted January 1, 2019 Author Share Posted January 1, 2019 Here ya go! tower-diagnostics-20190101-0656.zip Link to comment
bonienl Posted January 1, 2019 Share Posted January 1, 2019 You can also click on the disk icon of each device on the Main page. It opens a window with messages related to that device. Link to comment
JorgeB Posted January 1, 2019 Share Posted January 1, 2019 ATA1 is disk3, there are also a lot of errors for ATA8 (disk4), check/replace cables for both. Link to comment
hypergolic Posted January 1, 2019 Author Share Posted January 1, 2019 Thanks for the help! Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.