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

drive image cloning after hard disk damage


  • Please log in to reply
6 replies to this topic

#1 necrophyte

necrophyte

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:09:57 PM

Posted 13 September 2011 - 09:07 AM

ive been experiencing strange behavior and reduced performance on my notebook (hp envy 17 3d) since a few weeks, and first suspected some malware, but after having checked that thoroughly and, at least temporarily fixed the rather minor problems (my thread in the security forums), i analysed the issues inside the windows event viewer and saw that theyre probably hardware-related.

i first suspected the memory, since i put in 2 new 4096mb kingston ram 2 months ago, but all memory tests (inside windows and bios & uefi) reported no memory issues. then the only option left was to check my hard disk, and this revealed some major problems.

the hp uefi hard disk diagnostics stopped the short DST test with the failure ID: Q0BU39-5HL5PX-XD0141-60R903 on hard disk 1.

my first chkdsk /r attempt lasted too long while attempting to repair one file on c:/, so i restarted and installed a trial version of Active Hard Disk Monitor 3, which showed me the SMART info of my drive (this info is the present one showed while posting this thread):

Device TOSHIBA MK5061GSYN SMART Info (ID/Value/Raw Value/Worst/Treshold)
1 100 0 99 50
2 100 0 100 50
3 100 2385 100 2
4 100 549 100 0
5 90 211 90 10
7 100 0 100 50
8 100 0 100 50
9 95 2381 95 0
10 110 0 100 30
12 100 544 100 0
183 100 0 100 1
184 100 0 100 97
185 100 65535 100 1
187 1 16138 1 0
188 100 14 98 0
189 100 0 100 1
190 61 774176807 50 40
191 100 8 100 0
192 100 458759 100 0
193 96 47930 96 0
196 100 183 100 0
197 100 1579 100 0
199 200 0 200 0
------------------------

#1,2,3,7,8,184,196,197 all are fully green @ 100%
#5 (reallocated sector count) is @ 90%
#10 (spinup retry count) is @ 55%
the others dont have any status bars.

the hard disk work time is only 3 months and 9 days.

then i ran the disk scan in this software which showed several bad sectors.

after that i did a chkdsk /i /c /r, which did several actions ("deleting corrupt attribute record (128, "") from ... file segment #). then i let the full chkdsk /r scan during the whole night, which finally finished today.
here is the log from the event viewer:

Level,Date and Time,Source,Event ID,Task Category
Information,13.09.2011 12:19:37,Microsoft-Windows-Wininit,1001,None,"

Checking file system on E:
The type of the file system is NTFS.
Volume label is Data.

A disk check has been scheduled.
Windows will now check the disk.                         

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

File verification completed.
  8 large file records processed.                                   

  0 bad file records processed.                                     

  0 EA records processed.                                           

  0 reparse records processed.                                      

CHKDSK is verifying indexes (stage 2 of 5)...
  42514 index entries processed.                                        

Index verification completed.
  0 unindexed files scanned.                                        

  0 unindexed files recovered.                                      

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

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

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

Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
Read failure with status 0xc0000185 at offset 0x6387fe000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x638800000 for 0x2000 bytes.
Read failure with status 0xc0000185 at offset 0x6389f2000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x6389fa000 for 0x2000 bytes.
Windows replaced bad clusters in file 9527
of name \dl data\REDSON~1.ES_\VIDEO_TS\VTS_02_0.VOB.
Read failure with status 0xc0000185 at offset 0x638cb8000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x638cbe000 for 0x2000 bytes.
Read failure with status 0xc0000185 at offset 0x639a24000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x639a2a000 for 0x2000 bytes.
Read failure with status 0xc0000185 at offset 0x639ce6000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x639cee000 for 0x2000 bytes.
Windows replaced bad clusters in file 14206
of name \Data\mp3\DA4132~1.MP3.
Read failure with status 0xc0000185 at offset 0x639e3e000 for 0x10000 bytes.
  40688 files processed.                                                

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

Free space verification is complete.
Adding 435 bad clusters to the Bad Clusters File.
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.

 236726271 KB total disk space.
 161277664 KB in 38956 files.
     15328 KB in 907 indexes.
     93656 KB in bad sectors.
    110607 KB in use by the system.
     65536 KB occupied by the log file.
  75229016 KB available on disk.

      8192 bytes in each allocation unit.
  29590783 total allocation units on disk.
   9403627 allocation units available on disk.

Internal Info:
00 9f 00 00 c3 9b 00 00 6b cf 00 00 00 00 00 00  ........k.......
8d 05 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 00 00 00  ................
"
Information,13.09.2011 12:19:33,Microsoft-Windows-Wininit,1001,None,"

Checking file system on D:
The type of the file system is NTFS.
Volume label is Apps.

A disk check has been scheduled.
Windows will now check the disk.                         

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

File verification completed.
  3 large file records processed.                                   

  0 bad file records processed.                                     

  0 EA records processed.                                           

  0 reparse records processed.                                      

CHKDSK is verifying indexes (stage 2 of 5)...
  45844 index entries processed.                                        

Index verification completed.
  0 unindexed files scanned.                                        

  0 unindexed files recovered.                                      

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

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

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

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

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

Free space verification is complete.
Windows has checked the file system and found no problems.

 167772159 KB total disk space.
  85321288 KB in 31739 files.
     18008 KB in 3980 indexes.
         8 KB in bad sectors.
    106687 KB in use by the system.
     65536 KB occupied by the log file.
  82326168 KB available on disk.

      8192 bytes in each allocation unit.
  20971519 total allocation units on disk.
  10290771 allocation units available on disk.

Internal Info:
00 94 00 00 93 8b 00 00 1e ed 00 00 00 00 00 00  ................
70 00 00 00 00 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  ................
"
Information,13.09.2011 12:19:31,Microsoft-Windows-Wininit,1001,None,"

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)...
  157952 file records processed.                                         

