openSUSE Forums > Hardware > 64-bit » What is problem -- ata1.00: status: { DRDY }

Go Back   openSUSE Forums > Hardware > 64-bit
Forums FAQ Members List Search Today's Posts Mark Forums Read


64-bit Questions specific to 64 -bit hardware (Software questions should be posted in the appropriate software forums)

Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 29-Sep-2009, 00:53
Puzzled Penguin
 
Join Date: Sep 2009
Posts: 1
Archangelwu hasn't been rated much yet
Default What is problem -- ata1.00: status: { DRDY }

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
Reply With Quote
  #2 (permalink)  
Old 17-Oct-2009, 07:33
sid1950's Avatar
Puzzled Penguin
 
Join Date: Jun 2008
Location: London, UK
Posts: 23
sid1950 hasn't been rated much yet
Default Re: What is problem -- ata1.00: status: { DRDY }

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.
__________________
Best wishes

Sid
Registered Linux user #432874
Reply With Quote
Reply

Bookmarks


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On




 

Search Engine Friendly URLs by vBSEO 3.3.0 RC2