Good man, I hope I never have to use this...

 

Thought I'd use this rather than a new thread.

I can recover all my data but I'm struggling to get vista 64 to boot, managed it once but itnow gets to the part where the loadin bar comes up the restarts. Any ideas?

I can recover the data now as everything shows up on the recovery disk's command prompt.

The vista startup repair fails because of bad drivers, what drivers do I need?

 

Alright this post is a life saver! I thought I had lost all of data on my raptorX's in Raid0.

What had happened was when I turned my rig on with my WM phone synced and charging. It cut my raid array and my drives were showing as NON MEMBER. I tried everything I could think of, but this fixed it right up.

+rep

 

I can say this definitely works. My RAID has been giving me trouble lately (since taken it out temporarily) and did this probably a dozen times. Perfectly safe to do and can be scary at first, but it will WORK!

I seriously wish I knew this back in January when it wouldn't boot and I had to reformat and lost about 2 months worth of stuff.

 

Bump for the masses.. Had to do this again within the past month or two and missed the last few comments being away from the OCN forums a bit..

Cheers!

 

Absolutely awesome, I wish I had this a couple weeks ago

BOOKMARKED!!!
REP+

 

Update to the original post concerning Win7 as well the 3 commands needed to get the Vista boot manager working once you reset the RAID config..

Another success story here!
http://www.overclock.net/hard-drives...ml#post6837244

This works with Win7 but the navigation to the Command Prompt in the recovery console is a bit more `hidden` but have it go through Repair and when asked after it states it's fixed something hit NO and go to the Recovery Tools area where you'll find the Command Prompt option

~Ictinike

 

Is there anything i can do if when i create the raid volume over again it says Failed right away and the 2nd disk is still a Non-raid disk?

Thanks,
Philippe

EDIT: Never mind... ran diag on it.. its fried :/ RMAed

 

I'm trying to use this solution to my problem, but I can't boot to my spare drive when the motherboard is in RAID mode. It just crashes on windows startup. If I turn raid off in the bios then I can boot to it, but then test disk only sees each drive separately and not as a raid, so it can't find any partitions. Any tips?

 

Thanks, I appreciate the share.

Running a RAID0 array without a back-up is akin to playing Russian Roulette with no empty chambers.

 

Quote:

Originally Posted by Ictinike Update to the original post c.......... Another success story here! http://www.overclock.net/hard-drives...ml#post6837244 ~Ictinike

I gotta hand to ya Ictinike,

...

You went way beyond the call of duty!

I'm from Massillon and if you ever get close to my area, I'd be honored to buy you a refreshing beverage.

This Bud's for you!

 

two questions, i'm having same issue with Raid 1 setup does anyone know if this will work for this?

Also the first step which is to make all the drives non member using intel utility, how do you do that?

 

I went ahead and followed the instructions but sadly it says the drive is corrupt. No Windows (7) installation can be found. I think I'm screwed...

 

Eh... this post lead me to 'confidently' erase all my data. I followed the directions, booted into safe mode but it seems apparently the Raid had been initializing anyways in the background (even in safe mode). After I ran TestDisk and wrote the partition to the drive it recognized the Drive Letter, but said it was corrupt. When I booted to Normal Mode I checked the Raid Status and it was already on 50% of initialization... I could have chose a different route, but I trusted this method based on the post's responses, but it led me to confidently flush all my data down the drain. Not good.

 

An absolute life saver! Thank you very much

 

I read this post, and saw similar in other places. Sadly, the first post does not mention that the RST program will start initializing the RAID once the O.S. boots.

In my case, I have a RAID 5 array that comprises of 5 drives. I deleted the RAID, and then recreated it as mentioned here. When the machine came up, RST said, initializing raid. I stopped it at 1%

So, the question is, was I too late? Perhaps 1 of the 5 drives was being initialized, and the other 4 are ok? What does the initialization do? Does it destroy all of the data on the drive?

Also, I am currently using Test Disk to identify partitions. It seems to find the partition on one drive right off. I am searching a second drive, but it is going to take a long time. A couple of questions here, if I find the proper partion on one disk, would the partition be the same on all disks? Also, what kidn of partiton does the Intel ICH10 create - Intel partion, but I see NTFS as a choice too? I am not sure what the difference would be. Sorry to be such a nooblette.

Any ideas would be greatly appreciated.

 

I don't think you should delete the raid, but remove all drives from the raid. Don't

me when this ends up having the same result though. Then create a new one in the exact same config and use testdisk to analyze and recover the partitions from the raid volume that was just created.
Hope that helps

 

Same thing happened to me tons of times. All I have to do is power off, unplug, and replug my HDDs, boot up and it's fine.

 

Sadly, I had already started following the plan as written above. So I have already deleted the RAID from the BIOS and recreated. From what I read, TestDisk should have saved me at this point, but the RAID started to initialize - 1%. So I am not sure if I am cooked.

So that is really the question, does the Rapid Storage RAID initialization destroy the actual data on the drive, or does it recreate the RAID info on the drive, and leave the data as it was? At the very least, considering it only initialized 1% I am thinking I may still be able to save 4 of the 5 disks?

 

Woohoo!! It worked!!
I had a failed RAID 0 setup, because I switched my drives to different SATA ports, then afterwards I had 1 failed RAID and 1 non-raid disk.
I took a picture of the settings for my RAID, found in the Intel Matrix screen, than deleted the RAID and recreated it.
In Windows, I used TestDisk like you said (a guide can be found here: http://www.cgsecurity.org/wiki/TestDisk_Step_By_Step)
And it totally worked!!! I have everything back, without having to use extra disks!

Thanks a lot!
10 minutes of worked and what a result!
Rep+

 

I am having a similar error that is listed on this thread. However, I am dealing with a RAID-5 non-bootable array. The unknown drive is showing up as an internal drive within the Intel rapid storage manager. The unknown array drive has the same serial number of the internal drive, except the unknown array drive as a :0 after the serial number. Would these same instuctions still work for my RAID-5 array, or is there another way I can restore this array? I have an extra 2TB drive (same as the four drives in the array). Could I set one up as a spare and would that allow the array to rebuild automatically?

Thanks,
Dan

 

This worked like a boss. Even on a 3TB (GPT MS file table) formatted with ext2 on Windows Server 2008 R2. Fantastic.

For those with GPT file tables (if you have a filesystem bigger than 2TB, you will), I did a Google search "TestDisk gpt" and found some git commits (dated ~2010) which corrected a couple of bugs for GPT. The TestDisk version 6.11.3 (6 May 2009) would have this bug, so I used the Beta WIP version, 6.12. I encountered no problems using the Beta.

 

Yay! I got my RAID 0 partitions back. 70% of the way through the RAID 1.

 

I want to add additional information. Using ZAR (Zero Assumption Recovery) you can recover any RAID without the controller or settings it was set up with. It does this by, as it was named, assuming nothing. I'm on my second round using it after I gave up on fixing this failed RAID5 (2/3 disks read as offline without reason.) The process is roughly the same as using Testdisk. The Testdisk methode, however, is much faster. ZAR takes a lifetime to process.
Quote:

Originally Posted by Old Hippie;7389203
Thanks, I appreciate the share.

Running a RAID0 array without a back-up is akin to playing Russian Roulette with no empty chambers.

I had a four HDD RAID0 for three years before decommissioning it for my Revodrive. Never once a problem. Gotta love single platter WD drives. (4x160GB)

 

Quote:

I had a four HDD RAID0 for three years before decommissioning it for my Revodrive. Never once a problem. Gotta love single platter WD drives. (4x160GB)

Cool!

But my statement still stands.