File verification completed.
  429 large file records processed.                                   

  0 bad file records processed.                                     

  2 EA records processed.                                           

  44 reparse records processed.                                      

CHKDSK is verifying indexes (stage 2 of 5)...
  206664 index entries processed.                                        

Index verification completed.
  0 unindexed files scanned.                                        

  0 unindexed files recovered.                                      

CHKDSK is verifying security descriptors (stage 3 of 5)...
  157952 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.
  24357 data files processed.                                           

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

Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
Read failure with status 0xc0000185 at offset 0x11aaef3000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x11aaef4000 for 0x1000 bytes.
Windows replaced bad clusters in file 8696
of name \NBRT\VirusDef\20110831.002\virscan7.dat.
Read failure with status 0xc0000185 at offset 0x12d4a28000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12d4adf000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12d4adf000 for 0x1000 bytes.
Windows replaced bad clusters in file 15256
of name \Users\marko\Desktop\janmar\ei\IMG_0071.MOV.
Read failure with status 0xc0000185 at offset 0x119db71000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x119db7b000 for 0x1000 bytes.
Windows replaced bad clusters in file 67708
of name \PROGRA~1\SYNAPT~1\SynTP\SynCntxt.rtf.
Read failure with status 0xc0000185 at offset 0x119b154000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x119b159000 for 0x1000 bytes.
Windows replaced bad clusters in file 68202
of name \Windows\System32\DRIVER~1\FILERE~1\SYNPD~4.INF\SynCntxt.rtf.
Read failure with status 0xc0000185 at offset 0x12b1c50000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12b1c51000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12b1d12000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12b1d1b000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12b1ddc000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12b1de5000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12b1f96000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12b1fa0000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12b22c1000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12b22c8000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12b2549000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12b254e000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12b260f000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12b2618000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12b26d9000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12b26e2000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12b27a3000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12b27ac000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12b2d4d000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12b2d59000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12b2e1a000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12b2e23000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12b2ee4000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12b2eed000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12b316e000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12b3173000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12b3234000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12b323d000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12b32fe000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12b3307000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12b33c8000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12b33d1000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12b3492000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12b349b000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12b355c000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12b3565000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12b38a6000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12b38b4000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12b3a45000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12b3a49000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12b3b0a000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12b3b13000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12b3d94000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12b3d98000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12b3e59000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12b3e62000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1503000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c150d000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c150e000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c150e000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c150f000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c150f000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1510000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1510000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1511000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1511000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1512000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c151f000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1590000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1599000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c159a000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c159a000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c159b000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c159b000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c159c000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c159c000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c159d000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c159d000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c159e000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c159e000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c15df000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c15e7000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c15e8000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c15e8000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1669000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1671000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1672000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1672000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1673000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1673000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1674000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1674000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1675000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1675000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1676000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1676000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c16b7000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c16bb000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c16bc000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c16bc000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c16bd000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c16bd000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c16be000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c16be000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c173f000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c174e000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c174f000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c174f000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1750000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1750000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1751000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1751000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1752000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1752000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1753000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1753000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1754000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1754000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1755000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1755000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1756000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1756000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1757000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1757000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1758000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1758000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1759000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1759000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c175a000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c175a000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c176b000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c176c000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c176d000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c176d000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c176e000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c176e000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c176f000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c176f000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1770000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1770000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1771000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1771000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1772000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1772000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1773000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1773000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1774000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1774000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1795000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c17a2000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1863000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c186b000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c192c000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1934000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c19f5000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c19fd000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1abe000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1ac7000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1b88000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1b90000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1d41000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1d4b000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1e0c000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1e15000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1ed6000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1ede000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1f9f000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c1fa8000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c2069000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c2071000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c2132000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c213b000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c22ec000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c22f6000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c23b7000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c23c0000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c2481000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c248a000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c254b000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c2553000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c2614000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c261d000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c26de000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x12c26e7000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x12c2898000 for 0x10000 bytes.
Read"

