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.

Photo

Bad hdd or bad files?


  • Please log in to reply
11 replies to this topic

#1 millipede

millipede

  • Members
  • 604 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:outer space
  • Local time:02:44 PM

Posted 22 January 2014 - 06:07 PM

I'm working on a laptop for a friend and it's looking like the hdd might be bad.
It's a Dell Inspiron 1545 with a 80gb WD hdd.

At startup, it fails every time.  Says it could be from a recent hardware or software change...  mentions the file winload.exe, says something about it being missing or corrupt.  My first thought was, oh, a file isn't a big deal.  Can't even get into safe mode though and I'm not sure if I am finding the right vista disk.  Was going to simply try a repair but one of my vista discs is missing(on my desk in front of me likely) and I'm not sure which one was labeled correctly.  One is just a service pack while the other is actually Vista.  :/
Anyway...  So, I ran the onboad diagnostics and the hdd short test failed rather quickly.  Error code 0146(I'll look that up in a minute)
After that I finished the rest of the diagnostics which all passed and then booted parted magic so I could check out the hdd better.
I tried running a short self test and it failed at 10%.  But I copied some of the output.
On the "error log" tab it shows "uncorrectable error in data /  at LBA = 0x00001fac = 8108"

I'm getting ready to go out with the family and will research these myself later...  What I need to figure out is if this uncorrectable data is just data and if a repair or fresh install of windows would fix it...  or, does the hdd simply need to be replaced.
Any thoughts are appreciated on either the answers to that OR how to figure it out.

Here is the output data if that helps...
 

smartctl 6.0 2012-10-10 r3643 [i686-linux-3.6.10-pmagic] (local build)
Copyright (C) 2002-12, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Scorpio Blue Serial ATA
Device Model:     WDC WD800BEVS-22RST0
Serial Number:    WD-WXE107201571
LU WWN Device Id: 5 0014ee 2aac62ab0
Firmware Version: 04.01G04
User Capacity:    80,026,361,856 bytes [80.0 GB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA/ATAPI-7 (minor revision not indicated)
Local Time is:    Wed Jan 22 16:50:09 2014 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:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
Self-test execution status:      ( 121)	The previous self-test completed having
					the read element of the test failed.
Total time to complete Offline 
data collection: 		( 3360) seconds.
Offline data collection
capabilities: 			 (0x7b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 (  46) minutes.
Conveyance self-test routine
recommended polling time: 	 (   6) minutes.
SCT capabilities: 	       (0x103f)	SCT Status supported.
					SCT Error Recovery Control supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   200   200   051    Pre-fail  Always       -       8
  3 Spin_Up_Time            0x0003   159   156   021    Pre-fail  Always       -       1016
  4 Start_Stop_Count        0x0032   094   094   000    Old_age   Always       -       6046
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   200   200   051    Pre-fail  Always       -       0
  9 Power_On_Hours          0x0032   086   086   000    Old_age   Always       -       10337
 10 Spin_Retry_Count        0x0013   100   100   051    Pre-fail  Always       -       0
 11 Calibration_Retry_Count 0x0012   100   100   051    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   095   095   000    Old_age   Always       -       5227
192 Power-Off_Retract_Count 0x0032   198   198   000    Old_age   Always       -       1600
193 Load_Cycle_Count        0x0032   148   148   000    Old_age   Always       -       157702
194 Temperature_Celsius     0x0022   106   082   000    Old_age   Always       -       37
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0012   200   200   000    Old_age   Always       -       1
198 Offline_Uncorrectable   0x0010   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       35
200 Multi_Zone_Error_Rate   0x0009   100   253   051    Pre-fail  Offline      -       0

SMART Error Log Version: 1
ATA Error Count: 1080 (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 1080 occurred at disk power-on lifetime: 10335 hours (430 days + 15 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ac 1f 00 40  Error: UNC at LBA = 0x00001fac = 8108

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 10 a0 1f 00 00 00      00:10:45.096  READ DMA
  c8 00 02 c8 0b 60 00 00      00:10:45.096  READ DMA
  c8 00 08 50 2d e3 03 00      00:10:45.077  READ DMA
  c8 00 02 d8 c3 60 00 00      00:10:45.068  READ DMA
  ca 00 01 50 a7 97 00 00      00:10:45.055  WRITE DMA

Error 1079 occurred at disk power-on lifetime: 10335 hours (430 days + 15 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ac 1f 00 40  Error: UNC at LBA = 0x00001fac = 8108

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 10 a0 1f 00 00 00      00:09:52.800  READ DMA
  c8 00 02 c8 0b 60 00 00      00:09:52.781  READ DMA
  c8 00 08 50 2d e3 03 00      00:09:52.762  READ DMA
  c8 00 02 d8 c3 60 00 00      00:09:52.754  READ DMA
  ca 00 01 50 a7 97 00 00      00:09:52.741  WRITE DMA

Error 1078 occurred at disk power-on lifetime: 10335 hours (430 days + 15 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ac 1f 00 40  Error: UNC at LBA = 0x00001fac = 8108

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 10 a0 1f 00 00 00      00:08:25.696  READ DMA
  c8 00 02 c8 0b 60 00 00      00:08:25.352  READ DMA
  c8 00 10 a0 e5 89 01 00      00:08:12.419  READ DMA
  c8 00 10 90 e5 89 01 00      00:08:12.409  READ DMA
  c8 00 08 50 2d e3 03 00      00:08:12.350  READ DMA

Error 1077 occurred at disk power-on lifetime: 10335 hours (430 days + 15 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ac 1f 00 40  Error: UNC at LBA = 0x00001fac = 8108

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 10 a0 1f 00 00 00      00:01:04.594  READ DMA
  c8 00 02 c8 0b 60 00 00      00:01:04.575  READ DMA
  c8 00 08 50 2d e3 03 00      00:01:04.556  READ DMA
  c8 00 02 d8 c3 60 00 00      00:01:04.547  READ DMA
  ca 00 01 50 a7 97 00 00      00:01:04.535  WRITE DMA

Error 1076 occurred at disk power-on lifetime: 10335 hours (430 days + 15 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ac 1f 00 40  Error: UNC at LBA = 0x00001fac = 8108

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 10 a0 1f 00 00 00      00:00:24.587  READ DMA
  c8 00 02 c8 0b 60 00 00      00:00:24.567  READ DMA
  c8 00 08 50 2d e3 03 00      00:00:24.549  READ DMA
  c8 00 02 d8 c3 60 00 00      00:00:24.540  READ DMA
  ca 00 01 50 a7 97 00 00      00:00:24.527  WRITE DMA

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed: read failure       90%     10337         8108
# 2  Short offline       Completed: read failure       90%     10316         8108
# 3  Short offline       Completed without error       00%      7721         -
# 4  Short offline       Completed without error       00%      7714         -
# 5  Short offline       Completed without error       00%      7712         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.


BC AdBot (Login to Remove)

 


m

#2 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:08:44 PM

Posted 22 January 2014 - 06:20 PM

Do you have access to a Windows Vista Installation CD?

#3 millipede

millipede
  • Topic Starter

  • Members
  • 604 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:outer space
  • Local time:02:44 PM

Posted 22 January 2014 - 06:24 PM

I do.  I tried to explain but perhaps not well.  I have a vista installation cd and a vista service pack cd on my desk.  I have a BAD memory, misplace things, etc...  and I don't remember which one I labeled how.  I found one of them and the laptop would not boot to it.  Gave the same error.  Maybe that one was the sp disk.  When I get home later this evening I'll poke around my desk some more and see if I can find the other one and test it out.
Odd thing...  I also have a "backup disk" for this laptop from the last time I looked at it.  I could not boot to that either...  but, parted magic loaded from disk.   hmmm



#4 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:08:44 PM

Posted 22 January 2014 - 06:35 PM

When you boot to your Vista CD go to the Recovery COnsole, and find out your Windows Drive and type in the following:

chkdsk /f driverletter:

Hit Enter then hit Y

#5 James Litten

James Litten

    Ԁǝǝ˥q


  • BC Advisor
  • 1,943 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:03:44 PM

Posted 23 January 2014 - 12:06 AM

Hi

 

Have you tried getting into the Advanced Boot Options when you start it (hitting F8 at startup) and choosing Last Known Good Configuration ?

 

-=[ James ]=-



#6 millipede

millipede
  • Topic Starter

  • Members
  • 604 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:outer space
  • Local time:02:44 PM

Posted 23 January 2014 - 01:58 AM

Tried a few times but it never went there for me.  When I said I tried to get into safe mode, that's what I meant.  I couldn't even get to that menu.  Otherwise, I would have tried that.
Way past my bedtime.  I will be messing with it all in the morning again.  Hopefully I'll find that other cd and see if I can do a repair. 



#7 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:08:44 PM

Posted 23 January 2014 - 03:54 PM

Please download Data Life guard Tools from http://www.wdc.com and run it, your drive may be so corrupted it will not function.

#8 millipede

millipede
  • Topic Starter

  • Members
  • 604 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:outer space
  • Local time:02:44 PM

Posted 23 January 2014 - 05:29 PM

cryptodan, it looks to me like that is a windows program and I wouldn't be able to load it without being in windows.  I could take the hdd out and attack it to my desktop and then run that.

I found my vista iso(yay) but, repair failed.  In the details it mentions missing Os Loader..  I have a feeling this is similar to the startup error mentioning winload.exe being missing or corrupt or something. 
Stinks that startup repair didn't work. 
I'm going to try a few more things.  The way everything else is working so far I don't think it will work but I might try system restore from the vista disk menu. 
I'll keep poking around and see if something will work.
I will probably end up backing up some files in case I have to simply re-install windows.  I have that backup disk I created, well last February I guess but it didn't load to that last time I tried.  We'll see what happens.
Will update again later when something either works or doesn't.

Edit:  I was right, restore didn't work.  Said there were no restore points.  Moving on...


Edited by millipede, 23 January 2014 - 05:42 PM.


#9 millipede

millipede
  • Topic Starter

  • Members
  • 604 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:outer space
  • Local time:02:44 PM

Posted 25 January 2014 - 10:10 PM

I gave up trying to find other solutions.  If it really was just a corrupt or missing file, I figured there had to be a method of simply repairing it.  But the few places I found directions, they weren't completely simple.
At any rate...  I ended up formatting and reinstalling Vista.  It worked, so far.  My Iso already had SP1 on it and so far I've installed all the updates up to, including, and more than SP2.  Got a lot done so far and no errors.  After the windows updates are done and I install an AV, I'll then download the diagnostics tool from wd. 

Lots of updates, program installations and their updates, files moved back on(backed up the pictures), etc... 
In the meantime...
IF this was nothing more than a corrupt or missing file...  Is there any way to prevent this sort of thing from happening again?  I found some people ran into this problem more than once.



#10 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:08:44 PM

Posted 26 January 2014 - 02:12 PM

I gave up trying to find other solutions.  If it really was just a corrupt or missing file, I figured there had to be a method of simply repairing it.  But the few places I found directions, they weren't completely simple.


Yes it is very simple, and that is why I was asking you to get a Vista CD, so you could perform a chkdsk /f on your drive to repair the drive and fix errors. Whoever you went to for help on the issue and whatever sites you went to I would not trust them.

#11 millipede

millipede
  • Topic Starter

  • Members
  • 604 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:outer space
  • Local time:02:44 PM

Posted 26 January 2014 - 03:51 PM

hmmm  I'm looking back through the posts and wondered if I just overlooked that mention of chkdsk...  Sometimes when I'm multitasking, I miss things.  ha. 
If that would have worked, that would have been the quickest thing.  Still have a few things to tweak and install... but, sometimes on an older machine full of programs that aren't quite necessary, a fresh install isn't the worst thing that could happen to it.  :)

It was just websites, while looking for the exact issue... the missing or corrupt winload file.  The posts I saw that looked complicated were in the tech support sections of the microsoft site, where ANYONE can reply.  Some of the replies were horrible.  One person said they called microsoft and were told to type something in somewhere, etc... and that fixed it.  They didn't explain ANYTHING about what fixed it.  Kind of a pointless reply. 

So, you think chkdsk would have found and fixed the issue?  Even though the windows cd couldn't repair it on its own? 
Wish I paid more attention to the posts and gave that a try...  but again, a fresh install sure wont hurt this machine.  No adware and junk to clean up now.  :)



#12 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:08:44 PM

Posted 26 January 2014 - 03:55 PM

Yes a chkdsk /f usually fixes such issues.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users