CHKDSK Dellted ALL files on storage drive!

[Dark_Nemesis]

.... Soo CHDSK just viped my 3tb mass storage drive ...

 

I was backing up some data, moved a HDD from my NAS to my PC, disconnected one drive to be able to connect another drive.  Restarting my PC to get the drive I just connected to show up, and when the PC booted up CHKDSK wanted to check the drive (I didn't watch it closely enough to cancel in time). When PC booted up after running CHKDSK, the WD 3Tb I just connected, had been assigned the drive name of the drive previously connected to that SATA port. 

 

In short -> I disconnected ":1TB#1"

             -> connected ":WD3Tb"

             -> restarted the PC

             -> the 3TB drive previously named  ":WD3Tb" had now been renamed to  ":1TB#1" and the drive was empty.

 

Already tried some free data recovery tools, but to no avail. I have kept the drive disconnected since the incident.

 

 

Log file found on the drive:

 

_______________________________________________________________________________________

Checking file system on Q:

The type of the file system is NTFS.

Volume label is 1 TB # 1.

 

 

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 3)...

Attribute record of type 0x80 and instance tag 0x8 is cross linked

starting at 0xb68a9 for possibly 0x41 clusters.

Some clusters occupied by attribute of type 0x80 and instance tag 0x8

in file 0x9 is already in use.

Deleting corrupt attribute record (128, $SDS)

from file record segment 9.

  256 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)...

  276 index entries processed.                                        

 

Index verification completed.

  0 unindexed files scanned.                                        

 

  0 unindexed files recovered.                                      

 

CHKDSK is verifying security descriptors (stage 3 of 3)...

The security data stream is missing from file 0x9.

The security data stream size 0x0 should not be less than 0x40000.

Deleting an index entry with Id 256 from index $SII of file 9.

Deleting an index entry with Id 257 from index $SII of file 9.

Deleting an index entry with Id 258 from index $SII of file 9.

Deleting an index entry with Id 259 from index $SII of file 9.

Deleting an index entry with Id 260 from index $SII of file 9.

Deleting an index entry with Id 261 from index $SII of file 9.

Deleting an index entry with Id 262 from index $SII of file 9.

Deleting an index entry with Id 263 from index $SII of file 9.

Deleting an index entry with Id 264 from index $SII of file 9.

Deleting an index entry with Id 265 from index $SII of file 9.

Deleting an index entry with Id 266 from index $SII of file 9.

Deleting an index entry with Id 267 from index $SII of file 9.

Deleting an index entry with Id 268 from index $SII of file 9.

Deleting an index entry with Id 260 from index $SDH of file 9.

Deleting an index entry with Id 267 from index $SDH of file 9.

Deleting an index entry with Id 262 from index $SDH of file 9.

Deleting an index entry with Id 258 from index $SDH of file 9.

Deleting an index entry with Id 266 from index $SDH of file 9.

Deleting an index entry with Id 256 from index $SDH of file 9.

Deleting an index entry with Id 257 from index $SDH of file 9.

Deleting an index entry with Id 261 from index $SDH of file 9.

Deleting an index entry with Id 263 from index $SDH of file 9.

Deleting an index entry with Id 264 from index $SDH of file 9.

Deleting an index entry with Id 265 from index $SDH of file 9.

Deleting an index entry with Id 259 from index $SDH of file 9.

Deleting an index entry with Id 268 from index $SDH of file 9.

Replacing invalid security id with default security id for file 0.

Replacing invalid security id with default security id for file 1.

Replacing invalid security id with default security id for file 2.

Replacing invalid security id with default security id for file 6.

Replacing invalid security id with default security id for file 8.

Replacing invalid security id with default security id for file 9.

Replacing invalid security id with default security id for file 11.

Replacing invalid security id with default security id for file 24.

Replacing invalid security id with default security id for file 25.

Replacing invalid security id with default security id for file 26.

Replacing invalid security id with default security id for file 27.

Replacing invalid security id with default security id for file 29.

Replacing invalid security id with default security id for file 30.

Replacing invalid security id with default security id for file 31.

Replacing invalid security id with default security id for file 32.

Replacing invalid security id with default security id for file 33.

Replacing invalid security id with default security id for file 34.

Replacing invalid security id with default security id for file 35.

Replacing invalid security id with default security id for file 36.

  256 file SDs/SIDs processed.                                        

 

Security descriptor verification completed.

  10 data files processed.                                           

 

The MFT mirror is different from the MFT.

Correcting errors in the Master File Table (MFT) mirror.

Correcting errors in the Volume Bitmap.

Windows has made corrections to the file system.

 

   2861586 MB total disk space.

     21588 KB in 6 files.

        16 KB in 12 indexes.

         0 KB in bad sectors.

    155371 KB in use by the system.

     65536 KB occupied by the log file.

   2861414 MB available on disk.

 

      4096 bytes in each allocation unit.

 732566271 total allocation units on disk.

 732522028 allocation units available on disk.

 

Internal Info:

00 01 00 00 1d 00 00 00 1c 00 00 00 00 00 00 00  ................

01 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 00  ................

                                                   

_______________________________________________________________________________________

 

 

 

It is not a life or death situation, I have my personal stuff backed up, but a loss of 2.5Tb still stings somewhat  :wacko:

 

Any suggestions for software that (doesn't cost a fortune) that could solve this problem? Or any other possible solution?

Or should I just suck it up and reformat the drive 

 

 

Appreciate any input from you guys and girls!

Hope you all are having a nice weekend! 

 

 

 

[spaiduhz]

chkdsk reporting multiple bad entries is usually due to an interrupted shutdown while the harddrive is processing some changes, sometimes critical changes. it could also be an indicator that your hard drive may be having some critical infomation written on some sectors that has become bad.

 

before worrying about that date stored, i suggest running a utility like hdtune to check for SMART errors or bad sectors.