Anyway, I used genkernel to configure my kernel for 3.2.12 and I did the same for 3.3.8 and 3.4.9.

Code:

genkernel --mdadm-config=/etc/mdadm.conf --mdadm --dmraid all

But, both kernels won't boot. I get the error "Could not find the root block device". When I drop to a shell and tyr to "cat /proc/mdstat" It shows the md127 device and it shows both disks as inactive.

When I do that same command under 3.2.12 I also see the md126 device, it looks like this:

If I try to do "mdadm --assemble --scan" from 3.4.9 then I get a bunch of errors about how /dev/md/imsm0 and /dev/md/Raid1_0 "has no identity information". Also there is an error that "mdadm: No arrays found in config file or automatically."

I can't cut and paste those, though, so I'm paraphrasing.

Anyway, has anyone else had success with Intel's fakeraid with 3.3.8 and 3.4.9 kernels?[/code]_________________I was born with a freakin' dice bag on my belt.
-- www.howsyournetwork.com

Last edited by volumen1 on Mon Dec 03, 2012 5:53 pm; edited 1 time in total

I briefly tried that bios based Intel junk a while back and never got it to work reliably. I guess there's a reason they call those things "fake raids". Since then, I've stuck to either high end stuff (ie HP smart array) or full blown software raid with mdadm.

The version of card that I have actually uses mdadm. It works great under 3.2.12, but not 3.3 or 3.4 kernels, at least not for me yet._________________I was born with a freakin' dice bag on my belt.
-- www.howsyournetwork.com

This is interesting, what do you mean by "it uses mdadm". AFAIK you can use mdadm on any fakeraid. Are you saying mdadm actually picks up the RAID configuration from BIOS?_________________Please learn how to denote units correctly!

This is interesting, what do you mean by "it uses mdadm". AFAIK you can use mdadm on any fakeraid. Are you saying mdadm actually picks up the RAID configuration from BIOS?

Yes, Intel is officially supported mdraid as the preferred way to access imsm raids. It will read the BIOS configuration and you can use most mdadm commands to administer the array. I messed around a lot with this and even wrote a howto in the Documentation, Tips & Tricks forum. You do have to set up a script and modify a file in /etc/conf.d/ in order for the raid array to shut down cleanly. This isn't mdadm's fault, it's gentoo's fault. I've noted the solution in mentioned howto.

Genkernel then complained because I didn't have mdadm 3.2.3 in /var/cache/genkernel/src (nor did I have it emerged, I was still on 3.1.4). So, I emerged it and then copied the tarball from /usr/portage/distfiles to /var/cache/genkernel/src

After genkernel built the kernel, modules and initramfs I made the following entry in my grub.conf