undoing XP chkdsk possible?

[Vicken]

Is it possible do undo an XP chkdsk on a hard drive. My hard drive crashed with FAT32 corruption so I ran chkdsk /f generating lots of .chk files. I recently ran getdataback and it finds some of my data. I am wondering if I can get more back data back if i can undo the chkdsk.

 

[Sianath]

Not to my knowledge, no.

 

[Abzstrak]

sorry, you can't recorrupt your drive in the exact same way... hopefully you've now learned to stick with NTFS.

 

[n0cmonkey]

Originally posted by: Abzstrak
sorry, you can't recorrupt your drive in the exact same way... hopefully you've now learned to stick with NTFS.

And BACKUP 😉

 

[spyordie007]

Is it possible do undo an XP chkdsk on a hard drive.

I dont believe so.

I am wondering if I can get more back data back if i can undo the chkdsk.

Even if you could "undo" chkdsk you probably wouldnt be able to recover any additional data.

Sorry to hear about your data loss, it's never any fun if you loose something important. Take the suggestions of Abzstrak and n0cmonkey to heart to help avoid these problems in the future.

-Erik

 

[NogginBoink]

Chkdsk wasn't the cause of the problem. Your data was hosed before you ran chkdsk.

 

[Nothinman]

Chkdsk wasn't the cause of the problem. Your data was hosed before you ran chkdsk.

It depends on what the real problem was, something like a bad cable could cause read/write errors even though the data was fine and chkdsk would 'fix' the filesytem by losing or corrupting most of the data.

 

[NogginBoink]

Originally posted by: Nothinman

Chkdsk wasn't the cause of the problem. Your data was hosed before you ran chkdsk.

It depends on what the real problem was, something like a bad cable could cause read/write errors even though the data was fine and chkdsk would 'fix' the filesytem by losing or corrupting most of the data.

That's a weak argument. If a cable was bad causing read/write errors then chkdsk wouldn't be able to work on the filesystem.

Chkdsk corrects damage to the filesystem. If chkdsk caused files to go missing, those files were already in a damaged part of the filesystem.

 

[Nothinman]

That's a weak argument.

But it's still possible, even though not terribly likely. I'm just saying that running chkdsk isn't always a good idea if the hardware could be in question.

If a cable was bad causing read/write errors then chkdsk wouldn't be able to work on the filesystem.

Not necessarily, especially with FAT because there's no signature or journal or anything to check so Windows just mounts it and assumes it's fine.

Chkdsk corrects damage to the filesystem

Yes, but if it's recieving data that's not consitent with what's on disk it'll try to correct it and make the problem worse.

 

[gsaldivar]

It depends on what the real problem was, something like a bad cable could cause read/write errors even though the data was fine and chkdsk would 'fix' the filesytem by losing or corrupting most of the data.

That's a good point.

In the old SCSI days, it was completely possible for a bad cable or a malfunctioning device to corrupt data on a different device connected to the same SCSI bus. I had clients who would try to "fix" these problems by running their own diagnostics before calling us in, and end up with a massive self-inflicted data loss.

Ah..... the good old days. 🙂