Corrupt HDD question
 

I have a 120GB Maxtor that is just used as storage. I have about 75GB of used space on it. I just put a new mobo in (Epox 8KRAI-X) and now when I click on it it says that its corrupt and cannot be read. Is there anyway that I can recover these files? With my old mobo (Epox 8KHA+) it would sometimes work and sometimes not, but for the most part it would work and now it doesnt. Whats the deal? Am I screwed? Thanks in advance.

-Big D

I heard that maxtors are junk to begin with. You just might be screwed. Mabye go back to your old mobo and get the filed you nedd burn them to a CD and reload them onto the new HD. You could always go with a data recovery service. IF you have the $$$ to pony up.

Try Spinrite if nothing else works.

bad copy pro works wonders some times, as long as the data is still there and the controler is not shot.

its basically all my porn...i just want to get it all back...not too much of a biggie to lose but i had a lot of good stuff that i just wanted to save....would reformatting fix the problem?

No, reformatting would make it harder (if not impossible) to get your files back. Unless you were able to "repair" Windows, which only reinstalls system files. I've never had an opportunity to do this, so I don't know how well it works.

is there anyway i can get the hdd working again? porn or no porn?

btw, when i run a checkdisk it fails and says "corrupt master file table" what does that mean?

I have 4. None of them have ever stopped working. Great value for how much they cost. Sorry for getting off topic. :thumbsup:

A "Corrupt Master File Table" means your partition table (or possibly the file allocation table within one of the partitions) is hosed. Not sure why switching to a new motherboard would do that, but I've certainly seen stranger things. If you're not having any luck with file-recovery utilities, then my last resort would be to use fdisk to re-create the partition table on the drive. Fdisk will only write to the partition table, so whatever files you had on the partition *might* reappear if the partition table gets fixed. This has only worked a couple times for me, so it's kind of hit-or-miss. If your drive had been flaking out on you already, then you might be dealing with a toasted controller, in which case you're screwed.

You might also try swapping out the IDE cable...that's also worked for me once.