Raid 0 and XP repair options

sweetpain · Rated PG Joined: 23 Feb 2005 Posts: 2

It has been a while since I have been stumped but now I am. I have a PC that is using an on board Raid controller. It is set for Raid 0 (used for digital editing). Today at boot up we get a message that a system file is missing or currupt. I can fix that no problem right? Yea I wish.

Here is the deal....when I load recovery console it does not see C:....don't know why because I did load the third part driver at start up. Now I say lets give doing a repair a shot...no luck there either...XP can see both drives but not as one. So I load the driver so XP can see the disks but not the strip set.

Any ideas??? I am at a loss...and the kicker is if I could just get into my operating system I could solve my original problem in a flash.

I even tried ERDCommander and it did see the drives but could not tell what operating system was running. Again I suppose because it can't read them as one drive.

Thanks

BeerCheeze · Posted: Thu, 24 Feb 2005 01:08:19 Post Subject:

Sounds like you need to go into the RAID BIOS and see what's up. It might have lost it's config, or a drive went bad.

Spire · Posted: Thu, 24 Feb 2005 01:24:17 Post Subject:

This has happened to me...

I have gotten a stripe array back sucessfully by deleting the array in the RAID bios and immediately recreating the identical array. I think it causes a new MBR to be written.

This is only a last resort and is risky. You do risk losing everything if it does not work, but then again, thats where you stand now anyway.

In my case, I was assuming that the MBR of the stripe got hosed.

Please only attempt this if you understand the risk to your data.

A big welcome to BigBruin!!!!!!!!!!

sweetpain · Rated PG Joined: 23 Feb 2005 Posts: 2

I decided to install XP on a seperate disk. After installing I loaded my raid driver in XP. Now it does see my 2 drives as 1. It still does not recognize the format of the drive or what is in it.

I am now running getdataback software on that drive. So far it has counted 67,000 files with a few errors here and there. I'm assuming there are some bad sectors on one of the drives.

Cross my fingers