I would like to rebuild my Mirrored array, yet while the pre-boot utility will recognize and prompt to rebuild onto the non-member disk - it then says that rebuild will occur inside the OS.

But I'm running Fedora 11 - so, what is my best strategy? It doesn't look like a boot disk is an option - the Storage Manager is downloaded as an .exe install file.

I should say ahead of time - I just have a slight bobble in one disk and an extra drive and so thought I would re-build the array just to see how it works. I'm sure glad I am looking into this now! The only other hardware raid controller I've worked with are the Dell poweredge ones. It never occurred to me that the ICH7 wouldn't rebuild the array prior to booting to the OS.

T.I.A.

I'm pretty sure that ICH7 is supported by dmraid, which means that once the hardware is recognized you should be able to rebuild with the -R parameter if you're using rc15 or greater.

Oooookay. So. After working with it for a bit. I've decided to pull my data off and disable the mobo RAID and use Fedora's software RAID.

I could not rebuild the array using dmraid or mdadm. Neither would recognize the array. It is _very_ possible that this is simply error on my part and lack of knowledge regarding the /dev/dm-X structure, or what do to when confronted with fsck.ext3: "unable to .... UUID...". Since I could just plug back in the other drive and call it a day I took the easy way out.

However, I did dig up some interesting articles lambasting FRAID and why it is called such. Comparing my Perc controller experience (also had a failed disk in a RAID1 array) to the total lack of utility in the Bios Intel Matrix screen experience, I will implement software RAID and save up for a 3Ware card.

As usual with my Linux escapades, I learned some more. Such as the "xhost +local" command when after 5 min of trying to figure out how to launch Nautilus in admin mode. >.<

<walks off chanting "I still like Linux" "I still like Linux"> :P

Update. Ha ha HA!

As if it would let go so easy!

After disbanding the Array in the config screen and rebooting I configured the SATA disks to AHCI / Enhanced. As a result, could not install Fedora 11. It would not see the disks.

I dug around, saw that this was an issue with 11 (although I don't know if it's still an issue); and so reluctantly set my disks to IDE / Enhanced. Still won't see the disks.

My best guess based on my previous experience of Raid migration is that disks are still marked as Array Members. If so, only a low level format with a Seagate utility (Barracuda drives)will remove that info.

But I was tired, so I just created the FRAID group again and set it up. Later I will fiddle with it some more. I didn't get around to toggling Enhanced mode off. To easily prove the phantom array issue, I'll pop in a different disk to test.

If anyone has any thoughts, observations or experiences I'd love to hear them. I still consider myself "new" to Linux as I work with it in bursts. I'd learn more quickly if it weren't so durn stable!