Ata Drdy Error
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 the company Business ata drdy err Learn more about hiring developers or posting ads with us Super User Questions Tags Users Badges
Ata Status Drdy
Unanswered Ask Question _ Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes drdy error ubuntu boot 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 Hard Disk DRDY error: is it a crash up vote 3
What Is Drdy
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 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 } error: { unc } 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: PASSED General SMART Values: Offline data collection status: (0x84) Offline data collection activity was suspended by an interrupting command from host. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 153) seconds. Offline data collection capabilities: (0x1b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. No Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Support
#1 2014-05-20 16:07:22 Dornith Member Registered: 2013-02-19 Posts: 63 How do I/Do I need to fix "ata#.00 status { DRDY }" error? I've got an old server that used to
Status Drdy Err Centos
be running windows that I have received to set up with linux for
Ata1 00 Status Drdy
myself. As I was working with it, I remembered that I had an old computer that I was just going status drdy err linux to trash/give away anyways, of which many components would be better. I have since set up a computer that's a mash of components between the two and everything seems to run perfectly http://superuser.com/questions/246901/hard-disk-drdy-error-is-it-a-crash except for one problem: I keep getting this error: (Where "#" is either 2, 3, or 4)ata#.00: exception Emask 0x50 SAct 0x0 SErr 0x48900 action 0x6 frozen ata#: SError: {UnrecovData HostInt 10B8B Handshk } ata#.00: failed command WRITE DMA ata#.00: cmd ca/00:88:9f:ca:8d/00:00:00:00:00/e8 tag 0 dma 69632 out res 50/00:88:9f:ca:8d/00:00:9e:c9:8d/e8 Emask 0x50 (AtA bus error) ata#.00: status: { DRDY }This error occurred once for each https://bbs.archlinux.org/viewtopic.php?id=181782 of the three numbers (which also happens to correspond to the three sata ports my HDs are plugged into): 2 and 3 while I was using dd to zero them (I zeroed all three but 4 didn't give any errors), and 4 just after installing grub onto a mirror raid composing of HDs 2 and 3. All of the HDs originally used IDE so I used a converted to switch them (Model number CB-IS100)Additionally, when deconstructing the computers, one of the sata cables tore the first female connector out of the motherboard (hence why they start at 2), but while I know that's not preferable, I don't think it would cause this error.Finally, this motherboard was in a computer that had, as far as I could tell, a poor power supply that cause it to reboot when using a lot of CPU power.My question is really this: Will this cause any major problems or can I ignore it? Also, is there anything I can do to fix it?This is my dmesg:[ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux ver
Joined: May 28, 2011 Messages: 271 Thanks Received: 1 Trophy Points: 21 Freenas Domain Security Run email today: Code: freenas.domain kernel log messages: > (ada0:ahcich0:0:0:0): https://forums.freenas.org/index.php?threads/ata-status-41-drdy-err-error-40-unc.25864/ READ_FPDMA_QUEUED. ACB: 60 20 20 84 74 40 9b 00 00 00 00 00 > (ada0:ahcich0:0:0:0): CAM status: ATA Status Error > (ada0:ahcich0:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC ) > (ada0:ahcich0:0:0:0): https://www.redhat.com/archives/rhl-devel-list/2008-December/msg02951.html RES: 41 40 20 84 74 40 9b 00 00 00 00 > (ada0:ahcich0:0:0:0): Retrying command > (ada0:ahcich0:0:0:0): READ_FPDMA_QUEUED. ACB: 60 20 20 84 74 40 9b 00 00 00 00 00 > (ada0:ahcich0:0:0:0): drdy err CAM status: ATA Status Error > (ada0:ahcich0:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC ) > (ada0:ahcich0:0:0:0): RES: 41 40 20 84 74 40 9b 00 00 00 00 > (ada0:ahcich0:0:0:0): Retrying command > (ada0:ahcich0:0:0:0): READ_FPDMA_QUEUED. ACB: 60 20 20 84 74 40 9b 00 00 00 00 00 > (ada0:ahcich0:0:0:0): CAM status: ATA Status Error > (ada0:ahcich0:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC ) > ata drdy err (ada0:ahcich0:0:0:0): RES: 41 40 20 84 74 40 9b 00 00 00 00 > (ada0:ahcich0:0:0:0): Retrying command > (ada0:ahcich0:0:0:0): READ_FPDMA_QUEUED. ACB: 60 20 20 84 74 40 9b 00 00 00 00 00 > (ada0:ahcich0:0:0:0): CAM status: ATA Status Error > (ada0:ahcich0:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC ) > (ada0:ahcich0:0:0:0): RES: 41 40 20 84 74 40 9b 00 00 00 00 > (ada0:ahcich0:0:0:0): Retrying command > (ada0:ahcich0:0:0:0): READ_FPDMA_QUEUED. ACB: 60 20 20 84 74 40 9b 00 00 00 00 00 > (ada0:ahcich0:0:0:0): CAM status: ATA Status Error > (ada0:ahcich0:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC ) > (ada0:ahcich0:0:0:0): RES: 41 40 20 84 74 40 9b 00 00 00 00 > (ada0:ahcich0:0:0:0): Error 5, Retries exhaust I searched the forums and saw a few postings suggesting doing smartctl long test on a certain drive. I don't see which drive I should check from the error message. GUI says both volumes and all 22 drives are on-line. Scrub was recently started. I have Smart tests scheduled per Cyberjock advice. As background I replaced a few cables over the past few months per advice and those errors have not recurred. I also wiped a drive to remove pending sectors
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 0