Overclock.net banner

1 - 20 of 300 Posts

·
Fettered Firewall
Joined
·
2,491 Posts
Discussion Starter #1
Greets..

Just something I'm sure has been here but since the changes to the searching of the site I can no longer go back more than 5 pages and I've lost tons of info because I failed to bookmark or subscribe. Here is a new attempt at fixing this as I just lost and recovered my Intel RAID0 Array without loss of data.

I have the Gigabyte UD3P and it has the Intel ICH10R chipset which has given myself, as others out there on the interwebz, some problems with an unsuspecting action such as a reboot, BIOS Flash or OC'ing crash and leaving 1 or more of your drives in the RAID Array now showing "Non-Member Disk".

Essentially this means it's lost it's RAID configuration and I just got through my 3rd time with this issue. The prior 2 times I wasn't able to find info and had to "bite the bullet" and re-established my array from scratch and installing everything again. Quite a PITA.

Again tonight, after a BIOS Flash and restart on my UD3P, I saw in the RAID BIOS again the "Non-Member Disk" flag and my array in "Failure" mode


Fear not. The steps listed below are NOT mine but I found them and followed them to a T and unbelieveably they worked like a charm! My RAID0 is back and no data loss. Unbelieveable!

I provided this as-is but the thread where this was sourced had many with the same success. I cannot vouch for anyone but myself and my success as well possible controllers it may or may not work with so BE SAFE and do your dilegence!

Source Thread

Quote:

Originally Posted by The Source Thread Above
Thanks to everyone who tried to help. I found a solution and I thought I'd share it. I was able to recover the broken array using following steps.

1. Reset both HDs to non-member using Intel BIOS utility - the utility warns that all data will be lost - in fact only metadata is lost and can be recreated using steps below.

2. Create a new array with identical settings as the broken array. It is critical that the HDs are in the array the same order as before. I was reconnecting the drives several times and lost track of correct order. Because of that I had to go through the steps twice (I guessed wrong the first time).

3. Get TestDisk from http://www.cgsecurity.org. I used Windows version (I installed a new Vista on a separate HD for this purpose).

4. Run TestDisk according to steps on the web site. If your HDs are connected in correct order, TestDisk should find the lost partition(s) within a few seconds. It ran for several hours, scanning my array and never found anything because I had HDs were connected in wrong order. After I changed the order and restarted from step #1 TestDisk found the missing partition immediately.

5. Have the TestDisk write the fixed partition table to the drive and reboot.

6. Now all your data on the array should be readable but the system might not boot (it didn't for me).

7. Run Vista repair from installation CD to fix the MBR.

Quote:

Originally Posted by Ictinike

On this part, a gent and myself went through this for Win 7 as well I've done Vista and we had to run the 3 bootrec commands to get his viable. I can't remember if I did this on Vista but it might be wise to run all three to fix the MBR in Vista as listed above. To do so:

in Command Prompt from the Recover console enter:

bootrec /fixmbr (should success)
bootrec /fixboot (should success)
bootrec /rebuildbcd (detects the Windows installation and asks you to add it to the BCD, hit YES)

8. Last but not least, send a donation to Mr. Grenier, the author of TestDisk.
Now I'm bookmarking as well subscribing to this thread so I never lose it and have to find this info again!

Cheers!

~Ictinike
 

·
Registered
Joined
·
230 Posts
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?
 

·
Registered
Joined
·
1,163 Posts
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
 

·
Premium Member
Joined
·
7,426 Posts
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.
 

·
Fettered Firewall
Joined
·
2,491 Posts
Discussion Starter #6
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!
 
  • Rep+
Reactions: PR1M3R

·
Fettered Firewall
Joined
·
2,491 Posts
Discussion Starter #8
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
 

·
Registered
Joined
·
6 Posts
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
 

·
Registered
Joined
·
18 Posts
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?
 

·
Registered
Joined
·
1,822 Posts
Thanks, I appreciate the share.

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

·
Registered
Joined
·
1,822 Posts
Quote:

Originally Posted by Ictinike View Post
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!
 

·
Registered
Joined
·
1 Posts
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?
 

·
Registered
Joined
·
2,383 Posts
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...
 

·
Registered
Joined
·
3 Posts
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.
 

·
Registered
Joined
·
3 Posts
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.
 

·
Registered
Joined
·
2 Posts
I don't think you should delete the raid, but remove all drives from the raid. Don't
gunner2.gif
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
confused.gif
 

·
Registered
Joined
·
2,334 Posts
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.
 

·
Registered
Joined
·
3 Posts
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?
 
1 - 20 of 300 Posts
Top