that one i have seen -- as i now understand it yaird only<br>
does the root fs -- for debian set the raid script in rcS.d<br>
it will start the other md devices <br><br><div><span class="gmail_quote">On 1/5/06, <b class="gmail_sendername">Lionel Elie Mamane</b> <<a href="mailto:lionel@mamane.lu">lionel@mamane.lu</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
_______________________________________________<br>Yaird-devel mailing list<br><a href="mailto:Yaird-devel@lists.alioth.debian.org">Yaird-devel@lists.alioth.debian.org</a><br><a href="http://lists.alioth.debian.org/mailman/listinfo/yaird-devel">
http://lists.alioth.debian.org/mailman/listinfo/yaird-devel</a><br><br><br><br>---------- Forwarded message ----------<br>From: Lionel Elie Mamane <<a href="mailto:lionel@mamane.lu">lionel@mamane.lu</a>><br>To: Debian Bug Tracking System <
<a href="mailto:submit@bugs.debian.org">submit@bugs.debian.org</a>><br>Date: Thu, 5 Jan 2006 17:34:01 +0100<br>Subject: Re: yaird: Not all md devices in /dev/ after boot<br>On Thu, Jan 05, 2006 at 05:07:48PM +0100, Lionel Elie Mamane wrote:
<br><br>> Somehow, the initrd is keeping the kernel from doing its own<br>> automatic startup (the block and device drivers for /dev/sda are<br>> compiled in, as are the md RAID0 and RAID1 support), but it creates
<br>> only /dev/md0, not all of them;<br><br>Just removing the "initrd" line from the grub boot entry makes the<br>boot go fine.<br><br>--<br>Lionel<br><br><br><br><br><br></blockquote></div><br>