Hard Disk Unc Error
Contents |
view Previous topic | Next topic Author Message rocket777 Post subject: meaning of scan error codes mhdd unc (unc etc.)Posted: April 22nd, 2007, 16:15 Joined: September 6th, 2006, 2:14Posts: 10 I idnf error have a drive that gets a few unc errors and lists the error lba in the bottom right corner. But drdy err I'm curious, what is an unc error? Can't find the meaning of the time, unc, abrt, idnf, amnf, tonf, and bbk. Is this documented anywhere? Are all of these equally bad? Can failed command: read fpdma queued I run scan with remap and use arrow keys to go to the bad areas and just fix these few errors? Top bsnyder Post subject: Posted: April 22nd, 2007, 17:58 Joined: January 4th, 2007, 22:50Posts: 21Location: Seal Beach, CA (AMNF) Data Address Mark Not Found: During the read sector command, a data address mark was not found after finding the correct ID field
Unhcr
for the requested sector (usually a media error or read instability). (TONF) Track 0 Not Found: Track 0 was not found during drive recalibration. (ABRT) Aborted Command: The requested command was aborted due to a device status error. (IDNF) ID Not Found: The required cylinder, head, and sector could not be found, or an ECC error occurred in the ID field. (UNC) Uncorrectable Data: An ECC error in the data field could not be corrected (a media error or read instability). (BBK) Bad Mark Block: A bad sector mark was found in the ID field of the sector or an Interface CRC error occurred. Taken from: http://www.deepspar.com/pdf/DeepSparDis ... paper3.pdf Top rocket777 Post subject: Posted: April 23rd, 2007, 16:10 Joined: September 6th, 2006, 2:14Posts: 10 Thanks, interesting paper. One other question that it didn't answer, is there a way to see the current set of remapped sectors? I was able to remap the two unc's I had and perhaps my drive will work ok now. I had a strange problem. Somehow while doing only a read of the drive (under windows 2k) it wiped out the signature at the end of
Registered: 2010-02-11 Posts: 65 Is this a hardware issue? My laptop was working fine this morning, i was able to complete my work both in arch and in windows (i dualboot). I haven't slammed by laptop on anything, and i
Uncrc
know for a fact that everytime i closed it; i closed it correctly on uncrate windows and arch.Now whenever i attempt to boot arch i'm getting the following error: ata1.00: status: {DRDY ERR} ata1.00: error: {UNC} ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 ata1.00: irq_stat 0x40000008Then a bunch of "Buffer I/O error on device sda, logical block x"; with x being various numbers. My windows partition and fallback http://forum.hddguru.com/viewtopic.php?t=6992&start= partition aren't working either. Like the thread title says, is this a problem caused by my hardware; if so is there any fix for it? Offline #2 2011-01-21 02:52:03 Coacher Banned Registered: 2009-07-31 Posts: 210 Re: Is this a hardware issue? Yeah, its 99% hardware problem. To be more specific it is your hard drive problem. It has some sectors with uncorrectable errors(UNC) you can try to remap them using MHDD https://bbs.archlinux.org/viewtopic.php?id=112091 or Victoria(both running from DOS from some media) or utility from manufacturer in order to save the most of the data, if you dont have too many. But you should definitely start with utilty from your hard drive manufacturer. Just go to website and download some fitness test utility. It will give you more info and probably even fix the issue. If there is no such utility you can try badblocks form e2fsprogs package. Last edited by Coacher (2011-01-21 02:52:38) Offline #3 2011-01-21 03:56:26 dozerismydogsname Member Registered: 2010-02-11 Posts: 65 Re: Is this a hardware issue? Coacher wrote:Yeah, its 99% hardware problem. To be more specific it is your hard drive problem. It has some sectors with uncorrectable errors(UNC) you can try to remap them using MHDD or Victoria(both running from DOS from some media) or utility from manufacturer in order to save the most of the data, if you dont have too many. But you should definitely start with utilty from your hard drive manufacturer. Just go to website and download some fitness test utility. It will give you more info and probably even fix the issue. If there is no such utility you can try badblocks form e2fsprogs package.Messing around with mhdd and i'll try victoria later to
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 Social Media Facebook Twitter Useful Links https://ubuntuforums.org/showthread.php?t=937872 Distrowatch Bugs: Ubuntu PPAs: Ubuntu Web Upd8: Ubuntu OMG! Ubuntu Ubuntu Insights Planet Ubuntu Activity Page Please read before SSO login Advanced Search Forum The Ubuntu Forum Community Ubuntu Official Flavours Support Hardware [ubuntu] hdd error {DRDY err} Having https://forums.anandtech.com/threads/hard-drive-pending-sector-errors-how-severe.2068269/ an Issue With Posting ? Do you want to help us debug the posting issues ? < is the place to report it, thanks ! Page 1 of 2 12 Last Jump to page: Results 1 to 10 of hard disk 12 Thread: hdd error {DRDY err} Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode October 4th, 2008 #1 Asrael View Profile View Forum Posts Private Message First Cup of Ubuntu Join Date Mar 2006 Beans 2 hdd error {DRDY err} My system has two identical Maxtor 200GB SATA drives. Ubuntu is installed on the Primary, which runs perfectly. However when the second hard drive is connected Ubuntu hard disk unc won't boot. I get an error screen which reads: [272.854943] ata2.00: status: {DRDY err} [xxx.xxxxxx] ata2.00: error: {UNC} [xxx.xxxxxx]ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 [xxx.xxxxxx] ata2.00: BMDMA stat 0x24 [xxx.xxxxxx] ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in the x's are all different numbers. The message repeats several times. Sometimes it says Buffer I/O error on device sdb1, logical block x (where x is a changing number) In the forum a similar question has been asked before by others, but not answered. I have tried switching the cables, the result was the same as before. Since I can't get Ubuntu to boot with the second drive connected I can't use any tools to analyse or fix the disk as far as I know. My guess is the disk is broken, am I correct? If not how might I fix this? Thanks in advance, Asrael Adv Reply October 6th, 2008 #2 docmarine View Profile View Forum Posts Private Message Spilled the Beans Join Date Apr 2007 Beans 17 Re: hdd error {DRDY err} I am getting the same error my self when trying to install Xubuntu. Previously I had Ubuntu running on this machine with no problems whatsoever. I have 2x 120 gb disks SATA running off a "pesudo-RAID" card configured with each disk in "striping mode" Any help is appreciated.... Adv Reply October 12th, 2008 #3 mushroomcloudwarrior View Pr
Display results as threads More... Useful Searches Recent Posts Menu Forums Forums Quick Links Search Forums Recent Posts Menu Log in Sign up AnandTech Forums: Technology, Hardware, Software, and Deals Forums > Hardware and Technology > Memory and Storage > Hard drive Pending Sector errors: how severe? Discussion in 'Memory and Storage' started by ahallanandtech, Apr 18, 2010. ahallanandtech Junior Member Joined: Mar 7, 2010 Messages: 8 Likes Received: 0 I monitor my hard drives' S.M.A.R.T. status with Crystal Disk Info. I've encountered a number of hard drives with "Pending Sector" errors that seemed also to crash the hard drive. In one case, after finding twelve pending sector errors, I ran chkdsk in Windows and although it "recovered" five or six files, it also corrupted them and made them useless (I had backups). In another case, I had a laptop drive that would blue screen however you tried to boot it (even in safe mode); I cloned this drive to another that that one booted right up. The original drive had one pending sector error. However, after running DBAN on both failed drives to blank them out, all of the pending sector errors disappeared. I might have expected that they would have been replaced by spare sectors, but according to CDI, neither drive has any reallocated sectors or any other S.M.A.R.T. errors anymore. So how should I view these drives for future use? One was a few years old but the other is only about 6 months old - still under warranty but I can't RMA it I imagine with no errors anymore (it also passes the Western Digital diagnostic with no errors). Pending Sectors are sectors on the drive that cannot be read, right? What causes them? If blanking these sectors does not cause them to be deactivated by the drive firmware and replaced (as seems to have happened with these two drives), should I assume those sectors are really OK? I had assumed that such drives were basically dying and I should probably recycle them - but could such errors just be glitches that could appear from time to time and not indicate pending hardware failure of the drives, making them no more likely than any other drive to fail in the future? Thanks for your insight! #1 ahallanandtech, Apr 18, 2010 Russwinters Senior member Joined: Jul 31, 2009 Messages: 409 Likes Received: 0 Pending sectors are sectors that the drive has flagged as "probably bad" Most likely the drive "tested" them and found them to not be bad, most likely they were UNC errors that were caused by failed/incomplete writes causing the ECC to not match the actual data. Unfortunately the way CHKDSK tests these is pr