Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.



  • Please log in to reply
No replies to this topic

#1 fleamour


  • Members
  • 297 posts
  • Gender:Male
  • Location:UK
  • Local time:02:47 AM

Posted 08 December 2010 - 01:06 PM

This is a copy of error log of which there are 2016 similar errors:

Complete error log:

SMART Error Log Version: 1
ATA Error Count: 2016 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 2016 occurred at disk power-on lifetime: 608 hours (25 days + 8 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
-- -- -- -- -- -- --
40 51 00 47 f6 df e2 Error: UNC at LBA = 0x02dff647 = 48232007

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
40 00 02 47 f6 df e2 00 00:16:26.585 READ VERIFY SECTOR(S)
40 00 04 4b f6 df e2 00 00:16:26.568 READ VERIFY SECTOR(S)
40 00 04 47 f6 df e2 00 00:16:19.756 READ VERIFY SECTOR(S)
40 00 08 47 f6 df e2 00 00:16:12.951 READ VERIFY SECTOR(S)
40 00 08 3f f6 df e2 00 00:16:12.940 READ VERIFY SECTOR(S)

Can any expert shed any light on what this error means?

I dropped the drive from kitchen surface to kitchen floor many moons ago, but still use it to back up my Linux laptop, probably not best practise. Is this an error of impending doom?

ASRock Conroe (micro ATX) - Ubuntu 12.04/Win 7 Ultimate (x86)
Intel C2D E8400 3.0GHz/low profile Noctua (single fan)
4GB OCZ DDR2 RAM, GeForce GT220 1024MB

Vintage IBM-T21 laptop, Xubuntu Lucid LTS
512MB KingSpec RAM, 1GHz CPU [T22 Fan], Wireless-G PCMCIA, 7200RPM HDD

BC AdBot (Login to Remove)


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users