after that i called HP support and asked about the warranty and they immediately accepted the case and told me they were gonnna send me a new hard disk (i had to give them the errors from the bios hard disk tests, which both stopped @ 14% - hard disk 1 quick (303), hard disk 1 full (305) and hard disk smart passed - to accept a warranty case and send me the new disk).

now i would like to buy a seagate momentus xt 500gb (my present toshiba MK5061GSYN has 500gb, too) and clone the present hard disk image to the seagate, and then use the toshiba replacement drive thet hp will send me as a backup drive (the envy 17 has 2 hd bays).

so my question is, is it safe to clone this drive with the errors/repairs from chkdsk?
the files where bad sectors were replaced arent any system files, so if these are all files that were affected, this isnt a problem for me at all.
the d:/ partition is my partition with all apps on it, and this partition hasnt got any errors.
i already looked at one file (IMG_0071.MOV) from the c:/ partition, and the video can be played, but stopps somewhere in the middle, but thats no problem since i have a backup of my iphone and the files are still on the iphone as well. the other files listed arent important. i checked the folders of the files affected, and the folder where the iphone video is located is one full of pics & vids from my iphone, and the thumbnails may take some time (much longer than before these issues) to show a preview of the pics/vids, but all can be opened and there is no corruption, except this one video file (IMG_0071.MOV).

which software should i use to clone the drive?
i will also first make a backup of all important files on an external drive (if no clone is possible and/or a fresh OS install is necessary). if some of the files cannot be copied (using the usual way in windows explorer), which software should i try to copy them with then?



thank you very much!



my system specs:

hp envy 17 3d notebook
windows 7 ultimate 64bit
intel i7-720qm
ati mobility radeon 5850
8gb pc3-10700 ram
toshiba MK5061GSYN 500gb 7200rpm drive

BC AdBot (Login to Remove)

 


#2 abauw

abauw

  • Members
  • 951 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Kebun Kelapa
  • Local time:02:57 AM

Posted 13 September 2011 - 10:16 AM

so my question is, is it safe to clone this drive with the errors/repairs from chkdsk?


As long you could clone it it's safe to clone it except your hardrive contains a virus / trojan / malware. Clone process just moving your data not Bad Sector from your Hardrive.

:guitar: Take me to a place where time is frozen
You don't have to close your eyes to dream :busy:
You can find escape inside this moment :smash:
And I will follow  :whistle:


#3 necrophyte

necrophyte
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:09:57 PM

Posted 13 September 2011 - 10:35 AM

yes, i know (and the disk is absolutely malware-free), but what i wanted to make sure is whether i could rely on that that the files reported above form the chkdsk log were the only ones affected by bad sectors, or is there a chance that more files are affected which werent reported in the log. if so, and these files are too many or some of them are critical system files (ok, sfc could solve this afterwards, but still..), i may reconsider cloning the drive, since, as i can see with this video file, the files affected arent usable anymore.

