ooknat Posted September 30, 2015 Share Posted September 30, 2015 Hi i was wondering if anyone could help me..... ive been getting this strange error and i don't know what it means "ata11 and ata9" during parity check is this error something to worry about so far ive checked all my sata cables and power cables to make sure they are firmly in i have worked out that ata11 and ata9 are my two western digital hard drives, i have done a short smart check on both drives and both have passed, the two hard drives are attached to a sata expander card pcie on my motherboard. I've removed the card and replaced it back in and made sure it was all clean and secure, my other 6 hard drives are running from motherboard with no errors thanks for any help on this matter ive attached syslog also both smart checks "Sep 30 15:09:51 Tower logger: Updating templates... Updating info... Done. Sep 30 15:22:38 Tower kernel: mdcmd (43): check CORRECT Sep 30 15:22:38 Tower kernel: md: recovery thread woken up ... Sep 30 15:22:38 Tower kernel: md: recovery thread checking parity... Sep 30 15:22:38 Tower kernel: md: using 1536k window, over a total of 2930266532 blocks. Sep 30 16:06:24 Tower emhttp: shcmd (53): /usr/sbin/hdparm -y /dev/sdd &> /dev/null Sep 30 16:10:19 Tower kernel: ata11.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Sep 30 16:10:19 Tower kernel: ata11.00: failed command: IDENTIFY DEVICE Sep 30 16:10:19 Tower kernel: ata11.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 3 pio 512 in Sep 30 16:10:19 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Sep 30 16:10:19 Tower kernel: ata11.00: status: { DRDY } Sep 30 16:10:19 Tower kernel: ata11: hard resetting link Sep 30 16:10:20 Tower kernel: ata11: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Sep 30 16:10:20 Tower kernel: ata11.00: configured for UDMA/133 Sep 30 16:10:20 Tower kernel: ata11: EH complete" tower-syslog-20150930-1622.zip tower-smart-20150930-1634.zip tower-smart-20150930-1636.zip Link to comment
RobJ Posted October 1, 2015 Share Posted October 1, 2015 As you know, the SMART reports are fine. The syslog is short, covers less than an hour, and just shows what you showed above, only a hiccup with Disk 5 on ata11. As you can see, it failed to identify itself, but after a hard reset, continued on as normal. If you aren't seeing parity errors, this appears to be harmless. These are the 2 drives on the 4 port card, so the only thing I can think of is a strange incompatibility between the card and that model of drive. If it is bothering you, you might obtain an inexpensive 2 port SATA card (like an ASM1061 based card) and switch the 2 drives to it. By the way, with recent v6 versions, we prefer the diagnostics zip (Tools -> Diagnostics), as it automatically includes everything you included, plus a LOT more. Its lsscsi report includes the ata numbers, to help you identify the drive, and the lspci report would help identify the 4 port card. Link to comment
ooknat Posted October 1, 2015 Author Share Posted October 1, 2015 thank you for the reply I've attached the Diagnostics log and a longer syslog after Parity-Check, parity check 0 errors tower-diagnostics-20151001-1038.zip tower-syslog-20151001-1046.zip Link to comment
RobJ Posted October 1, 2015 Share Posted October 1, 2015 I don't have time right now, have to work, but a different SATA card would be advised. You could also try swapping SATA ports with 2 other drives, see if problem follows drive or stays with port. Link to comment
ooknat Posted October 1, 2015 Author Share Posted October 1, 2015 thank you for the reply I will try that abit later on Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.