Ata1.00 Drdy Error Unc
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow drdy err unc the company Business Learn more about hiring developers or posting ads with us Super
What Is Drdy
User Questions Tags Users Badges Unanswered Ask Question _ Super User is a question and answer site for computer enthusiasts and power status drdy err linux users. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top DRDY ERR from drdy error ubuntu boot HDD up vote 2 down vote favorite All of a sudden I started getting the DRDY ERR with my laptop running linux..some messages look like.. ata1:00: status: { DRDY ERR } ata1.00: error {UNC } ata1:00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata1:00: BMDMA stat 0x25 ata1:00: failed command: READ DMA finally it drops me into a command prompt asking me to enter a run level and after that INIT:
Status Drdy Err Centos
no more processes left in this runlevel Suspecting a HDD crash, I took it out and used in another PC as an external USB HDD drive and I was able to mount & see all partitions and files within. So I assume Disc is OK. [EDIT/UPDATE] I'm also able to boot into the laptop from a USB pen drive with linux) and even able to see all the partitions on the disk and access them. Also took out the HDD and put it in a external casing and tried booting into the same laptop but got following different errors end_request: critical target error, dev sda, sector 32839936 EXT4_fs error: (device sda5): ext4_find_entry:935: inode #393217: comm init: reading directory lblock 0 INIT: No inittab file found Enter runlevel: So I guess, the HDD is accesible as a storage, but not bootable. The partitioning scheme on that HDD is as under if that'd help.. (GPT scheme) partition FileSystem size flags --------- ----------- ---- ----- /dev/sda1 unknown 2.00MB bios_grub /dev/sda2 ext2 128MB # was supposed to be common boot partition for chain loading /dev/sda3 swap 1.5GB /dev/sda4 ext4 8GB # Linux 1 (somehow, Grub does not show this in the menu, cannot boot into) /dev/sda5 ext4 8GB # Linux 2 (I could only boot into this one from Grub.) /de
disk failure Date: Tue, 30 Dec 2008 19:21:26 -0600 Now one occurrence doesn't prove it was the Load_Cycle_Count problem that killed the drive, but this drive is definitely prematurely failed. This drdy err abrt is going to be spammy, I think it is important to document this ata1.00 failed command read dma so we can all learn from it... The drive I posted about a while back: https://www.redhat.com/archives/fedora-devel-list/2008-July/msg00426.html Is now definitely
Options Libata Noacpi=1
failing as of about 3-4 weeks ago. It's at the stage where the drive still seems to be mostly readable, but IO bandwidth has dropped like a rock. Booting Fedora takes http://superuser.com/questions/796423/drdy-err-from-hdd like 20 minutes. Same thing two previous failed drives did. The drive has a manufacture date of May 2007. I have no reason to believe the drive has been mistreated, no more than typical laptop wear and tear. It is a "desktop replacement" laptop and is rarely transported. Fortunately /home seems to be readable. Media errors show up in the syslog, but no IO https://www.redhat.com/archives/rhl-devel-list/2008-December/msg02951.html errors are turning up in user space. The WinXP partition seems to be trashed, however. So much for my wife's Half Life 2 and Spore savegames... ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata1.00: BMDMA stat 0x25 ata1.00: cmd 25/00:00:00:58:08/00:04:00:00:00/e0 tag 0 dma 524288 in res 51/40:0f:f1:59:08/40:02:00:00:00/e0 Emask 0x9 (media error) ata1.00: status: { DRDY ERR } ata1.00: error: { UNC } ata1.00: configured for UDMA/100 ata1: EH complete ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata1.00: BMDMA stat 0x25 ata1.00: cmd 25/00:00:00:58:08/00:04:00:00:00/e0 tag 0 dma 524288 in res 51/40:0f:f1:59:08/40:02:00:00:00/e0 Emask 0x9 (media error) ata1.00: status: { DRDY ERR } ata1.00: error: { UNC } ata1.00: configured for UDMA/100 ata1: EH complete ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata1.00: BMDMA stat 0x25 ata1.00: cmd 25/00:00:00:58:08/00:04:00:00:00/e0 tag 0 dma 524288 in res 51/40:0f:f1:59:08/40:02:00:00:00/e0 Emask 0x9 (media error) ata1.00: status: { DRDY ERR } ata1.00: error: { UNC } ata1.00: configured for UDMA/100 ata1: EH complete ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata1.00: BMDMA stat 0x25 ata1.00: cmd 25/00:00:00:58:08/00:04:00:00:00/e0 tag 0 dma 524288 in res 51/4
communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us http://askubuntu.com/questions/321277/how-do-i-recover-from-a-read-dma-bootup-error Learn more about Stack Overflow the company Business Learn more about hiring developers http://serverfault.com/questions/152855/sata-hdd-errors or posting ads with us Ask Ubuntu Questions Tags Users Badges Unanswered Ask Question _ Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up drdy err and rise to the top How do I recover from a read DMA bootup error? up vote 4 down vote favorite 3 I am running 12.04 LTS, and almost every time I shut down my system, my root fails to mount on the next bootup, usually after an update. In this particular case, I can see my filesystem when running on live CD, but every time I boot, I status drdy err see the following sequence of messages cycle in an endless loop (process IDs removed): ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata1.00: BMDMA stat 0x24 ata1.00: failed command: READ DMA ata1.00: cmd c8/00:08:b0:f7:46/00:00:00:00:00/e0 res 51/40:08:b0:f7:46/40:02:02:00:00/e0 Emask 0x9 (media error) ata1.00: status:{DRDY ERR} ata1.00:error:{UNC} end_request: I/O error, dev sda, sector 4650928 I boot off of a relatively new 60GB solid state disk drive, and in the past when I have run into this issue, I use fsck to detect and fix errors. But fsck runs clean on my partition, so i am uncertain how to approach the problem. 12.04 boot share|improve this question asked Jul 17 '13 at 20:46 txmystic 113239 possible duplicate of how to interpret these errors from syslog –Eliah Kagan Sep 9 '14 at 21:55 add a comment| 3 Answers 3 active oldest votes up vote 3 down vote accepted There was an Input Output error at your Hard Disk sda part, at sector 4650928. You can boot from Ubuntu Live cd/dvd/usb, start Disks Utility, try to see the SMART data and test your sda disk. Possible duplicate share|improve this answer answered Jul 17 '13 at 22:20 ubuntu_tr 64536 Disk utility claims the disk is
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top SATA hdd errors up vote 0 down vote favorite I have one server with WDC WD3202ABYS ... There are 100 virtual hosts. Server is working about 5 years and in this time period I have change 4 disks. All with same reason: sata error. The last one: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata2.00: BMDMA stat 0x5 ata2.00: cmd 35/00:60:57:7b:b6/00:01:06:00:00/e0 tag 0 dma 180224 out res 51/10:60:57:7b:b6/10:01:06:00:00/e0 Emask 0x81 (invalid argument) ata2.00: status: { DRDY ERR } ata2.00: error: { IDNF } ata2.00: configured for UDMA/133 sd 1:0:0:0: SCSI error: return code = 0x08000002 sdb: Current [descriptor]: sense key: Aborted Command Add. Sense: Recorded entity not found Descriptor sense data with sense descriptors (in hex): 72 0b 14 00 00 00 00 0c 00 0a 80 00 00 00 00 00 06 b6 7b 57 end_request: I/O error, dev sdb, sector 112622423 Buffer I/O error on device dm-8, logical block 14077747 lost page write due to I/O error on dm-8 Buffer I/O error on device dm-8, logical block 14077748 lost page write due to I/O error on dm-8 Buffer I/O error on device dm-8, logical block 14077749 lost page write due to I/O error on dm-8 Buffer I/O error on device dm-8, logical block 14077750 lost page write due to I/O error on dm-8 Buffer I/O error on device dm-8, logical block 14077751 lost page write due to I/O error on dm-8 Buffer I/O error on device dm-8, logical block 14077756 lost page write due to I/O error on dm-8 ata2: EH complete SCSI device sdb: 625142448 512-byte hdwr sectors (320073 MB) sdb: Write Protect is off sdb: Mode Sense: 00 3a 00 00 SCSI device sdb: drive cache: write back ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata2.00: BMDMA stat 0x5 ata2.00: cmd 35/00:90:17:30:b7/00:02:08:00:00/e0 tag 0 dma 335872 out res 51/10:90:17:30:b7/10:02:08:00:00/e0 Emask 0x81 (invalid