Any RAID experts? - Restore array after controller failure

[Dredgy]

Hi

 

My motherboard failed and has been replaced. (Exact same motherboard, exact same chipset)  - Asus X79 Deluxe with Intel chipset.

 

I have a RAID 0 array as my primary boot drive.

 

On the replacement board, when I boot, the RAID doesn't find all member disks.

 

It finds the array name "BOOT" and it's capacity as 900GB and lists it as "failed".

 

It detects the first drive in the array as a Member disk of the BOOT array.

 

It detects the second drive as a non-member array.

 

Both disks are fine, and I'm 99% sure they are plugged in the right ports (had a diagram). I am able to pull data off the array in recovery software.

 

While there is little crucial data on the drive, if any, it will take me weeks to download the software on it and I need this system running ASAP.

 

What is the best way to get this array to boot.

Thank you.

[N4dez]

Had the same thing happening to me. I had a spare disk laying around that was big enough, copied all the data to that disk.
Removed the raid and configured it again on my new mobo.

[Dredgy]

Had the same thing happening to me. I had a spare disk laying around that was big enough, copied all the data to that disk.

Removed the raid and configured it again on my new mobo.

 

Yea is what I'm going to have to do. Can't seem to find any disks big enough so will have to buy one tomorrow. Which is annoying, was hoping for a solution tonight.

[N4dez]

Yea is what I'm going to have to do. Can't seem to find any disks big enough so will have to buy one tomorrow. Which is annoying, was hoping for a solution tonight.

 

That's what i did, as far as i know, they may be another solution out there, i just don't know it

Don't now how much time you have until someone posts it here.

[Dredgy]

@N4dez. 

 

Thanks. If no one comes up with anything better I'll just buy a drive on my way to work in the morning.. Extra hard drives always come in handy anyway. Will also have to rebuild a mass storage array now I think about it, so will probably need to do that anyway.

[Dredgy]

@N4dez what software did you use to create an image? I have a couple but I'm unsure if any can image striped volumes even when they aren't in RAID.

[ChineseChef]

Restoring raid arrays with onboard raid controllers can be super finicky, you may need to do some heavy googling of your specific mobo to see if anyone out there has a good walkthrough or something.

[N4dez]

@N4dez what software did you use to create an image? I have a couple but I'm unsure if any can image striped volumes even when they aren't in RAID.

 

I didn't use any "software".

I created a live ubuntu usb, and for some strange reason it recongized the disk seperatly but also as one partition. so i copied everything over from that one partition to an other hard disk.

It's gonna take some time, just saying.

This is still dangerous for file corruption because the raid array isn't "recongized".

Can't garantee a perfect recovery, but it worked for me, not really in expert in these things. 

[ManWithBeard1990]

This is why I prefer software RAID.

[Dredgy]

Was able to recover this fairly easily with ReclaiMe and an external hard drive.

[NumLock21]

Even though you have not modified your RAID array, looks like the sudden failure of your board might have knock out one of the HDD to become a non-member disk. Normally when you change the motherboard with the same type of RAID controller you're currently using, then the RAID array should still detect properly and boot right up. Had RAID 0 running for a few years, upgraded to 3 different boards, all running running RAID 0 on the Intel chipset. When booting up, RAID detects both drives and boots right up. Even though the board has changed, the RAID setup doesn't know this and still thinks it's running on the original board the RAID has initially been setup with. Your raid setup is corrupted, nothing you can do except rebuild it from scratch or try to add the non-member disk back to RAID, and hope for the best.