4

I am receiving a lot of these messages. Is my HD going to die tomorrow morning?

ata1: link is slow to respond, please be patient (ready=0)
ata1: device not ready (errno=-16), forcing hardreset
ata1: soft resetting link
ata1: clearing spurious IRQ
ata1: clearing spurious IRQ
ata1: clearing spurious IRQ
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: qc timeout (cmd 0xa0)
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
         cdb 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
         res 51/20:03:00:00:00/00:00:00:00:00/a0 Emask 0x5 (timeout)
Improve this question
4
  • Your drive is already close to dead. I hope you have good backups, because it is a bit late now to do much about it.
    – Jonathan Leffler
    Mar 23, 2010 at 11:37
  • Yeah this definitely a terminally ill drive. Grab your data while you still can.
    – Tyler McHenry
    Mar 23, 2010 at 11:40
  • possible duplicate (at least, similar symptom): superuser.com/questions/121391/…
    – quack quixote
    Apr 3, 2010 at 20:39
  • Try to replace hdd cable, sometimes it helps
    – Alex
    Jul 19, 2018 at 14:28

3 Answers 3

Reset to default
2

I also wanted to add, there is an official Ubuntu bug located at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/530649

(Edit: fixed broken link)

Improve this answer
1

The problem could be related to the SATA chipset ?

SATA drives or chipset throwing DRDY ERR and ICRC ABRT

Improve this answer
-1

My 2 WD800JD's had a similar Exception...Emask...0x6...frozen issue. During kernel compilation it would happen maybe 20 times. After adding "libata.force=noncq,norst" parameter the errors seem to be gone

Improve this answer

You must log in to answer this question.