#4 necrophyte

necrophyte
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:09:57 PM

Posted 13 September 2011 - 02:05 PM

also, shall i try to run chkdsk /r another night (or maybe another tool - which one? - that could repair/reallocate bad sectors)? it seems like the damage was a physical one, although theres no strange noise etc., but i really experience very reduced performance while eg. opening windows explorer windows or a browser or copying data to an external drive.

Edited by necrophyte, 13 September 2011 - 02:06 PM.


#5 AustrAlien

AustrAlien

    Inquisitor


  • BC Advisor
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:05:57 AM

Posted 14 September 2011 - 12:58 AM

shall i try to run chkdsk /r another night (or maybe another tool - which one? - that could repair/reallocate bad sectors)?

No, do not do that.

The first thing you should do is to clone the hard drive to another known good hard drive. You have been very lucky to date, but I suggest that you don't push your luck too much further. Edit: I recommend that you do not even attempt to boot to the Windows system again ... before cloning the hard drive.

See the following guide for further information and cautions to observe:
DjLizard's data recovery guide

Please have a look through the very recent thread at the following link to see a successful result of cloning a failing hard drive using the recommended method:
http://www.bleepingcomputer.com/forums/topic408466.html

Let me know if you would like some assistance.

Edited by AustrAlien, 14 September 2011 - 01:22 AM.

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#6 necrophyte

necrophyte
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:09:57 PM

Posted 14 September 2011 - 06:49 AM

thanks for the info!

i had one case of a phisically damaged hard disk some 5-6 years ago when a notebook fell down while running, and afterwards windows wasnt bootable and it was very difficult to copy files - but finally i managed to copy some 80-90% of my important files, many of which i had to recover using special software since they were "disappeared" because of the damages made by using chkdsk /r on that drive and deleting some folders.
so i know that letting the hard disk concerned operate after the damage is very risky, but i had to make some backups of my most important files yesterday, because i am now rather tending to a fresh OS install. i then again ran chkdsk on my c:/ drive which "only" found some 850kb of in bad sectors and again "repaired" the 3 files affected - a much better result than first time. after that i must admit that the boot time and windows explorer & browser windows opening ran MUCH smoother and faster.

now i am waiting for the already ordered seagate momentus xt (should come today or tomorrow), then i will decide whether to clone or do a fresh install. but i am quite happy since ive backed up some 200gb of files from the notebook yesterday, and only 3 files (from all 3 partitions - 2 from c:/, 1 from e:/) werent copied, and i already knew about these 3 from the chkdsk log. and since most of this data are photos, videos and music, it is very easy to recognize whether they are corrupt or not, and so far everything is perfect.

so i will report back as soon as my disk has arrived and then i will decide whether to clone this drive or just do a fresh install and copy back my backed up files.


what i would like to know now already is a suggestion for the replacement drive that HP is sending me. since i can put in both drives into my notebook, and both, the seagate momentus xt and the toshiba have 500gb, what would be the smartest way to handle them - just as 2 separate drives and then perform regular automatic synchs of important folders or maybe a raid array?

thanks!

#7 AustrAlien

AustrAlien

    Inquisitor


  • BC Advisor
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:05:57 AM

Posted 14 September 2011 - 08:58 AM

what would be the smartest way to handle them?

My opinion ... without hesitation ... would be to opt for "as 2 separate drives and then perform regular automatic synchs of important folders". RAID is not designed to be used as a safeguard for your data, and is no substitute for having a backup.

I would strongly recommend that you use something like DiscWizard to create backup images of your system drive (or entire hard drive on which the system resides) to the second hard drive on a regular basis (along with any other method that you wish for more frequent backing up of important files).

If you are using at least one of either Seagate or Western Digital branded HDDs in the system, you can take advantage of the free version of Acronis' imaging and cloning software provided by each of those manufacturers. The Acronis software can be run either from within Windows or from a bootable CD, which can be created once the utility is installed on a Windows system (and it is a wise to create this CD immediately). The bootable CD will be needed if ever the Windows system is not accessible.

Seagate: DiscWizard

Western Digital: Acronis True Image WD Edition
AustrAlien
Google is my friend. Make Google your friend too.

Posted Image




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users