After Chkdsk one of my SATA drives is now RAW

One of my HDD's is an older WD 500GB Sata drive which I've used for data storage only. It has no OS on it. Back in the day I used a PKzip command line batch file to do my backups onto that drive, and at that point in time a Fat32 partition was sensible since most of the .zip files were large anyway.

Last night before bedtime I decided it was probably time to Defrag that drive since I had not done so for many years. Shortly into the Defrag process Windows says "Cannot proceed (with analyze) due to D:\dir\sub\sub\sub\problem" is corrupt and unreadable."

I clicked that box away, and tracked down the Problem sub-directory, which turned out to be something 20 years old that I would never need again anyway, so I tried to delete that at the parent level. "Access denied..... FO.... you can't delete me". So then I wanted to reboot into Linux and remove that directory from there, but due to a domestic disturbance I was not attending the reboot. When I came back to the machine Windows was running Chkdsk on drive D. I didn't schedule this, so I don't know what options were automatically set. This was going on for at least a couple hours when I fell asleep.

So this morning I woke up to XP loaded, my D drive is of file system RAW, the volume label is changed to "Local Disk" and Windows XP cannot access the drive thru file manager. However, MiniTools Enterprise v.12 sees it as a Fat32 partition. I tried using MiniTools "Check Disk", which got me nowhere.

Then I booted into Linux Mint, mounted the drive, and Linux does see the Directory structure, and the contained subs and files...... but at a very slow rate. Clicking on a directory might take up to a minute before the files are shown, depending on content. I tried copying some directories over to an external drive, but after 41% the progress got stuck and nothing seemed to be happening for at least half an hour.

Then I bailed out of Linux and rebooted XP, and for fun tried to do a System Restore to a point just prior to when I initiated the Defrag process. Got a warning that "Changes to drive D will not be restored cuz XP says so"...... something like that. Anyway, that got me no joy.

So now I'm looking for advice. At least 90% of the data on that Fat32 drive is backed up elsewhere, but I want that other 10% too. Doing a Marcium Reflect of a RAW drive doesn't seem like much help, unless I need that to undo future catastrophes, and I'm not too sure I want to run Windows Chkdsk again since it created this problem in the first place.

Linux does have options to fix file systems, but I've never used them, and of course there are 3rd party apps (like Minitools) to try as well.

Spank me!!
 

did you try above solutions? knock on wood but I have no personal experience to this issue, :)
Thanks for the reply Elizabeth, but I've already read dozens of posts related to Minitool and others. All of the Minitool articles I've read have the same thing in common, they never describe SPECIFICALLY how their software will help you even identify the correct option to use, ( MBR rebuild, data recovery, partition recovery), or WTF you're gonna end up with.

Since this Fat32 drive was actually recognized by my Linux OS, (even at the slow rate) I managed to copy over (I think) all the recent data on that drive onto an external drive. Before this, I had also used Macrium Reflect to create an image of the "corrupted" drive.. I hope I'll never need to restore that image to another HDD since it took about 5 hours and had "Errors: 465 bad clusters".

At this point in time, I think Linux is a better friend than Windows. (it was Chkdisk that screwed me over in the first place.) Once I get a confirmation from the Linux guru's that what I'm planning is right/wrong... whatever, I'll post again.
 
Last edited:
Hi Wolf,

First, it is a good idea to clone/image the damaged HDD to another one, recommended programs are HDDSuperClone or ddrescue (both are Linux-based).
Then run some software on the clone.


Partition Find and Mount 2.31 :

Info:
Partition Find and Mount allows you to recover deleted partitions. What's special in this program is that it allows you to mount lost partitions right into the system, so the operating system sees that lost partition like a good one.
This software also has the possibility to create and mount images of the entire hard drive or separate partitions.


TestDisk :

Info:
Can help recover lost partitions.


Try both programs, Partition Find and Mount 2.31 and TestDisk, both were recommended, I have never used them though.
 
so you need a tool to recover bad clusters


the poster in the above was able to recover his files, read through and see if it will help you.
 
Thanks for all that info, but it's water under the bridge now. When I looked up how to recover "corrupted" files, most of the articles weren't very encouraging. Add to that, while I was using Linux to recover data there were entire directories which were unreadable. Luckily however, I was able to retrieve all the newer stuff I hadn't backed up yet.

The drive has now been "saved". I ended up using MiniTools Enterprise V.12 to delete all partitions, then create new NTFS (415GB) & Ext4 (50GB) partitions. The Ext4 partition is intended for use with Linux Snapshot. I spent roughly 4 hours to then copy all the data back onto the drive from an external HDD via USB, and from a networked machine via WiFi.

Even though neither OS would offer me the "quick fix" I was hoping for, I'm very happy that I did have Linux Mint installed which allowed me at least to recover all the data I didn't have backed up elsewhere. I don't think I'll ever know for sure how this drive got messed up in the first place. Perhaps there was a power hick-up during the time Windows decided to run Chkdsk on it?
 
well I am glad you recovered your files, and yes power fluctuations can corrupt a disk, where I live now there are lots of power outages, and I run checkdisk after each power flux. if windows considers the disk dirty then it will run checkdisk at the next startup. you can run below to check the disk, if it says it is dirty, then you can run checkdisk, I always run with the /r parameter. :)

Command Prompt

fsutil dirty query C:

Sample output:
Volume C: is dirty
Volume C: is not dirty
 
Back
Top