What is problem -- ata1.00: status: { DRDY }

English Hardware
#1

Dear Sir …

I have some problem in below(Suse enterprise 11 64bit)…

logsvr02:/var/log # uname -a
Linux logsvr02 2.6.27.19-5-default #1 SMP 2009-02-28 04:40:21 +0100 x86_64 x86_64 x86_64 GNU/Linux

logsvr02:/var/log # cat warn
Sep 28 03:41:12 logsvr02 kernel: ata1.00: status: { DRDY }
Sep 28 03:41:17 logsvr02 kernel: ata1: link is slow to respond, please be patient (ready=0)
Sep 28 03:41:22 logsvr02 kernel: ata1: device not ready (errno=-16), forcing hardreset
Sep 28 10:20:56 logsvr02 kernel: ata1.00: qc timeout (cmd 0xa0)
Sep 28 10:20:56 logsvr02 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Sep 28 10:20:56 logsvr02 kernel: ata1.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Sep 28 10:20:56 logsvr02 kernel: cdb 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Sep 28 10:20:56 logsvr02 kernel: res 51/20:03:00:00:00/00:00:00:00:00/a0 Emask 0x5 (timeout)
Sep 28 10:20:56 logsvr02 kernel: ata1.00: status: { DRDY ERR }
Sep 28 10:21:01 logsvr02 kernel: ata1: link is slow to respond, please be patient (ready=0)
Sep 28 10:21:06 logsvr02 kernel: ata1: device not ready (errno=-16), forcing hardreset
Sep 28 17:40:45 logsvr02 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Sep 28 17:40:45 logsvr02 kernel: ata1.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Sep 28 17:40:45 logsvr02 kernel: cdb 1e 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Sep 28 17:40:45 logsvr02 kernel: res 40/00:02:00:08:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
Sep 28 17:40:45 logsvr02 kernel: ata1.00: status: { DRDY }
Sep 28 17:40:50 logsvr02 kernel: ata1: link is slow to respond, please be patient (ready=0)
Sep 28 17:40:55 logsvr02 kernel: ata1: device not ready (errno=-16), forcing hardreset
Sep 28 22:13:10 logsvr02 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Sep 28 22:13:10 logsvr02 kernel: ata1.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Sep 28 22:13:10 logsvr02 kernel: cdb 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Sep 28 22:13:10 logsvr02 kernel: res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
Sep 28 22:13:10 logsvr02 kernel: ata1.00: status: { DRDY }
Sep 28 22:13:15 logsvr02 kernel: ata1: link is slow to respond, please be patient (ready=0)
Sep 28 22:13:20 logsvr02 kernel: ata1: device not ready (errno=-16), forcing hardreset
Sep 29 04:17:03 logsvr02 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Sep 29 04:17:03 logsvr02 kernel: ata1.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Sep 29 04:17:03 logsvr02 kernel: cdb 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Sep 29 04:17:03 logsvr02 kernel: res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
Sep 29 04:17:03 logsvr02 kernel: ata1.00: status: { DRDY }
Sep 29 04:17:08 logsvr02 kernel: ata1: link is slow to respond, please be patient (ready=0)
Sep 29 04:17:13 logsvr02 kernel: ata1: device not ready (errno=-16), forcing hardreset

I don’t know how to fix it …

Please help me … Thanks …

Best Regards

#2

If you haven’t fixed this yet, I had the same sort of error messages on a Dell Precision 670 when experimenting with combinations of IDE/ATA & SATA drives.

I found two reasons:

1/ The drive jumpers were set wrong, and in the end I found that setting all drives to Cable Select was the best.

2/ A drive was enabled in BIOS, but not connected (while checking out the jumper settings). Most BIOS have some way to enable/disable drive connections. DELL is very good, and others less so.

I suggest you unplug all drives and see what happens, then plug them back one at a time.

IIRC the entry ata 1.00 means IDE Secondary Master

PS SATA drives normally have no jumpers other than for setting the access speed.

#3

Luckly, I met this too,

Try this as follow, It works fine for me now, :slight_smile:

add kernel command parameter

libata.dma=0

enjoy !