Ata Drdy Error Unc
Contents |
Get Kubuntu Get Xubuntu Get Lubuntu Get UbuntuStudio Get Mythbuntu Get Edubuntu Get Ubuntu-GNOME Get UbuntuKylin Ubuntu Code of Conduct Ubuntu Wiki Community Wiki Other Support Launchpad Answers Ubuntu IRC Support AskUbuntu Official Documentation User Documentation what is drdy Social Media Facebook Twitter Useful Links Distrowatch Bugs: Ubuntu PPAs: Ubuntu Web Upd8: Ubuntu drdy error ubuntu boot OMG! Ubuntu Ubuntu Insights Planet Ubuntu Activity Page Please read before SSO login Advanced Search Forum The Ubuntu Forum Community Ubuntu Official status drdy err centos Flavours Support Hardware [ubuntu] Hard Drive Error : ata3.00: status: { DRDY ERR } Having an Issue With Posting ? Do you want to help us debug the posting issues ? < is the place to report ata1 00 status drdy it, thanks ! Page 1 of 3 123 Last Jump to page: Results 1 to 10 of 29 Thread: Hard Drive Error : ata3.00: status: { DRDY ERR } Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode January 9th, 2009 #1 hobong View Profile View Forum Posts Private Message Spilled the Beans Join Date Mar 2007 Beans 12 [ SOLVED ]
Status Drdy Err Linux
Hard Drive Error : ata3.00: status: { DRDY ERR } Hi all I have problem with my System the log always spam with these messages : Code: .......... 68489.756311] ata3.00: status: { DRDY ERR } [68489.756314] ata3.00: error: { UNC } [68489.951583] ata3.00: configured for UDMA/133 [68489.951604] ata3: EH complete [68492.671124] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 [68492.671133] ata3.00: BMDMA stat 0x24 [68492.671140] ata3.00: cmd c8/00:08:55:e8:8d/00:00:00:00:00/e2 tag 0 dma 4096 in [68492.671142] res 51/40:00:56:e8:8d/00:00:00:00:00/02 Emask 0x9 (media error) [68492.671145] ata3.00: status: { DRDY ERR } [68492.671148] ata3.00: error: { UNC } [68492.899657] ata3.00: configured for UDMA/133 [68492.899678] ata3: EH complete [68495.610841] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 [68495.610851] ata3.00: BMDMA stat 0x24 [68495.610857] ata3.00: cmd c8/00:08:55:e8:8d/00:00:00:00:00/e2 tag 0 dma 4096 in [68495.610859] res 51/40:00:56:e8:8d/00:00:00:00:00/02 Emask 0x9 (media error) [68495.610863] ata3.00: status: { DRDY ERR } [68495.610865] ata3.00: error: { UNC } [68495.799599] ata3.00: configured for UDMA/133 [68495.799620] sd 2:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK [68495.799626] sd 2:0:0:0: [sda] Sense Key : Medium Error [current] [descriptor] [68495.799631] Descriptor sense data with sense descriptors (in hex): [68495.799633] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 [68495.799643] 02 8d e8 56 [68495.799647] sd 2:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed [6849
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
Status Drdy Err Error Abrt
Super User Questions Tags Users Badges Unanswered Ask Question _ Super User is a question and answer drdy err abrt site for computer enthusiasts and power users. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody options libata noacpi=1 can answer The best answers are voted up and rise to the top DRDY ERR from 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: https://ubuntuforums.org/showthread.php?t=1034762 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: 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. http://superuser.com/questions/796423/drdy-err-from-hdd 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.) /dev/sda6 ext4 94GB # DATA unallocated _ 1MB I have installed linuxes one after another and actually wanted to install Grub in /dev/sda2 and chainload Linux 1 & 2, but before I could do it, I hit this snag! Any ideas? Solutions? [UPDATE 2] Title of the problem is no longer applicable * I booted from USB and did a 'fsck' on all partitions. All (except /sda5) were reported clean. /dev/sda5 reported many errors (probably around a couple of
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 is going to be https://www.redhat.com/archives/rhl-devel-list/2008-December/msg02951.html spammy, I think it is important to document this 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 failing as of about 3-4 http://www.linux.org.ru/forum/linux-hardware/3467021 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 like 20 minutes. Same thing two previous failed drdy err 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 errors are turning up in user space. The WinXP partition seems status drdy err 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/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 com
активность винта, странные звуки из него, через несколько минут прошло. dmesg выдал: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x80000 action 0x0 ata5.00: BMDMA stat 0x25 ata5: SError: { 10B8B } ata5.00: cmd c8/00:18:bf:9a:e6/00:00:00:00:00/e0 tag 0 dma 12288 in res 51/40:03:d4:9a:e6/00:00:00:00:00/e0 Emask 0x9 (media error) ata5.00: status: { DRDY ERR } ata5.00: error: { UNC } ata5.00: configured for UDMA/133 ata5: EH complete ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x80000 action 0x0 ata5.00: BMDMA stat 0x25 ata5: SError: { 10B8B } ata5.00: cmd c8/00:18:bf:9a:e6/00:00:00:00:00/e0 tag 0 dma 12288 in res 51/40:03:d4:9a:e6/00:00:00:00:00/e0 Emask 0x9 (media error) ata5.00: status: { DRDY ERR } ata5.00: error: { UNC } ata5.00: configured for UDMA/133 ata5: EH complete ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x80000 action 0x0 ata5.00: BMDMA stat 0x25 ata5: SError: { 10B8B } ata5.00: cmd c8/00:18:bf:9a:e6/00:00:00:00:00/e0 tag 0 dma 12288 in res 51/40:03:d4:9a:e6/00:00:00:00:00/e0 Emask 0x9 (media error) ata5.00: status: { DRDY ERR } ata5.00: error: { UNC } ata5.00: configured for UDMA/133 ata5: EH complete ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x80000 action 0x0 ata5.00: BMDMA stat 0x25 ata5: SError: { 10B8B } ata5.00: cmd c8/00:18:bf:9a:e6/00:00:00:00:00/e0 tag 0 dma 12288 in res 51/40:03:d4:9a:e6/00:00:00:00:00/e0 Emask 0x9 (media error) ata5.00: status: { DRDY ERR } ata5.00: error: { UNC } ata5.00: configured for UDMA/133 ata5: EH complete ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x80000 action 0x0 ata5.00: BMDMA stat 0x25 ata5: SError: { 10B8B } ata5.00: cmd c8/00:18:bf:9a:e6/00:00:00:00:00/e0 tag 0 dma 12288 in res 51/40:03:d4:9a:e6/00:00:00:00:00/e0 Emask 0x9 (media error) ata5.00: status: { DRDY ERR } ata5.00: error: { UNC } ata5.00: configured for UDMA/133 ata5: EH complete ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x80000 action 0x0 ata5.00: BMDMA stat 0x25 ata5: SError: { 10B8B } ata5.00: cmd c8/00:18:bf:9a:e6/00:00:00:00:00/e0 tag 0 dma 12288 in res 51/40:03:d4:9a:e6/00:00:00: