Page 1 of 1

WD Caviar Blue recognizing as raid-0 after energy fall

Posted: 09 Dec 2014, 12:51
by Cezamo
Hi everyone!

I own 01 HD WD Caviar Blue, and this weekend after a energy/power outage, the disk is no longer recognized by the windows as a valid disk.

I used this hard drive about 2 years ago in a raid-0, but then I got rid of the raid and began to use it only as a unit for backups.

After the power outage, I ran the TestDisk through Ubuntu, and he "sees this" 500gb disk as a 1TB disk, somehow as were part of a raid.

I believe that because of not having done a full disk format and used the quick format, the MBR was returned as raid, but with these weird problems.

The testdisk with the parameters that I used, found no partition or system of valid files. Im receiving a warning: Bad ending cylinder (CHS and LBA don't match).

On windows, the disk is also seen as having 1tb and the Disk Management can not boot it or mark it as active, and I get cyclic redundancy error when I try to activate it.

Maybe if I apply some changes in geometry could solve the problem? I have no ideia on how to do this but its a guess.

In view of this information, as could I at least recover the files that are contained in the unit? I honestly dont care if the hard drive become obsolete, just like to recover some or all of the files if possible.

Maybe if I apply some changes in geometry could solve the problem or at least give me access to the files? I have no ideia on how to do this but its a guess.

Im working right now, and when i got home i can provide much more information if needed.

Thanks in advance!

Re: WD Caviar Blue recognizing as raid-0 after energy fall

Posted: 11 Dec 2014, 13:20
by Cezamo
Solved, photorec saved me. I won the hard battle to recover all the files, but the most weirdest thing now is that Windows is seeing two hard disks instead of one.

He's seeing a 500GB disk and a 1TB Raid-0 Intel disk, that no longer exists.

I've made a surface scan test last night and the results was fine. But now, I'm affraid to lost all my files again due to this problem.

Does anyone have seen something like this before?

This ghost RAID is write-protected, inaccessible, so till now its impossible to remove it.