Corrupt Partition.... Inaccessible.

[Geforcer]

It's on a storage drive, that contains 2 partitions. Partition 2 seems fine, but partition 1 got messed pretty bad. The drive was damn near full, so when I try to run chkdsk on it, an error is given before it can finish fixing it. I still see the partition in windows (except it changed the label from Storage to Local Disk), and it won't let me open it. It happened when I did a windows update, and it asked me to reboot, so I clicked Yes. Well, I had a opened file on it when I rebooted. I can't see how that could have corrupted the whole partition though, but figured I'd throw that in for extra info. Any Ideas how I can restore this data? Thanks

C:\chkdsk /f d:
The type of the file system is NTFS.
Volume label is Storage.
Fixing critical master file table (MFT) files with MFT mirror.

CHKDSK is verifying files (stage 1 of 3)...
Deleting corrupt file record segment 0.
File record segment 4 is unreadable.
File record segment 5 is unreadable.
File record segment 6 is unreadable.
File record segment 7 is unreadable.
Deleting corrupt attribute record (128, $Bad)
from file record segment 8.
File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Correcting a minor error in file 5.
Index verification completed.
CHKDSK is creating new root directory.
CHKDSK is recovering lost files.
Recovering orphaned file $MFT (0) into directory file 5.
Recovering orphaned file $MFTMirr (1) into directory file 5.
Recovering orphaned file $LogFile (2) into directory file 5.
Recovering orphaned file $Volume (3) into directory file 5.
Correcting a minor error in file 5.
Recovering orphaned file . (5) into directory file 5.
Recovering orphaned file $Boot (7) into directory file 5.
Recovering orphaned file $BadClus (8) into directory file 5.
Recovering orphaned file $Secure (9) into directory file 5.
Recovering orphaned file $UpCase (10) into directory file 5.
Recovering orphaned file $Extend (11) into directory file 5.
Recovering orphaned file SYSTEM~1 (27) into directory file 5.
Recovering orphaned file System Volume Information (27) into directory file 5.
Recovering orphaned file RECYCLER (344) into directory file 5.
Recovering orphaned file MSOCache (369) into directory file 5.
Recovering orphaned file Music (829) into directory file 5.
Recovering orphaned file Movies (1391) into directory file 5.
CHKDSK is verifying security descriptors (stage 3 of 3)...
Security descriptor verification completed.
Inserting data attribute into file 0.
Inserting data attribute into file 7.
Correcting errors in the Master File Table (MFT) mirror.
Correcting errors in the Master File Table (MFT) mirror.
Correcting errors in the Attribute Definition Table.
Correcting errors in the Boot File.
Correcting errors in the Bad Clusters File.
Adding 1 bad clusters to the Bad Clusters File.
Correcting errors in the master file table's (MFT) DATA attribute.
Correcting errors in the master file table's (MFT) BITMAP attribute.
Insufficient disk space to fix master file table (MFT). CHKDSK aborted.

 

[birdpup]

For recovering data (google 'data recovery'), I would recommend GetDataBack from Runtime.org. This utility has worked well for me multiple times. There are other tools that supposedly work well but I have not tried them. Since hard drives often go bad, you may wish to search through other threads in this category for the solutions to other people's problems with hard drives. Recovery is not guaranteed and it is best if you install the failed drive as a slave to a master drive so the master may search the failed slaved drive. Do not forget to configure the jumper settings if this is an IDE drive.

 

[sykopath79]

Whatever you do, have a second HDD available, and save all recovered files from the bad drive to this second HDD. DO NOT save recovered files back to the same physical drive from which you are trying to recover files -- you'll end up overwriting something you want to recover.

Also, I noticed that the last line before CHKDSK quit says "Insufficient disk space to fix master file table (MFT). CHKDSK aborted." How full was this drive when it went down? Getting a HDD near 100% full will cause lots of problems, from just performing slower to drastically increased chances of data getting corrupted.

 

[nebula]

I too recommend GetDataBack. I tried R-Studio and one other app and they didn't work as well, but GDB worked nicely for me anyway.

 

[BadThad]

Originally posted by: sykopath79
Whatever you do, have a second HDD available, and save all recovered files from the bad drive to this second HDD. DO NOT save recovered files back to the same physical drive from which you are trying to recover files -- you'll end up overwriting something you want to recover.

Also, I noticed that the last line before CHKDSK quit says "Insufficient disk space to fix master file table (MFT). CHKDSK aborted." How full was this drive when it went down? Getting a HDD near 100% full will cause lots of problems, from just performing slower to drastically increased chances of data getting corrupted.

Yes, never fill a hard drive to capacity. Anyway, you need at least 20% free to properly defragment the drive.