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 sectors


  • Please log in to reply
11 replies to this topic

#1 millipede

millipede

  • Members
  • 614 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:outer space
  • Local time:11:56 AM

Posted 05 December 2012 - 12:16 PM

Long story behind this drive... but... to keep it short.
It's a windows 7 drive, refurbished...
Running a short test at one point failed....

Windows still seems to run just fine.
I want to eventually put ubuntu on this drive but I want to resolve any drive issues.
So, I ran chkdsk...
Not sure how helpful this is but here's a log from it.

Log Name:      Application
Source:        Microsoft-Windows-Wininit
Date:          12/5/2012 12:12:26 AM
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      Combs-PC
Description:


Checking file system on C:
The type of the file system is NTFS.

One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.                         

CHKDSK is verifying files (stage 1 of 5)...
  122112 file records processed.                                         

File verification completed.
  181 large file records processed.                                   

  0 bad file records processed.                                     

  0 EA records processed.                                           

  44 reparse records processed.                                      

CHKDSK is verifying indexes (stage 2 of 5)...
The file reference 0x1000000000a28 of index entry msdsm.inf_amd64_neutral_7a6981d1020ef566 of index $I30
with parent 0x918 is not the same as 0x2000000000a28.
Deleting index entry msdsm.inf_amd64_neutral_7a6981d1020ef566 in index $I30 of file 2328.
The file reference 0x1000000000a28 of index entry MSDSM~1.INF of index $I30
with parent 0x918 is not the same as 0x2000000000a28.
Deleting index entry MSDSM~1.INF in index $I30 of file 2328.
Index entry msdv.inf_amd64_neutral_571f87a277565224 of index $I30 in file 0x918 points to unused file 0xa29.
Deleting index entry msdv.inf_amd64_neutral_571f87a277565224 in index $I30 of file 2328.
Index entry MSDV~1.INF of index $I30 in file 0x918 points to unused file 0xa29.
Deleting index entry MSDV~1.INF in index $I30 of file 2328.
Index entry mshdc.inf_amd64_neutral_a69a58a4286f0b22 of index $I30 in file 0x918 points to unused file 0xa2a.
Deleting index entry mshdc.inf_amd64_neutral_a69a58a4286f0b22 in index $I30 of file 2328.
Index entry MSHDC~1.INF of index $I30 in file 0x918 points to unused file 0xa2a.
Deleting index entry MSHDC~1.INF in index $I30 of file 2328.
Index entry mstape.inf_amd64_neutral_c2bb3ef1c45cd5a1 of index $I30 in file 0x918 points to unused file 0xa2d.
Deleting index entry mstape.inf_amd64_neutral_c2bb3ef1c45cd5a1 in index $I30 of file 2328.
Index entry MSTAPE~1.INF of index $I30 in file 0x918 points to unused file 0xa2d.
Deleting index entry MSTAPE~1.INF in index $I30 of file 2328.
The file reference 0x1000000000a2e of index entry mtconfig.inf_amd64_neutral_4de24f49b5e60c45 of index $I30
with parent 0x918 is not the same as 0x2000000000a2e.
Deleting index entry mtconfig.inf_amd64_neutral_4de24f49b5e60c45 in index $I30 of file 2328.
The file reference 0x1000000000a2e of index entry MTCONF~1.INF of index $I30
with parent 0x918 is not the same as 0x2000000000a2e.
Deleting index entry MTCONF~1.INF in index $I30 of file 2328.
The file reference 0x1000000000a2f of index entry multiprt.inf_amd64_neutral_988a34fc912eab54 of index $I30
with parent 0x918 is not the same as 0x2000000000a2f.
Deleting index entry multiprt.inf_amd64_neutral_988a34fc912eab54 in index $I30 of file 2328.
The file reference 0x1000000000a2f of index entry MULTIP~1.INF of index $I30
with parent 0x918 is not the same as 0x2000000000a2f.
Deleting index entry MULTIP~1.INF in index $I30 of file 2328.
  164996 index entries processed.                                        

Index verification completed.
CHKDSK is scanning unindexed files for reconnect to their original directory.
  25 unindexed files scanned.                                        

