I'm running the following kernel on 13.1 3.12.0-34.ge8fa6b4-desktop #1 SMP PREEMPT Mon Nov 4 13:06:33 UTC 2013 (e8fa6b4) x86_64 x86_64 x86_64 GNU/Linux And seeming the following message in dmesg with depressing regularity: [45080.377905] ata2.00: exception Emask n SAct 0x20 SErr 0x0 action 0x6 frozen [45080.377911] ata2.00: failed command: READ FPDMA QUEUED [45080.377917] ata2.00: cmd 60/01:28:00:2a:d4/00:00:4c:00:00/40 tag 5 ncq 512 in res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [45080.377920] ata2.00: status: { DRDY } [45080.377924] ata2: hard resetting link [45085.734173] ata2: link is slow to respond, please be patient (ready=0) [45090.428230] ata2: COMRESET failed (errno=-16) [45090.428236] ata2: hard resetting link [45095.784590] ata2: link is slow to respond, please be patient (ready=0) My question is do I have a bad disk, cable, motherboard or what might it be and how do I test? -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
El 10/08/14 a las #4, Bruce Ferrell escribió:
I'm running the following kernel on 13.1
3.12.0-34.ge8fa6b4-desktop #1 SMP PREEMPT Mon Nov 4 13:06:33 UTC 2013 (e8fa6b4) x86_64 x86_64 x86_64 GNU/Linux
And seeming the following message in dmesg with depressing regularity:
[45080.377905] ata2.00: exception Emask n SAct 0x20 SErr 0x0 action 0x6 frozen [45080.377911] ata2.00: failed command: READ FPDMA QUEUED [45080.377917] ata2.00: cmd 60/01:28:00:2a:d4/00:00:4c:00:00/40 tag 5 ncq 512 in res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [45080.377920] ata2.00: status: { DRDY } [45080.377924] ata2: hard resetting link [45085.734173] ata2: link is slow to respond, please be patient (ready=0) [45090.428230] ata2: COMRESET failed (errno=-16) [45090.428236] ata2: hard resetting link [45095.784590] ata2: link is slow to respond, please be patient (ready=0)
My question is do I have a bad disk, cable, motherboard or what might it be and how do I test?
what does the drive's SMART information says? run a long test and see if there is any error. -- Cristian "I don't know the key to success, but the key to failure is trying to please everybody." -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On 08/10/2014 09:42 AM, Bruce Ferrell wrote:
I'm running the following kernel on 13.1
3.12.0-34.ge8fa6b4-desktop #1 SMP PREEMPT Mon Nov 4 13:06:33 UTC 2013 (e8fa6b4) x86_64 x86_64 x86_64 GNU/Linux
And seeming the following message in dmesg with depressing regularity:
[45080.377905] ata2.00: exception Emask n SAct 0x20 SErr 0x0 action 0x6 frozen [45080.377911] ata2.00: failed command: READ FPDMA QUEUED [45080.377917] ata2.00: cmd 60/01:28:00:2a:d4/00:00:4c:00:00/40 tag 5 ncq 512 in res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [45080.377920] ata2.00: status: { DRDY } [45080.377924] ata2: hard resetting link [45085.734173] ata2: link is slow to respond, please be patient (ready=0) [45090.428230] ata2: COMRESET failed (errno=-16) [45090.428236] ata2: hard resetting link [45095.784590] ata2: link is slow to respond, please be patient (ready=0)
My question is do I have a bad disk, cable, motherboard or what might it be and how do I test?
It is not a kernel problem - as you guessed, it is hardware. Those kinds of errors are not usually coming from the heads and platter assembly, but from the communication between the controller and the disk. If you are lucky, reseating or replacing the cable will cure the problem. In any case, running the long test with smartctl would be a good thing to do. Assuming that your disk is /dev/sda, use smartctl -t long /dev/sda After waiting for the test to complete, you can see the results with smartctl -a /dev/sda Larry -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On 2014-08-10 10:59 (GMT-0500) Larry Finger composed:
[45090.428236] ata2: hard resetting link [45095.784590] ata2: link is slow to respond, please be patient (ready=0)
My question is do I have a bad disk, cable, motherboard or what might it be and how do I test?
It is not a kernel problem - as you guessed, it is hardware. Those kinds of errors are not usually coming from the heads and platter assembly, but from the communication between the controller and the disk. If you are lucky, reseating or replacing the cable will cure the problem.
Such errors show up on tty10 on all my systems with SATA cards in PCI slots any time any of many different eSATA disks and cases or adapters and differing cables get connected, e.g.: 04:00.0 SATA controller: Silicon Image, Inc. SiI 3512 [SATALink/SATARaid] Serial ATA Controller (rev 01)
In any case, running the long test with smartctl would be a good thing to do. Assuming that your disk is /dev/sda, use
smartctl -t long /dev/sda
After waiting for the test to complete, you can see the results with
smartctl -a /dev/sda -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
My question is do I have a bad disk, cable, motherboard or what might it be and how do I test? Basic testing included having some known good spare, like another cable and disk.. Even if you have 2 disks, you can try switching cables and see it the
Bruce Ferrell wrote: problem follows the disk or the cable. If you don't have a spare HD to try, then options are more limited (i.e. -- options others have suggested ... test via SW)... -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On August 10, 2014 10:42:34 AM EDT, Bruce Ferrell
I'm running the following kernel on 13.1
3.12.0-34.ge8fa6b4-desktop #1 SMP PREEMPT Mon Nov 4 13:06:33 UTC 2013 (e8fa6b4) x86_64 x86_64 x86_64 GNU/Linux
And seeming the following message in dmesg with depressing regularity:
[45080.377905] ata2.00: exception Emask n SAct 0x20 SErr 0x0 action 0x6 frozen [45080.377911] ata2.00: failed command: READ FPDMA QUEUED [45080.377917] ata2.00: cmd 60/01:28:00:2a:d4/00:00:4c:00:00/40 tag 5 ncq 512 in res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [45080.377920] ata2.00: status: { DRDY } [45080.377924] ata2: hard resetting link [45085.734173] ata2: link is slow to respond, please be patient (ready=0) [45090.428230] ata2: COMRESET failed (errno=-16) [45090.428236] ata2: hard resetting link [45095.784590] ata2: link is slow to respond, please be patient (ready=0)
My question is do I have a bad disk, cable, motherboard or what might it be and how do I test?
I'll give 2 to one odds that its a bad cable. I've seen it numerous times and those errors look very familiar. Greg -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
participants (6)
-
Bruce Ferrell -
Cristian Rodríguez -
Felix Miata -
Greg Freemyer -
Larry Finger -
Linda Walsh