May 13, 201016 yr Has anyone seen this particular error before? I'm seeing this most times I boot up the server now, and sometimes it means that unraid will not start. Other times, like shown in the log below, eventually the link responds and unraid starts. I'm assuming this is a failing HD, but how do identify which one? (I have at least two WDC WD5000AACS-00G8B1 drives) May 13 08:42:59 Tower kernel: ata9: link is slow to respond, please be patient (ready=-19) May 13 08:42:59 Tower kernel: ata9: COMRESET failed (errno=-16) May 13 08:42:59 Tower kernel: ata9: link is slow to respond, please be patient (ready=-19) May 13 08:42:59 Tower kernel: ata9: COMRESET failed (errno=-16) May 13 08:42:59 Tower kernel: ata9: link is slow to respond, please be patient (ready=-19) May 13 08:42:59 Tower kernel: ata9: SATA link up 1.5 Gbps (SStatus 113 SControl 310) May 13 08:42:59 Tower kernel: ata9.00: ATA-8: WDC WD5000AACS-00G8B1, 05.04C05, max UDMA/133 May 13 08:42:59 Tower kernel: ata9.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 0/32) May 13 08:42:59 Tower kernel: ata9.00: configured for UDMA/100
May 13, 201016 yr Has anyone seen this particular error before? I'm seeing this most times I boot up the server now, and sometimes it means that unraid will not start. Other times, like shown in the log below, eventually the link responds and unraid starts. I'm assuming this is a failing HD, but how do identify which one? (I have at least two WDC WD5000AACS-00G8B1 drives) May 13 08:42:59 Tower kernel: ata9: link is slow to respond, please be patient (ready=-19) May 13 08:42:59 Tower kernel: ata9: COMRESET failed (errno=-16) May 13 08:42:59 Tower kernel: ata9: link is slow to respond, please be patient (ready=-19) May 13 08:42:59 Tower kernel: ata9: COMRESET failed (errno=-16) May 13 08:42:59 Tower kernel: ata9: link is slow to respond, please be patient (ready=-19) May 13 08:42:59 Tower kernel: ata9: SATA link up 1.5 Gbps (SStatus 113 SControl 310) May 13 08:42:59 Tower kernel: ata9.00: ATA-8: WDC WD5000AACS-00G8B1, 05.04C05, max UDMA/133 May 13 08:42:59 Tower kernel: ata9.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 0/32) May 13 08:42:59 Tower kernel: ata9.00: configured for UDMA/100 It could just as easily be the cable... If you had posted the full syslog we could tell you which drive. Basically ata9 = scsi 9:0:0:0 (or something like that) so look for the scsi line followed by "sd" lines that have the device name.
Archived
This topic is now archived and is closed to further replies.