CHKDSK is recovering remaining unindexed files.
  6 unindexed files recovered.                                      

CHKDSK is verifying security descriptors (stage 3 of 5)...
  122112 file SDs/SIDs processed.                                        

Cleaning up 5 unused index entries from index $SII of file 0x9.
Cleaning up 5 unused index entries from index $SDH of file 0x9.
Cleaning up 5 unused security descriptors.
Security descriptor verification completed.
  21443 data files processed.                                           

CHKDSK is verifying Usn Journal...
  36037728 USN bytes processed.                                            

Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
  122096 files processed.                                                

File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
  54813699 free clusters processed.                                        

Free space verification is complete.
Correcting errors in the master file table's (MFT) BITMAP attribute.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

 244196351 KB total disk space.
  24649820 KB in 85742 files.
     60108 KB in 21445 indexes.
         8 KB in bad sectors.
    231619 KB in use by the system.
     65536 KB occupied by the log file.
 219254796 KB available on disk.

      4096 bytes in each allocation unit.
  61049087 total allocation units on disk.
  54813699 allocation units available on disk.

Internal Info:
00 dd 01 00 be a2 01 00 83 32 03 00 00 00 00 00  .........2......
25 01 00 00 2c 00 00 00 00 00 00 00 00 00 00 00  %...,...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

Windows has finished checking your disk.
Please wait while your computer restarts.

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" />
    <EventID Qualifiers="16384">1001</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-12-05T05:12:26.000000000Z" />
    <EventRecordID>4843</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>Combs-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>

Checking file system on C:
The type of the file system is NTFS.

One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.                         

CHKDSK is verifying files (stage 1 of 5)...
  122112 file records processed.                                         

File verification completed.
  181 large file records processed.                                   

  0 bad file records processed.                                     

  0 EA records processed.                                           

  44 reparse records processed.                                      

CHKDSK is verifying indexes (stage 2 of 5)...
The file reference 0x1000000000a28 of index entry msdsm.inf_amd64_neutral_7a6981d1020ef566 of index $I30
with parent 0x918 is not the same as 0x2000000000a28.
Deleting index entry msdsm.inf_amd64_neutral_7a6981d1020ef566 in index $I30 of file 2328.
The file reference 0x1000000000a28 of index entry MSDSM~1.INF of index $I30
with parent 0x918 is not the same as 0x2000000000a28.
Deleting index entry MSDSM~1.INF in index $I30 of file 2328.
Index entry msdv.inf_amd64_neutral_571f87a277565224 of index $I30 in file 0x918 points to unused file 0xa29.
Deleting index entry msdv.inf_amd64_neutral_571f87a277565224 in index $I30 of file 2328.
Index entry MSDV~1.INF of index $I30 in file 0x918 points to unused file 0xa29.
Deleting index entry MSDV~1.INF in index $I30 of file 2328.
Index entry mshdc.inf_amd64_neutral_a69a58a4286f0b22 of index $I30 in file 0x918 points to unused file 0xa2a.
Deleting index entry mshdc.inf_amd64_neutral_a69a58a4286f0b22 in index $I30 of file 2328.
Index entry MSHDC~1.INF of index $I30 in file 0x918 points to unused file 0xa2a.
Deleting index entry MSHDC~1.INF in index $I30 of file 2328.
Index entry mstape.inf_amd64_neutral_c2bb3ef1c45cd5a1 of index $I30 in file 0x918 points to unused file 0xa2d.
Deleting index entry mstape.inf_amd64_neutral_c2bb3ef1c45cd5a1 in index $I30 of file 2328.
Index entry MSTAPE~1.INF of index $I30 in file 0x918 points to unused file 0xa2d.
Deleting index entry MSTAPE~1.INF in index $I30 of file 2328.
The file reference 0x1000000000a2e of index entry mtconfig.inf_amd64_neutral_4de24f49b5e60c45 of index $I30
with parent 0x918 is not the same as 0x2000000000a2e.
Deleting index entry mtconfig.inf_amd64_neutral_4de24f49b5e60c45 in index $I30 of file 2328.
The file reference 0x1000000000a2e of index entry MTCONF~1.INF of index $I30
with parent 0x918 is not the same as 0x2000000000a2e.
Deleting index entry MTCONF~1.INF in index $I30 of file 2328.
The file reference 0x1000000000a2f of index entry multiprt.inf_amd64_neutral_988a34fc912eab54 of index $I30
with parent 0x918 is not the same as 0x2000000000a2f.
Deleting index entry multiprt.inf_amd64_neutral_988a34fc912eab54 in index $I30 of file 2328.
The file reference 0x1000000000a2f of index entry MULTIP~1.INF of index $I30
with parent 0x918 is not the same as 0x2000000000a2f.
Deleting index entry MULTIP~1.INF in index $I30 of file 2328.
  164996 index entries processed.                                        

