Drdy Err 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 drdy err abrt Support AskUbuntu Official Documentation User Documentation Social Media Facebook Twitter Useful Links Distrowatch status drdy err Bugs: Ubuntu PPAs: Ubuntu Web Upd8: Ubuntu OMG! Ubuntu Ubuntu Insights Planet Ubuntu Activity Page Please read before SSO login Advanced ata1 00 status drdy err Search Forum The Ubuntu Forum Community Ubuntu Official Flavours Support Hardware [ubuntu] Hard Drive Error : ata3.00: status: { DRDY ERR } Having an Issue With Posting ? Do you want to help
Status Drdy Err Linux
us debug the posting issues ? < is the place to report 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 status drdy err centos Profile View Forum Posts Private Message Spilled the Beans Join Date Mar 2007 Beans 12 [ SOLVED ] 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): [684
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the ubuntu drdy err workings and policies of this site About Us Learn more about Stack
Ata3.00 Status Drdy Err
Overflow the company Business Learn more about hiring developers or posting ads with us Super User Questions Tags
What Is Drdy
Users Badges Unanswered Ask Question _ Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute: Sign up https://ubuntuforums.org/showthread.php?t=1034762 Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Hard Disk DRDY error: is it a crash up vote 3 down vote favorite 1 I am using IBM Thinkpad, 1.7GHz, 512 RAM with Linux Mint 9 installed. I have two partitions in addition to root. One http://superuser.com/questions/246901/hard-disk-drdy-error-is-it-a-crash of the partitions became read-only yesterday, after which I rebooted my system. It is extremely slow along with DRDY Error : Is my Hard disk crashed ? Error Log while booting. Differences between boot sector and its backup. failed command : READ DMA BMDMA : stat 0X25 ata 1.00 : status : { DRDY ERR } ata 1.00 : status :{ UNC } Buffer I/O error on logical device, logical block 65467 smartctl output for the partition: mint mint # smartctl -a /dev/sda1 smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: TOSHIBA MK4026GAX RoHS Serial Number: X5LY1623T Firmware Version: PA107E User Capacity: 40,007,761,920 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 6 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Thu Feb 17 06:48:25 2011 UTC SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result:
#1 2012-08-23 14:42:19 68flag Member Registered: 2012-08-23 Posts: 4 DRDY ERR I/O Errors only occur with KDE. HDD or kernel related? This isn't too urgent since I'm not https://bbs.archlinux.org/viewtopic.php?id=147546 having this problem anymore, but I would like to know what caused https://www.redhat.com/archives/rhl-devel-list/2008-December/msg02951.html it in the first place.A few months ago, I think it was in May, when I was booting into KDE, the desktop wouldnt load. After logging in it goes to a black screen with a cursor. I check my tty consoles and they are all spammed with DRDY and drdy err I/O errors.Today my log files don't go back to that time, but I apparantly wrote them down:[timestamp] ata1.00: irq_stat 0x40000001[timestamp] ata1: SError: { CommWake }[timestamp] ata1.00: failed command: READ FPDMA QUEUED[timestamp] ata1.00: cmd 60/08:00:79:c5:e9/00:00:38:00:00/40 tag 0 ncq 4096 in[timestamp] res 41/40:08:7c:c5:e9/00:00:38:00:00/60 Emast 0x409 (media error)
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 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 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 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 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 complete ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata1.00: BMDMA stat 0x25 ata1.00: cmd 25/00:00:00: