www.deadharddrive.com

[Nigo]

Hi guys.

Ok, i succesfully switched a PCB on my Maxtor Diamondmax 9 Plus 120gb and i got booted up and windows loaded it in once i got into desktop.

I looked at the data and yes, everything was correct, NICE!

I move some data but after a while i get a data reduncancy error, and it frooze sometimes. I thought there might be a interferrence from my other drive, so i shut down and switch it over to its own IDE channel.

After i boot up, it does not show and after some testing back and forth i have concluded that the MBR / Partition table is ruined and/or the data is now in RAW format.

The dilemma:

What happened after the boot? At first boot the drive was installed as i expected and immediatly popped up in explorer with the same name and data inside. How could a second boot ruin the partition table or possible MBR?

I got some data before the reduncancy error and the pictures worked.

I now sit with a couple of options.

Can i do a RAW data recovery succesful ?

Should i try to create new MBR and partition table and after do a standard data recovery with a utility program? I dont know if the data would be ruined if i create a new MBR


Almost every recovery program is able to find it, shows with the correct model name and size, just no info, cause of ruined MBR / Partition table.

I cant reach it, try to rebuild MBR or what not, BUT the drive is functional and i know there is SOME way of fixing this problem.

So that's why i post here, as there maybe some of u with a solution?
I cant be the only one having problems with readable data after a PCB switch

Also, as i am from denmark, can some of u guys link me too good/large english forums regarding hardware questions etc.

Thank!

Mails are welcome

[RussWinters]

Dont worry about the MBR at this point. RAW recovery is what you are going to want to shoot for. If the drive identifies that is a good sign that you can still extract data from the drive using recovery software. I would recommend R-studio or getdataback as they are pretty easy to use.

What happened is this: When you plug a drive directly in to a PC it is not "Write protected" meaning that writes can still be made to the drive. What is likely occuring with your drive is a weak/failing head/heads. When you plug your drive in as the boot drive, it makes writes even if you did not specifically tell it to do so it will always make changes as needed. What probably happened is that it attempted to make changes to the MBR, and since the head/s are weak the write failed, and corrupted sector/s in the MBR and in other areas writes where being made to. It then began to give you cyclic redundancy error.