Index verification completed.
CHKDSK is scanning unindexed files for reconnect to their original directory.
  25 unindexed files scanned.                                        

CHKDSK is recovering remaining unindexed files.
  6 unindexed files recovered.                                      

CHKDSK is verifying security descriptors (stage 3 of 5)...
  122112 file SDs/SIDs processed.                                        

Cleaning up 5 unused index entries from index $SII of file 0x9.
Cleaning up 5 unused index entries from index $SDH of file 0x9.
Cleaning up 5 unused security descriptors.
Security descriptor verification completed.
  21443 data files processed.                                           

CHKDSK is verifying Usn Journal...
  36037728 USN bytes processed.                                            

Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
  122096 files processed.                                                

File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
  54813699 free clusters processed.                                        

Free space verification is complete.
Correcting errors in the master file table's (MFT) BITMAP attribute.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

 244196351 KB total disk space.
  24649820 KB in 85742 files.
     60108 KB in 21445 indexes.
         8 KB in bad sectors.
    231619 KB in use by the system.
     65536 KB occupied by the log file.
 219254796 KB available on disk.

      4096 bytes in each allocation unit.
  61049087 total allocation units on disk.
  54813699 allocation units available on disk.

Internal Info:
00 dd 01 00 be a2 01 00 83 32 03 00 00 00 00 00  .........2......
25 01 00 00 2c 00 00 00 00 00 00 00 00 00 00 00  %...,...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

Windows has finished checking your disk.
Please wait while your computer restarts.
</Data>
  </EventData>
</Event>

AFTER chkdsk had run, ran a short test with seatools (hard drive is samsung but when looking for tools for it, it leads to seagate's site and tools)
short test failed rather quickly.
It suggested seatools for DOS as it is supposed to be able to repair bad sectors and such...
BUT, it failed to boot all the way from that CD.
I planned on trying to install ubuntu alongside of windows... but I wanted to try and resolve any hard drive problems first, if possible. At this point, I'm just not sure. Windows is running... but, that doesn't mean it will continue to run I guess.
Any advice on dealing with bad sectors or whatever might be ailing this hard drive?

BC AdBot (Login to Remove)

 


#2 rotor123

rotor123

  • Moderator
  • 8,093 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:12:56 PM

Posted 05 December 2012 - 12:37 PM

One thing to do. Back up anything you would hate to have go missing.

Try burning the Seatools for dos to a Cd again. It does work, I've used it.

Stray thought: Be prepared to replace the drive, they do not last forever. It isn't if a drive will die, it is when.
In the past when I have had a Boot drive act like yours I have replaced it and relegated that old drive to only unimportant things that I don't care if they go away use.

What I didn't like seeing was that the short test failed. That suggests deeper troubles.

Good Luck
Roger

Edited by rotor123, 05 December 2012 - 12:42 PM.

Fortune Cookie says: Fortune not Found: Abort, Retry, Ignore?

Sent from my All-In-One Desktop. Perfect for Internet, Not for heavy usage or gaming however.

How Does a computer get Infected? http://www.bleepingcomputer.com/forums/t/2520/how-did-i-get-infected/
Forum Rules,    The BC Welcome Guide

167 @ June 2015


#3 coxchris

coxchris

  • Members
  • 1,151 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Atwater
  • Local time:09:56 AM

Posted 05 December 2012 - 12:38 PM

Hi,

I see you run chkdsk that is completely successfully and repaired you can try to perform a different repair tool from this site http://www.tacktech.com/display.cfm?ttid=287 just click on Samsung drive to download the tools.

Have you heard grinding noises on the drive?

If Windows display some message about your hard drive from inside windows there is a serious error with the drive

I would wait and see

Are you dual booting your Ubuntu or clean install of Ubuntu

AA in Computer Networking Technology

BS in Information Technology 

Comptia A+, Project+, L+

Renewable:  N+,S+

CIW Web Design Specialist, JavaScript Specialist,  Database Design Specialist 

LPIC-1, SUSE 


#4 millipede

millipede
  • Topic Starter

  • Members
  • 614 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:outer space
  • Local time:11:56 AM

Posted 05 December 2012 - 01:27 PM

rotor, tried downloading and creating a new CD... still didn't work. It starts up the loading process, says it's doing this and that... then a mostly black screen with a little bit of text so small you almost can't read it. It's purple and TINY and looks like it says "invalid". Last time I tried it was similar except there was some random characters under that as well. All just near the top of the screen.

coxchris, Unfortunately, EVERYTHING that points to samsung redirects to seagate. All of the samsung tools are no longer on samsung's website. And seatools is the only diagnostic software I could find at seagate's website.

I originally planned on installing ubuntu alongside of windows... partly just because... well, just because. This drive came on another computer with windows 7 installed and some games. Nothing vital though. I just feel bad simply deleting a hard drive with windows 7 on it, since windows is so expensive. But... it wasn't going to be working in the computer I'm putting the hard drive in anyway so I guess it doesn't matter.

I WAS working on the hard drive IN the computer it came in. I was trying that because I was having a little trouble checking on things in the computer I'm moving it to. I figured it would be easier to resolve issues and even partition if need be in the computer where the drive was actually able to function in.
The machine it's going into doesn't support windows 7 so I can't do much besides run ubuntu off a flash drive to poke around. That was becoming a hassle...
BUT, my wife just got mad I took the other hard drive out and put this one back in. This whole situation has been QUITE frustrating :(
So, that hard drive is sitting on my desk again... and perhaps, I'll pop it into my own machine that I'm on now so I don't have to mess with so many computers at one time.
blah... I may just format the stupid thing and see what happens... but I'm guessing if there's bad sectors or whatever causing a test to fail, it might not help much.
I may have to take a few deep breaths before I get back to this....... Got myself in a bad mood. :/

#5 millipede

millipede
  • Topic Starter

  • Members
  • 614 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:outer space
  • Local time:11:56 AM

Posted 05 December 2012 - 04:46 PM

minor update:
I have that hard drive in my own computer now. I ran chkdsk from within windows and it found no problems. I'm going through and cleaning some things up... including a bunch of pictures and sound files someone left on here. This is not the first time I've bought a used computer and found lots of personal stuff on it.

Anyway... I'm going to download a program so I can run the short test on the drive from my own computer, I hope...
At any rate, I randomly decided I might want to run a scan of some sort on it. It seemed clean running and all and has microsoft security essentials or whatever that's called... but I'm running a malwarebytes scan at the moment and it has 34 objects detected at the moment. So I guess I better take care of that before I go further checking the hard drive for errors.

Edit: 33 entries were pup.mywebsearch and 1 was pup.funwebproducts. Nothing too harmful,I doubt they had anything to do with the hard drive errors but I'll clean that up anyway.

Edited by millipede, 05 December 2012 - 05:42 PM.


#6 millipede

millipede
  • Topic Starter

  • Members
  • 614 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:outer space
  • Local time:11:56 AM

Posted 07 December 2012 - 11:19 AM

Finally got back to that drive this morning. I installed GSmartControl, something someone suggested while I was checking out another drive recently.
Here's the output before I even try to run any scans. Errors were there already and lots of them... all pointing to an aging and failing drive... so it seems to me anyway.
I would rather NOT go out and buy a new hard drive to get that laptop up and running... but I also don't want to get it all set up only to have to buy a new drive anyway not too long from now.

I'm still quite upset about the person we bought that computer from. I find it hard to believe he didn't know anything about that drive being refurbished... or it's current state. :(
Why do computer parts cost so much?

Here's the output from GSmart
smartctl 5.43 2012-06-30 r3573 [i686-w64-mingw32-win7(64)-sp1] (sf-5.43-1)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     SAMSUNG SpinPoint M7
Device Model:     SAMSUNG HM250HI
Serial Number:    S1YQJDNS826971
LU WWN Device Id: 5 0024e9 001f865bd
Firmware Version: 2AC101C4
User Capacity:    250,059,350,016 bytes [250 GB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 6
Local Time is:    Fri Dec 07 10:07:21 2012 CST
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
See vendor-specific Attribute list for marginal Attributes.

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: 		( 4200) seconds.
Offline data collection
capabilities: 			 (0x51) SMART execute Offline immediate.
					No Auto Offline data collection support.
					Suspend Offline collection upon new
					command.
					No Offline surface scan supported.
					Self-test supported.
					No 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: 	 (  70) minutes.
SCT capabilities: 	       (0x003f)	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     0x002f   100   100   047    Pre-fail  Always       -       6678
  2 Throughput_Performance  0x0027   252   252   039    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0023   093   092   035    Pre-fail  Always       -       2350
  4 Start_Stop_Count        0x0032   097   097   050    Old_age   Always       -       3759
  5 Reallocated_Sector_Ct   0x0033   252   252   051    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002f   252   252   047    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0025   252   252   037    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0032   100   100   050    Old_age   Always       -       2642
 10 Spin_Retry_Count        0x0033   252   252   051    Pre-fail  Always       -       0
 11 Calibration_Retry_Count 0x0032   100   100   050    Old_age   Always       -       120
 12 Power_Cycle_Count       0x0032   097   097   050    Old_age   Always       -       3741
183 Runtime_Bad_Block       0x0032   252   252   050    Old_age   Always       -       0
184 End-to-End_Error        0x0033   252   252   051    Pre-fail  Always       -       0
186 Unknown_Attribute       0x0032   252   252   050    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   050    Old_age   Always       -       6565
188 Command_Timeout         0x0032   252   252   050    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0002   080   045   002    Old_age   Always       -       19 (Min/Max 13/55)
191 G-Sense_Error_Rate      0x0022   099   099   034    Old_age   Always       -       12834
192 Power-Off_Retract_Count 0x0022   252   252   034    Old_age   Always       -       0
193 Load_Cycle_Count        0x0032   001   001   050    Old_age   Always   FAILING_NOW 3653391
194 Temperature_Celsius     0x0002   064   045   002    Old_age   Always       -       19 (Min/Max 13/55)
195 Hardware_ECC_Recovered  0x003a   100   100   058    Old_age   Always       -       0
196 Reallocated_Event_Count 0x0032   252   252   050    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   100   100   050    Old_age   Always       -       2
198 Offline_Uncorrectable   0x0030   252   252   048    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0036   200   200   054    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x002a   100   100   042    Old_age   Always       -       222

SMART Error Log Version: 1
ATA Error Count: 756 (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 756 occurred at disk power-on lifetime: 2627 hours (109 days + 11 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 01 58 1c 60 e0  Error: UNC 1 sectors at LBA = 0x00601c58 = 6298712

  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 01 58 1c 60 e0 08      00:00:04.003  READ DMA
  ec 00 00 00 00 00 a0 08      00:00:04.003  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 08      00:00:04.003  SET FEATURES [Set transfer mode]
  ec 00 00 00 00 00 a0 08      00:00:04.003  IDENTIFY DEVICE
  c8 00 01 58 1c 60 e0 08      00:00:04.002  READ DMA

Error 755 occurred at disk power-on lifetime: 2627 hours (109 days + 11 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 01 58 1c 60 e0  Error: UNC 1 sectors at LBA = 0x00601c58 = 6298712

  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 01 58 1c 60 e0 08      00:00:04.002  READ DMA
  ec 00 00 00 00 00 a0 08      00:00:04.002  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 08      00:00:04.002  SET FEATURES [Set transfer mode]
  ec 00 00 00 00 00 a0 08      00:00:04.002  IDENTIFY DEVICE
  c8 00 01 58 1c 60 e0 08      00:00:04.000  READ DMA

Error 754 occurred at disk power-on lifetime: 2627 hours (109 days + 11 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 01 58 1c 60 e0  Error: UNC 1 sectors at LBA = 0x00601c58 = 6298712

  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 01 58 1c 60 e0 08      00:00:04.000  READ DMA
  ec 00 00 00 00 00 a0 08      00:00:04.000  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 08      00:00:04.000  SET FEATURES [Set transfer mode]
  ec 00 00 00 00 00 a0 08      00:00:04.000  IDENTIFY DEVICE
  c8 00 01 58 1c 60 e0 08      00:00:03.998  READ DMA

Error 753 occurred at disk power-on lifetime: 2627 hours (109 days + 11 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 01 58 1c 60 e0  Error: UNC 1 sectors at LBA = 0x00601c58 = 6298712

  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 01 58 1c 60 e0 08      00:00:03.998  READ DMA
  ec 00 00 00 00 00 a0 08      00:00:03.998  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 08      00:00:03.998  SET FEATURES [Set transfer mode]
  ec 00 00 00 00 00 a0 08      00:00:03.998  IDENTIFY DEVICE
  c8 00 01 58 1c 60 e0 08      00:00:03.996  READ DMA

Error 752 occurred at disk power-on lifetime: 2627 hours (109 days + 11 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 01 58 1c 60 e0  Error: UNC 1 sectors at LBA = 0x00601c58 = 6298712

  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 01 58 1c 60 e0 08      00:00:03.996  READ DMA
  ec 00 00 00 00 00 a0 08      00:00:03.996  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 08      00:00:03.996  SET FEATURES [Set transfer mode]
  ec 00 00 00 00 00 a0 08      00:00:03.996  IDENTIFY DEVICE
  c8 00 01 58 1c 60 e0 08      00:00:03.995  READ 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%      2633         6298711
# 2  Short offline       Aborted by host               90%      2633         -
# 3  Short offline       Completed: read failure       90%      2622         6298711

Note: selective self-test log revision number (0) not 1 implies that no selective self-test has ever been run
SMART Selective self-test log data structure revision number 0
Note: revision number not 1 implies that no selective self-test has ever been run
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Completed_read_failure [90% left] (0-65535)
    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.
(756 errors, but it only will show 5 of them)

#7 Artrooks

Artrooks

  • Members
  • 1,463 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New York
  • Local time:12:56 PM

Posted 09 December 2012 - 04:41 PM

Hello,

From GSmartControl:

193 Load_Cycle_Count 0x0032 001 001 050 Old_age Always FAILING_NOW 3653391 <======


From SAMSUNG HM250HI (page 16)

RELIABILITY SPECIFICATIONS:
Non-recoverable Read Error 1 sector in 10 to the14 bits
Controlled Ramp Load/Unload 600,000 <=====


The Load Cycle Count is the number of times the heads are parked then activated on the drive. Notebook computers unload the heads more frequently than do desktops to prevent drive damage due to the mobile nature of the laptop computer. (reference)

Is the drive toast? While I can't say for sure, I suspect that it is. I personally wouldn't trust it in a computer that I relied on.

Regards,
Brooks



 


#8 millipede

millipede
  • Topic Starter

  • Members
  • 614 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:outer space
  • Local time:11:56 AM

Posted 09 December 2012 - 05:33 PM

Thanks. I tried formatting it and installing ubuntu but haven't had any luck getting it to load yet. Not really rushing getting it working at the moment as I don't have a ton of hope for that drive anyway...
Good news, maybe, someone is giving me a laptop today... a used/broken one. Best Buy told them it would cost too much to fix it, that was a year ago, so they bought a new one. It's been sitting under their bed for the past year... is only 3 years old so it might have some useful parts in it. We'll see.

This has been extra frustrating because we have 2 laptops that 2 or our kids use for school work.(homeschooled) and my wife has become addicted to ebay and ravelry(she LOOKS at knitting FAR more than she does any) and she keeps borrowing computers from the kids when they should be doing their work. :/ So I do need to get something running for my wife soon... real soon. Hopefully whatever we get today will be helpful in that.

#9 millipede

millipede
  • Topic Starter

  • Members
  • 614 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:outer space
  • Local time:11:56 AM

Posted 09 December 2012 - 07:34 PM

well, nevermind that new laptop for now. No power cable... and the lady's story went from, she didn't know what was wrong with it to, Best Buy told her it needed a new motherboard. I can't even plug it in to test it out. :( bah... I suppose I can test out the hard drive and cd drive in that other laptop... too bad though, this one had 4gb of memory and that other one is just older. Had my hopes up.

#10 millipede

millipede
  • Topic Starter

  • Members
  • 614 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:outer space
  • Local time:11:56 AM

Posted 10 December 2012 - 10:48 AM

I'm about ready to shoot these computers... if only I had a gun.
I don't know where to even post at this point.
Since I was given another computer yesterday, I gave up on the hard drive that appears to be failing since I wasn't getting anywhere with it anyway. Thought to myself, foolishly, that this newer one is only three years old and it was, supposedly, the motherboard that went out on it. And for whatever stupid reason, I decided to jump right in and put ubuntu on the free space the drive had. Things looked like they were going to go smoothly... til I tried to partition that free space for ubuntu.
I don't remember, and silly me didn't write it down, the exact wording.... only that it failed and had an exit of 141... I googled that but that was anything but helpful.
Oh yeah... I told it to try again since it told me if I didn't try again, the whole installation might fail.
That didn't work. So, I chose to quit installation.
FROZEN. Sat there for an hour or more and nothing worked. I could not quit out of it or anything. I finally told it to shut down, which it did manage to do.
This morning I decided to put the hard drive in MY computer to take a look at the files and run that GSmart thing.
My computer cannot open the drive. Says it's not accessible... it was listed there... I can see a partition for recovery... but that recovery doesn't do me any good anyway with it not being in the computer it was created for.

I popped it back into the old E1505 Dell and booted ubuntu from the flash drive. It lists a 74GB device(it's a 120GB drive, not 74) and trying to open that from ubuntu results in
"Unable to mount 74 GB file system
Error mounting: mount exited with exit code 13: failed to load runlist for $MFT/$DATA etc etc etc.......

I'm wondering if I should find a way to simply format the drive at this point, if I can even do that. I'm so frustrated... I was thinking it would be interesting to view the windows installation and see what was on there. I thought to myself, who knows... maybe there's some old files on there that lady lost and I could recover them for her.
I don't know if I'm tired, hungry, or what... but I just wasn't in the mood for this, this morning....... eh... computers... :/

I don't know if all this craziness is getting confusing... I'm wondering if I should try installing ubuntu again, this time replacing the windows and formatting the drive... or... or, well I don't know. I just don't know. :(
Humbug...

#11 millipede

millipede
  • Topic Starter

  • Members
  • 614 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:outer space
  • Local time:11:56 AM

Posted 10 December 2012 - 04:38 PM

I guess we can call this topic closed... That drive with the bad sector(s), I gave up on it... and even though I had BIG problems with the newer one... I got it working. I decided this morning to put it back in and install ubuntu from the flash drive. It worked. EVERYTHING else that was on it is gone now, but it worked.

#12 rotor123

rotor123

  • Moderator
  • 8,093 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:12:56 PM

Posted 10 December 2012 - 05:17 PM

Thanks for the report on the final result

Roger

Fortune Cookie says: Fortune not Found: Abort, Retry, Ignore?

Sent from my All-In-One Desktop. Perfect for Internet, Not for heavy usage or gaming however.

How Does a computer get Infected? http://www.bleepingcomputer.com/forums/t/2520/how-did-i-get-infected/
Forum Rules,    The BC Welcome Guide

167 @ June 2015





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users