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

Windows Recovery says 'Bad Hard Drive'. How do I fix this?


  • Please log in to reply
17 replies to this topic

#1 Dipsgal

Dipsgal

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:06:09 AM

Posted 16 November 2014 - 05:15 PM

Hi

 

I was having trouble with missing files and virus infections but this is now resolved (forum post http://www.bleepingcomputer.com/forums/t/553566/metasupportdll-file-missing-cant-get-rid-of-trojans-fake-program-updates/page-2)

 

But right after I did the last step... set up a restore point, my laptop has crashed 4 times, just suddenly went black and turned off. 

 

When I re-booted it gave me the option to run the Windows Recovery which I did and the result was that it could not fix the problem. I looked at the log and it said 'Bad Hard Drive'.  Can you advise if this is something that can be fixed and if so, how?

 

My system properties are:

 

Pentium Dual Core CPU T4500 @2.30GHz

4 GB Ram

64Bit Operating System

Windows 7 Home Premium Service Pack 1

 

I looked at my system properties for my disk drive and it says Samsung HM641JI if that means anything?  There was a button to 'Update the driver' but I didn't want to do anything until you guys advise in case I make it worse. 

 

Thanks a lot

Moira



BC AdBot (Login to Remove)

 


#2 Chris Cosgrove

Chris Cosgrove

  • Moderator
  • 6,313 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Scotland
  • Local time:07:09 AM

Posted 17 November 2014 - 05:59 AM

First things first !  Just against the possibility that your hard drive is failing back up your data - work, photos, music, etc. - to external media. What you use depends on how much you have - memory sticks, DVDs or an external drive - but back it up and then you can relax, your data will be safe.

 

Then run the 'chkdsk /r' command on your computer. This will give you some idea of what the problems on your hard drive are and it will fix at least some problems.

 

To do this, if you can get your computer to boot normally, click on the 'Start' button then type 'cmd' into the search box (NOTE - all typing to be done without the ' ' quotes) and click 'search'. This will come up with a list with 'cmd.exe' right at the top of the list. RIGHT click on 'cmd.exe' and select 'Run as Administrator' from the pop-up menu. You will now get a small window appear with white text on a black background and at the end of the text a blinking white underscore.

 

Next, just type 'chkdsk /r' - note there is a space between 'chkdsk' and '/r' - and press 'Enter'. You will now get a message saying 'chkdsk cannot run, do you want to run it at next start up ? Y/N'. Type 'Y' and re-boot the computer. Chkdsk will run at start up. Make sure you have the charger connected if it is a laptop and leave it to run. This can take quite a while - up to 1 hour is  not unusual - depending on your computer and the size of the hard drive and then have a look at the report.

 

If it says problems fixed, or words to that effect, you are safe to carry on using it. If it doesn't but says you have bad sectors then make a note of the report in your next post. Better still, take a photo of the report on the screen and post that. There are other tools that can be used in this situation.

 

But, back up your data first. Hard drives are replaceable and so long as you have your data you will merely be faced with the tedium of reinstalling your OS and applications !

 

Chris Cosgrove

 

PS - It is a good idea to have your data backed up in any case.



#3 Dipsgal

Dipsgal
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:06:09 AM

Posted 17 November 2014 - 12:02 PM

Hi Chris

 

Thanks for your help.  I did the scan, but it didn't give me a report. As soon as it was finished, it automatically went to the Windows Start-up so I didn't see if it is completely fixed.  Is there a way to see the log now, through the command prompt or anything, or should I run the scan again?

 

Throughout the scan it was saying that Clusters were Fixed, but of course this doesn't give me the final result.

 

I've backed up as much as I can at the moment too  :thumbup2:

 

Let me know what you think if U should re-do the scan or there's something else I can try.

 

Many thanks

Moira



#4 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,371 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:11:09 PM

Posted 17 November 2014 - 03:18 PM

Download and run ListChkdskResult.
 
This will open Notepad with the results of the chkdsk scan.  Please copy and then paste this log in your topic.

Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#5 Dipsgal

Dipsgal
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:06:09 AM

Posted 17 November 2014 - 03:58 PM

Fabulous! Thank-you.  This is the log:

 

ListChkdskResult by SleepyDude v0.1.7 Beta | 21-09-2013
 
------< Log generate on 17/11/2014 20:57:14 >------
Category: 0
Computer Name: Moira-Laptop
Event Code: 1001
Record Number: 59912
Source Name: Microsoft-Windows-Wininit
Time Written: 11-17-2014 @ 16:54:59
Event Type: Information
User: 
Message: 
 
Checking file system on C:
The type of the file system is NTFS.
 
A disk check has been scheduled.
Windows will now check the disk.                         
 
CHKDSK is verifying files (stage 1 of 5)...
  243200 file records processed.                                         
 
File verification completed.
  1291 large file records processed.                                   
 
  0 bad file records processed.                                     
 
  0 EA records processed.                                           
 
  47 reparse records processed.                                      
 
CHKDSK is verifying indexes (stage 2 of 5)...
  311822 index entries processed.                                        
 
Index verification completed.
  0 unindexed files scanned.                                        
 
  0 unindexed files recovered.                                      
 
CHKDSK is verifying security descriptors (stage 3 of 5)...
  243200 file SDs/SIDs processed.                                        
 
Cleaning up 371 unused index entries from index $SII of file 0x9.
Cleaning up 371 unused index entries from index $SDH of file 0x9.
Cleaning up 371 unused security descriptors.
Security descriptor verification completed.
  34312 data files processed.                                           
 
CHKDSK is verifying Usn Journal...
  37572024 USN bytes processed.                                            
 
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
Read failure with status 0xc0000185 at offset 0xbc27b000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0xbc289000 for 0x1000 bytes.
Windows replaced bad clusters in file 57814
of name \Windows\Prefetch\AGGLUA~2.DB.
Read failure with status 0xc0000185 at offset 0x5e2488000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x5e248b000 for 0x1000 bytes.
Windows replaced bad clusters in file 62546
of name \Windows\RtlExUpd.dll.
Read failure with status 0xc0000185 at offset 0x484bdf000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x484bdf000 for 0x1000 bytes.
Windows replaced bad clusters in file 64732
of name \PROGRA~1\Samsung\SAMSUN~1\SAMSUN~4\SAMSUN~1\thumnail\SC4D0B~1.JPG.
Read failure with status 0xc0000185 at offset 0x6bbbba000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x6bbbc1000 for 0x1000 bytes.
Windows replaced bad clusters in file 74762
of name \Windows\winsxs\AM425A~1.172\F12.dll.
Read failure with status 0xc0000185 at offset 0x5b44c5000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x5b44d2000 for 0x1000 bytes.
Windows replaced bad clusters in file 76006
of name \Users\Moira\Desktop\BURNNO~1\BUEB61~1.AVI.
Read failure with status 0xc0000185 at offset 0x5b757f000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x5b7582000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x5b7673000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x5b7679000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x5b789a000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x5b789a000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x5b798b000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x5b7991000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x5c3172000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x5c317f000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x5ca0c0000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x5ca0c8000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x5ca1b9000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x5ca1bf000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x5ca2b0000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x5ca2b6000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x5cd867000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x5cd86c000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x5cd95d000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x5cd963000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x5e1794000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x5e1799000 for 0x1000 bytes.
Windows replaced bad clusters in file 76007
of name \Users\Moira\Desktop\BURNNO~1\BUC8CB~1.AVI.
Read failure with status 0xc0000185 at offset 0x65c8e8000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x65c8f3000 for 0x1000 bytes.
Windows replaced bad clusters in file 76132
of name \Users\Moira\DOWNLO~1\NETLOA~1.100\OLB4CF~1.PAR.
Read failure with status 0xc0000185 at offset 0x6b8b0c000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x6b8b11000 for 0x1000 bytes.
Windows replaced bad clusters in file 83953
of name \PROGRA~2\MICROS~3\CLIPART\PUB60COR\NA01368_.WMF.
Read failure with status 0xc0000185 at offset 0x522cb0000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x522cbf000 for 0x1000 bytes.
Windows replaced bad clusters in file 89651
of name \Windows\INSTAL~1\$PATCH~1\Managed\000021~1\12.0.4518\XIMAGE3B.DLL.
Read failure with status 0xc0000185 at offset 0x46884a000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x46884e000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x468a6f000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x468a73000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x468c64000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x468c65000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x46af66000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x46af6f000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x46b570000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x46b578000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x46b769000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x46b76a000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x46b85b000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x46b863000 for 0x1000 bytes.
Windows replaced bad clusters in file 117687
of name \PROGRA~3\MICROS~1\OEMOFF~1\OStarter\fr-fr\CONSUM~1.SFT.
Read failure with status 0xc0000185 at offset 0xbbf4f000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0xbbf59000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0xbc04a000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0xbc058000 for 0x1000 bytes.
Windows replaced bad clusters in file 137274
of name \Windows\winsxs\WOE4F1~1.175\explorer.exe.
Read failure with status 0xc0000185 at offset 0x5e257f000 for 0xc000 bytes.
Read failure with status 0xc0000185 at offset 0x5e2582000 for 0x1000 bytes.
Windows replaced bad clusters in file 172314
of name \Windows\INSTAL~1\$PATCH~1\Managed\BE4EBE~1\4.5.50938\NORMNF~1.
Read failure with status 0xc0000185 at offset 0xacbd6000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0xacbd6000 for 0x1000 bytes.
Windows replaced bad clusters in file 196260
of name \Users\Moira\Desktop\SGW\IMG_47~4.JPG.
Read failure with status 0xc0000185 at offset 0x6badce000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x6badd8000 for 0x1000 bytes.
Windows replaced bad clusters in file 199574
of name \Users\Moira\Desktop\NEWKIN~1\MATTER~2.MOB.
Read failure with status 0xc0000185 at offset 0xb5d0e000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0xb5d10000 for 0x1000 bytes.
Windows replaced bad clusters in file 204591
of name \Windows\winsxs\X83B6E~1.175\themecpl.dll.
Read failure with status 0xc0000185 at offset 0xac998000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0xac9a5000 for 0x1000 bytes.
Windows replaced bad clusters in file 207869
of name \Users\Moira\AppData\Roaming\Adobe\FLASHP~1\NATIVE~1\497C8D~1\8d2d7de\plugin.vch.
Read failure with status 0xc0000185 at offset 0xbc67f000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0xbc683000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0xbc774000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0xbc781000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0xbc9b2000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0xbc9b3000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0xbcaa4000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0xbcab1000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0xbcba2000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0xbcbb0000 for 0x1000 bytes.
Windows replaced bad clusters in file 218591
of name \Windows\INSTAL~1\4f95edd.msp.
Read failure with status 0xc0000185 at offset 0xaa805000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0xaa806000 for 0x1000 bytes.
Windows replaced bad clusters in file 220098
of name \Windows\winsxs\AM7D79~1.164\VGX.dll.
  243184 files processed.                                                
 
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
  16671201 free clusters processed.                                        
 
Free space verification is complete.
Adding 39 bad clusters to the Bad Clusters File.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.
 
 187695103 KB total disk space.
 120519588 KB in 170173 files.
    135552 KB in 34313 indexes.
       216 KB in bad sectors.
    354943 KB in use by the system.
     65536 KB occupied by the log file.
  66684804 KB available on disk.
 
      4096 bytes in each allocation unit.
  46923775 total allocation units on disk.
  16671201 allocation units available on disk.
 
Internal Info:
00 b6 03 00 d1 1e 03 00 7e a5 05 00 00 00 00 00  ........~.......
50 06 00 00 2f 00 00 00 00 00 00 00 00 00 00 00  P.../...........
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.
 
-----------------------------------------------------------------------
Category: 0
Computer Name: Moira-Laptop
Event Code: 26214
Record Number: 54900
Source Name: Chkdsk
Time Written: 10-06-2014 @ 17:28:48
Event Type: Information
User: 
Message: Chkdsk was executed in read/write mode.  
 
Checking file system on E:
Volume label is SAMSUNG.
 
CHKDSK is verifying files (stage 1 of 3)...
Attribute record of type 0xa0 and instance tag 0x4 is cross linked
starting at 0x84a0213 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0xa0 and instance tag 0x4
in file 0xdb is already in use.
Deleting corrupt attribute record (160, $I30)
from file record segment 219.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0xa285058 for possibly 0x540a1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0xec is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 236.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0xa2d90f9 for possibly 0x52960 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0xed is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 237.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x65b2644 for possibly 0x4af32 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x351 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 849.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0xa3541c8 for possibly 0x3cd9f clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x563 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 1379.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x9dc0000 for possibly 0xd54e clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x58e is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 1422.
  7424 file records processed.                                         
 
File verification completed.
  0 large file records processed.                                   
 
  0 bad file records processed.                                     
 
  0 EA records processed.                                           
 
  0 reparse records processed.                                      
 
CHKDSK is verifying indexes (stage 2 of 3)...
The index bitmap for index $I30 in file 0xdb is invalid or missing.
Correcting error in index $I30 for file 219.
The index bitmap $I30 is present but there is no corresponding
index allocation attribute in file 0xdb.
Correcting error in index $I30 for file 219.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff be b0 c6 26 79 12 3f d6  ÿÿÿÿÿÿÿÿ¾.Æ&y.?Ö
81 09 00 00 00 00 01 00 53 2b a8 04 bc fc 92 47   ......S+¨..üG
Sorting index $I30 in file 219.
  8368 index entries processed.                                        
 
Index verification completed.
CHKDSK is scanning unindexed files for reconnect to their original directory.
Recovering orphaned file ATTACK~1.MKV (220) into directory file 219.
Recovering orphaned file Attack on Titan (Shingeki no Kyojin) S01E01 To You, Two Thousand Years Later (Dual Audio) (1920x1080) [Phr0stY].mkv (220) into directory file 219.
Recovering orphaned file ATTACK~2.MKV (221) into directory file 219.
Recovering orphaned file Attack on Titan (Shingeki no Kyojin) S01E02 That Day (Dual Audio) (1920x1080) [Phr0stY].mkv (221) into directory file 219.
Recovering orphaned file ATTACK~3.MKV (222) into directory file 219.
Recovering orphaned file Attack on Titan (Shingeki no Kyojin) S01E03 A Dull Light in Despair (Dual Audio) (1920x1080) [Phr0stY].mkv (222) into directory file 219.
Recovering orphaned file ATTACK~4.MKV (223) into directory file 219.
Recovering orphaned file Attack on Titan (Shingeki no Kyojin) S01E04 Night of the Disbanding (Dual Audio) (1920x1080) [Phr0stY].mkv (223) into directory file 219.
Recovering orphaned file ATC6E9~1.MKV (224) into directory file 219.
Recovering orphaned file Attack on Titan (Shingeki no Kyojin) S01E05 First Battle (Dual Audio) (1920x1080) [Phr0stY].mkv (224) into directory file 219.
Recovering orphaned file AT1BAD~1.MKV (225) into directory file 219.
Recovering orphaned file Attack on Titan (Shingeki no Kyojin) S01E06 The World She Saw (Dual Audio) (1920x1080) [Phr0stY].mkv (225) into directory file 219.
Recovering orphaned file AT536E~1.MKV (226) into directory file 219.
Recovering orphaned file Attack on Titan (Shingeki no Kyojin) S01E07 A Small Blade (Dual Audio) (1920x1080) [Phr0stY].mkv (226) into directory file 219.
Recovering orphaned file AT85D0~1.MKV (227) into directory file 219.
Recovering orphaned file Attack on Titan (Shingeki no Kyojin) S01E08 I Can Hear a Heartbeat (Dual Audio) (1920x1080) [Phr0stY].mkv (227) into directory file 219.
Recovering orphaned file ATF5F4~1.MKV (228) into directory file 219.
Recovering orphaned file Attack on Titan (Shingeki no Kyojin) S01E09 The Whereabouts of His Left Arm (Dual Audio) (1920x1080) [Phr0stY].mkv (228) into directory file 219.
Recovering orphaned file AT7728~1.MKV (229) into directory file 219.
Recovering orphaned file Attack on Titan (Shingeki no Kyojin) S01E10 Answer (1920x1080) [Phr0stY].mkv (229) into directory file 219.
Recovering orphaned file AT3B19~1.MKV (230) into directory file 219.
Recovering orphaned file Attack on Titan (Shingeki no Kyojin) S01E11 Idol (Dual Audio) (1920x1080) [Phr0stY].mkv (230) into directory file 219.
Recovering orphaned file AT2B1C~1.MKV (231) into directory file 219.
Recovering orphaned file Attack on Titan (Shingeki no Kyojin) S01E12 WOUND (Dual Audio) (1920X1080) [Phr0stY].mkv (231) into directory file 219.
Recovering orphaned file AT4DF6~1.MKV (232) into directory file 219.
Recovering orphaned file Attack on Titan (Shingeki no Kyojin) S01E13 Basic Needs (Dual Audio) (1920x1080) [Phr0stY].mkv (232) into directory file 219.
Recovering orphaned file AT71B4~1.MKV (233) into directory file 219.
Recovering orphaned file Attack on Titan (Shingeki no Kyojin) S01E14 Can't Look into His Eyes (Dual Audio) (1920x1080) [Phr0stY].mkv (233) into directory file 219.
Recovering orphaned file ATE439~1.MKV (234) into directory file 219.
Recovering orphaned file Attack on Titan (Shingeki no Kyojin) S01E15 Special Ops Squad (Dual Audio) (1920x1080) [Phr0stY].mkv (234) into directory file 219.
Recovering orphaned file AT63DD~1.MKV (235) into directory file 219.
Recovering orphaned file Attack on Titan (Shingeki no Kyojin) S01E16 What Should Be Done (Dual Audio) (1920x1080) [Phr0stY].mkv (235) into directory file 219.
Recovering orphaned file AT1CB7~1.MKV (236) into directory file 219.
Recovering orphaned file Attack on Titan (Shingeki no Kyojin) S01E17 Female Titan (Dual Audio) (1920x1080) [Phr0stY].mkv (236) into directory file 219.
Recovering orphaned file AT6EA1~1.MKV (237) into directory file 219.
Recovering orphaned file Attack on Titan (Shingeki no Kyojin) S01E18 Forest of Giant Trees (Dual Audio) (1920x1080) [Phr0stY].mkv (237) into directory file 219.
Recovering orphaned file AT1D3C~1.MKV (238) into directory file 219.
Recovering orphaned file Attack On Titan (Shingeki no Kyojin) S01E19 Bite (Dual Audio) (1902x1080) [Phr0stY].mkv (238) into directory file 219.
Recovering orphaned file ATBFC3~2.MKV (245) into directory file 219.
Recovering orphaned file Attack on Titan (Shingeki no Kyojin) S01E20 Erwin Smith (Dual Audio) (1920x1080) [Phr0stY].mkv (245) into directory file 219.
Recovering orphaned file AT7CD5~2.MKV (247) into directory file 219.
Recovering orphaned file Attack on Titan (Shingeki no Kyojin) S01E21 Crushing Blow (Dual Audio) (1920x1080) [Phr0stY].mkv (247) into directory file 219.
Recovering orphaned file ATE2F7~2.MKV (248) into directory file 219.
Recovering orphaned file Attack on Titan (Shingeki no Kyojin) S01E22 The Defeated (Dual Audio) (1920x1080) [Phr0stY].mkv (248) into directory file 219.
Recovering orphaned file ATF871~2.MKV (249) into directory file 219.
Recovering orphaned file Attack on Titan (Shingeki no Kyojin) S01E23 Smile (Dual Audio) (1920x1080) [Phr0stY].mkv (249) into directory file 219.
Recovering orphaned file ATA162~2.MKV (250) into directory file 219.
Recovering orphaned file Attack on Titan (Shingeki no Kyojin) S01E25 Wall (Dual Audio) (1920x1080) [Phr0stY].mkv (250) into directory file 219.
Recovering orphaned file ARROWS~1.MP4 (1373) into directory file 180.
Recovering orphaned file Arrow.S02E14.HDTV.x264-LOL.mp4 (1373) into directory file 180.
 
Recovering orphaned file THETOM~3.MP4 (1430) into directory file 940.
Recovering orphaned file The.Tomorrow.People.US.S01E01.HDTV.x264-LOL.mp4 (1430) into directory file 940.
CHKDSK is recovering remaining unindexed files.
 
CHKDSK is verifying security descriptors (stage 3 of 3)...
  7424 file SDs/SIDs processed.                                        
 
Cleaning up 16 unused index entries from index $SII of file 0x9.
Cleaning up 16 unused index entries from index $SDH of file 0x9.
Cleaning up 16 unused security descriptors.
Security descriptor verification completed.
Inserting data attribute into file 236.
Inserting data attribute into file 237.
Inserting data attribute into file 849.
Inserting data attribute into file 1379.
Inserting data attribute into file 1422.
  478 data files processed.                                           
 
CHKDSK is verifying Usn Journal...
The remaining of an USN page at offset 0x7bcb8 in file 0x85
should be filled with zeros.
The remaining of an USN page at offset 0x4b9000 in file 0x85
should be filled with zeros.
Repairing Usn Journal file record segment.
  4961328 USN bytes processed.                                            
 
Usn Journal verification completed.
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.
 
 976751967 KB total disk space.
 687902484 KB in 6476 files.
      3176 KB in 475 indexes.
    108315 KB in use by the system.
     65536 KB occupied by the log file.
 288737992 KB available on disk.
 
      4096 bytes in each allocation unit.
 244187991 total allocation units on disk.
  72184498 allocation units available on disk.
 
-----------------------------------------------------------------------


#6 Chris Cosgrove

Chris Cosgrove

  • Moderator
  • 6,313 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Scotland
  • Local time:07:09 AM

Posted 17 November 2014 - 08:02 PM

Reading that log file there certainly were errors on your hard drive, but most of them appear to have been fixed and the bad sectors isolated and routed around. Because of the tolerances involved all hard drives, including brand new ones, have problem sectors.

 

Unless I am mistaken you can carry on using that hard drive quite happily. I would not at this stage use the Seagate tools because they can put a lot of stress on a drive. If DC3 wishes to disagree with me I will have no objection - I freely admit I don't know it all. But you do need to be aware that hard drives can, do and will fail - sooner or later. The best protection against this is to carry out a regular back up policy to somewhere other than that hard drive.

 

By this I mean don't use a second partition on that hard drive, use  - as I said above - memory sticks, DVDs or an external hard drive. This means that someday when the hard drive does die, should you still own the computer then, it is merely a matter of fitting a new hard drive and re-installing all your applications and OS. It also means that if you buy another computer while this one is still working you don't have to sweat about copying all your data off it in one session - you will have virtually all of it in your back ups.

 

Chris Cosgrove



#7 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,371 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:11:09 PM

Posted 18 November 2014 - 11:08 AM

If you are using the long generic test I would agree with the statement that the scan is stressful as it takes upwards of four hours to run and makes repairs.  But the short generic test takes between 20 to 90 seconds to run, as I understand it, this is not a stressful test.  But then... I don't know everything. :whistle:


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#8 Dipsgal

Dipsgal
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:06:09 AM

Posted 18 November 2014 - 11:16 AM

:lol:

 

Whatever you guys recommend, I'm happy to do... guessing the short generic test may be the way to go and won't do any harm?



#9 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,371 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:11:09 PM

Posted 18 November 2014 - 11:21 AM

I would go ahead and run the short generic test.


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#10 Dipsgal

Dipsgal
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:06:09 AM

Posted 18 November 2014 - 12:10 PM

Cool!

 

Can either of you tell me how to do that though?  :grinner:



#11 Chris Cosgrove

Chris Cosgrove

  • Moderator
  • 6,313 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Scotland
  • Local time:07:09 AM

Posted 18 November 2014 - 06:39 PM

Yes, it's fairly easy if you have the means too create a CD or you can run it from a memory stick if your BIOS will boot from a memory stick.

 

first of all you need to download Seagate's 'Tools for DOS' from here -

 

http://www.seagate.com/gb/en/support/downloads/item/seatools-dos-master/

 

This file downloads as an .ISO file which needs to be unpacked into its component files before you can use it. I have been told that the disc burner built into Windows can unpack these but I always use ImageBurn, which is a free download from -

 

http://www.imgburn.com/

 

Once you have the CD - which is self-booting - all you have to do is power up your computer, open the CD drawer and put the disc in then re-boot the computer. It will now start from the CD and all you have to do is follow the on-screen prompts. Once you have run the short test you have a period in which you can study the results before it goes into the long test. If you are using a memory stick, so long as your BIOS is set to read a memory stick (External USB in BIOS) before the hard drive it is even simpler. With the computer off, put the memory stick in a slot and start the computer !

 

Any problems, post back. And, I make no apologies for this - I cannot emphasize it enough - back up your data first !  What I tell you three times is true !

 

Chris Cosgrove



#12 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,371 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:11:09 PM

Posted 19 November 2014 - 08:51 AM

There is a Windows application which can be used to burn the ISO to a disc.  I had been using ImgBurn to do this until I discovered that in Windows 7 and 8 using the Windows Burn Disk.  Not only do you not need to download another program, I find it to be easier.

 

How to burn ISO image using Windows Burn Disk Image.
 
Notice:  This applies only to Windows 7 and Windows 8, earlier versions do not have this.  
 
1.  Place a blank CD or DVD in the tray of your optical drive and close the tray.
 
2.  After you have downloaded the ISO image you want to burn right click on the Start orb, then choose Windows Explorer.
 
3.  When Explorer opens click on Downloads in the left pane.  Scroll down till you find the ISO file you want and double click on it.  Click on Burn Disk Image.
 
4.  In the image below you will see Disk burner:, this should be set to the optical drive you want to use.  Click on Verify disc after burning if you want to Windows to verity the disc image after burn.  Click on burn.
 
burndiskimage1_zpsb502b181.png
 
5.  In the image below you can see that the green progress bar, when the image is finished burning the bar will be filled.
 
burndiskimage2_zps17a9d6ff.png
 
6.  After the image has completed being burned click on Close

Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#13 Dipsgal

Dipsgal
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:06:09 AM

Posted 19 November 2014 - 09:31 AM

Slight problem! My disk drive is broken... I dropped my laptop about 6 months ago. I know, total  :o  moment, but as I never use my disk drive, as everything is USB I didn't bother getting it fixed.



#14 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,371 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:11:09 PM

Posted 19 November 2014 - 10:18 AM

You can use a flash drive to run the SeaTool for DOS, but the hdd would needs to be a Seagate in order to run it.  You can find instructions for this here

 

SeaTools for DOS will run on all manufacturer's hard drives, but may not recognize the hard drive if the Storage Configuration is not set in a configuration which SeaTools will recognize.

 

If the motherboard has a Intel SATA controller the storage configuration for SATA must be set to AHCI.  If you need to change the configuration this will have to be done in the BIOS.
 
If the mohterboard has a Marvel SATA controller the storage configuration for SATA must be set to IDE.
 
To determined how your storage is configured open the Device Manager and click on IDE ATA/ATAPI controllers.This will expand the tree allowing you to see your storage configuration.
 
For Non Seatools hdds you can perform the Short Drive Self Test, Short Generic Test, and Long Generic Test.  This is why I suggested the SeaTools for Windows.

Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#15 Chris Cosgrove

Chris Cosgrove

  • Moderator
  • 6,313 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Scotland
  • Local time:07:09 AM

Posted 19 November 2014 - 06:09 PM

Thanks for the instructions on using the Windows feature, DC3. As I said, I had heard it was possible but like you I had always used ImageBurn. I'll give it a try next time I want to create something from an ISO file.

 

Chris Cosgrove






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users