Data recovery and disk repair questions and discussions related to old-fashioned SATA, SAS, SCSI, IDE, MFM hard drives - any type of storage device that has moving parts
Post a reply

SATA RAID 0 Repair - One disk doesn't know it's RAID

May 13th, 2006, 19:44

I've got a real problem that I haven't been able to fix for nearly a month now and I'm only one step short of paying a data recovery company through the teeth to solve it for me..

I currently have two SATA Western Digital Raptors running in a RAID 0 configuration as my primary Windows (NTFS) drive. One day while I was at work and my girlfriend was watching a TV show on my computer, it crashed and rebooted. But it never came back up.

When the machine is booted, the Intel RAID BIOS screen shows that there should be a RAID volume and that it can see two disks. It reports that Disk1 is a member of the RAID volume, but it reports that Disk2 is a "Non-Member Disk".

Since Disk2 doesn't know it is part of the array, it's completely broken everything, but I need to get that volume working again.

I am assuming that something failed a disk write on Disk2 when the machine crashed, but I have NO idea how to tell Disk2 to re-join the RAID array. The Intel RAID BIOS has no option other than to delete and re-create the volume, though I'm sure this will destroy access to all data permanently.

Can anyone give me any useful suggestions as to how to uncorrupt Disk2 - even if it means losing a small portion of data, I HAVE to get the array running again without losing the whole volume. I have considered raw disk editing, but I have no idea how, nor what I would do if I could; I do not know how RAID volumes are built, my knowledge stops at the filesystem.

Any help anyone can give would be greatly appreciated.. I can't afford to pay a company to recover it for me.

Thank you for your time.

May 15th, 2006, 10:59

Hello,

Now if U really need the data, U should not try to remount it using the raid controller. In fact U should never give Windows a chance to mount a damaged partition.
In this case (though U haven't mentioned the RAID level the disks were running) I suppose it was striped (RAID0).
I think U should first diagnose the damaged disk and make an image of it to a known good drive, if even it is possible.
Then U may continue with SW recovery.
If U are unfamiliar with theese things, I definitely suggest to take the set to a specialist.

edit: now I see the topic shows it is a RAID0 :) sorry.

regards,
pepe

May 16th, 2006, 14:20

I definitely plan to do a disk image to a backup disk before attempting recovery, but the problem is that I have no idea how to go about starting the recovery itself.

Right now I do not have a working windows installation that can boot in the same machine as the RAID0 array, so unless i take drastic measure to get one going, im stuck with Linux for the moment.

But the next step is.......... who knows?

May 17th, 2006, 11:28

U may install a windows on a spare disk and use that...
Anyway U will need a new installation probably.

pepe

June 16th, 2006, 11:30

I don't know about Recovery of RAID 0, but i would like to know more since i have RAID0 myserlf.
You definitly need to take image from at last from damaged drive to another HDD. Also i think that you need OS on other HD.
There is a tool
RAID Reconstructor
_http://www.runtime.org/raid.htm
That can help you with reconstruction. I never used it but you better to read manual first.

All that is Pure IMHO.

Please tell how you solved that. Thanks.[/url]

June 16th, 2006, 14:03

Not solved at all. Only possible resolution is in-house software made by data recovery companies with a minimum recovery cost of £1500 ($2000).

RAID Reconstructor is of no use in this case. Intel agree there is no standard way to reconstruct.

Am giving up :(
Post a reply