LinuxQuestions.org
Visit the LQ Articles and Editorials section
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices



Reply
 
Search this Thread
Old 06-01-2012, 01:30 PM   #1
DJ Shaji
Member
 
Registered: Dec 2004
Location: India
Distribution: Debian Squeeze, Fedora 17
Posts: 440
Blog Entries: 15

Rep: Reputation: 80
Unhappy IDE error: ata1.00: failed command: READ DMA


So, all of a sudden, since last week, I've started getting the following error when I boot up:

Code:
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x64
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:88:f6:01/00:00:00:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:8f:f6:01/00:00:00:00:00/e0 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/33
ata1.01: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x65
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:88:f6:01/00:00:00:00:00/e0 tag 0 dma 4096 in
         res 51/40:04:8c:f6:01/00:00:00:00:00/e0 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/33
ata1.01: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x65
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:88:f6:01/00:00:00:00:00/e0 tag 0 dma 4096 in
         res 51/40:04:8c:f6:01/00:00:00:00:00/e0 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/33
ata1.01: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x65
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:88:f6:01/00:00:00:00:00/e0 tag 0 dma 4096 in
         res 51/40:04:8c:f6:01/00:00:00:00:00/e0 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/33
ata1.01: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x65
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:88:f6:01/00:00:00:00:00/e0 tag 0 dma 4096 in
         res 51/40:04:8c:f6:01/00:00:00:00:00/e0 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/33
ata1.01: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x65
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:88:f6:01/00:00:00:00:00/e0 tag 0 dma 4096 in
         res 51/40:04:8c:f6:01/00:00:00:00:00/e0 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/33
ata1.01: configured for UDMA/33
sd 0:0:0:0: [sda] Unhandled sense code
sd 0:0:0:0: [sda]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sd 0:0:0:0: [sda]  Sense Key : Medium Error [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
        72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 
        00 01 f6 8c 
sd 0:0:0:0: [sda]  Add. Sense: Unrecovered read error - auto reallocate failed
sd 0:0:0:0: [sda] CDB: Read(10): 28 00 00 01 f6 88 00 00 08 00
end_request: I/O error, dev sda, sector 128652
Buffer I/O error on device sda1, logical block 132
Buffer I/O error on device sda1, logical block 133
Buffer I/O error on device sda1, logical block 134
Buffer I/O error on device sda1, logical block 135
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x65
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:04:8c:f6:01/00:00:00:00:00/e0 tag 0 dma 2048 in
         res 51/40:03:8d:f6:01/00:00:00:00:00/e0 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/33
ata1.01: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x65
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:04:8c:f6:01/00:00:00:00:00/e0 tag 0 dma 2048 in
         res 51/40:03:8d:f6:01/00:00:00:00:00/e0 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/33
ata1.01: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x65
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:04:8c:f6:01/00:00:00:00:00/e0 tag 0 dma 2048 in
         res 51/40:03:8d:f6:01/00:00:00:00:00/e0 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/33
ata1.01: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x65
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:04:8c:f6:01/00:00:00:00:00/e0 tag 0 dma 2048 in
         res 51/40:03:8d:f6:01/00:00:00:00:00/e0 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/33
ata1.01: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x65
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:04:8c:f6:01/00:00:00:00:00/e0 tag 0 dma 2048 in
         res 51/40:03:8d:f6:01/00:00:00:00:00/e0 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/33
ata1.01: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x65
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:04:8c:f6:01/00:00:00:00:00/e0 tag 0 dma 2048 in
         res 51/40:03:8d:f6:01/00:00:00:00:00/e0 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/33
ata1.01: configured for UDMA/33
sd 0:0:0:0: [sda] Unhandled sense code
sd 0:0:0:0: [sda]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sd 0:0:0:0: [sda]  Sense Key : Medium Error [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
        72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 
        00 01 f6 8d 
sd 0:0:0:0: [sda]  Add. Sense: Unrecovered read error - auto reallocate failed
sd 0:0:0:0: [sda] CDB: Read(10): 28 00 00 01 f6 8c 00 00 04 00
end_request: I/O error, dev sda, sector 128653
Buffer I/O error on device sda1, logical block 133
Buffer I/O error on device sda1, logical block 134
Buffer I/O error on device sda1, logical block 135
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x64
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:08:f7:01/00:00:00:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:0f:f7:01/00:00:00:00:00/e0 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/33
ata1.01: configured for UDMA/33
ata1: EH complete
Boot up takes more time than before. Now,
  1. This system is 12 years old
  2. I've been having a lot of power outages recently and have no UPS

I checked the drive's S.M.A.R.T status with the palimpset utility, and it shows just one bad sector, which has been around for quite a while now (I keep checking periodically).

So, is the drive going to fail soon? Has it failed already? The partitions on this drive seem to be okay, and I can access data on it fine, although it's 40GB and I haven't checked every single file, so it is possible there might be issues there.

Right now, my primary concern is the error (warning?) and the slightly longer boot up time.
 
Old 06-02-2012, 03:31 AM   #2
hua
Member
 
Registered: Oct 2006
Location: Slovak Republic
Distribution: Slackware 13.37, 14.0
Posts: 396

Rep: Reputation: 49
Quote:
Originally Posted by DJ Shaji View Post
So, is the drive going to fail soon? Has it failed already?
Yes it failed already. Actually each time you see "ata1.00: failed command: READ DMA" it actually fails. After this the system tries to bring the drive back. In your case it is still sometimes successful but at one point it won't come back.
So yes replace it as soon as possible.
You can also make sure that the hard-drive is wrong (and not something else) by trying to boot with another drive on the same port and check weather the error persists. I personally used the Backtrack5 live DVD for this.

Last edited by hua; 06-02-2012 at 03:32 AM.
 
  


Reply

Tags
boot up, dma, failure, harddrive, warning


Thread Tools Search this Thread
Search this Thread:

Advanced Search

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 Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
ata1:SRST Failed errorno=-16 venky6 Linux - Newbie 2 04-02-2012 05:46 AM
HDD SATA problems : failed command : READ DMA Dillinger86 Linux - Newbie 4 02-18-2012 10:52 PM
failed command: read dma (status: { DRDY DF ERR }) G00fy Linux - Hardware 2 01-21-2012 07:01 PM
HDD SATA problems : failed command : READ DMA (EXT) gomines Linux - Hardware 1 10-02-2011 11:01 AM
IDE hard disk DMA error at boot up. patufet99 Linux - Hardware 3 11-25-2007 11:13 PM


All times are GMT -5. The time now is 10:56 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration