> On boot, the kernel automatically detects and starts md0 through md4.
> However, md5 is *not* autodetected. Using the RAID_AUTORUN ioctl also
> has no effect. The only way I've found to reliably start md5 is to
> have rc.sysinit run "mdadm -assemble --scan".
>
> Is this a bug? A design limitation? Something else?
this is one of the limitations of the in-kernel autodetection
> (I am currently using kernel-2.6.9-1.675_EL on the RHEL 4AS beta. But
> I've never been able to get autodetection of stacked raid devices to
> work using any kernel.)
if you are not booting from the stacked raid device you can safely have
mdadm called from rc.sysinit, if you are you better use mdassemble in
initrd.
Regards,
L.
--
Luca Berra -- bluca@xxxxxxxxxx
Communication Media & Services S.r.l.
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
