On Sun, 6 Jul 2008 11:32:36 +0200 Florian Philipp <[EMAIL PROTECTED]> wrote:
> On Sun, 6 Jul 2008 11:03:45 +0200 > Francesco Talamona <[EMAIL PROTECTED]> wrote: > > > On Saturday 05 July 2008, Florian Philipp wrote: > > > - Could I disable the kernel auto-detection and instead add a > > > custom init-script prior to checkfs and localmount? > > > > It's impractical, check carefully all partitions with > > > > mdadm -E <partition> > > > > If it's not automatically assembled but you can do it manually, it > > means something is fooling mdadm. > > > > Try also to comment ARRAY lines in /etc/mdadm.conf. > > > > HTH > > Francesco > > > What actually happens is that the kernel starts md1 (consisting of > md0 and hdd7) BEFORE md0 (hda and hdb) is created. The most likely > cause is that the kernel starts its autodetection on the disk where / > (or /boot?) lie. > > mdadm.conf has the following lines: > > DEVICE /dev/hda1 /dev/hdb1 > DEVICE /dev/md0 /dev/hdd7 > > ARRAY /dev/md0 devices=/dev/hda1,/dev/hdb1 > ARRAY /dev/md1 devices=/dev/md0,/dev/hdd7 > > Since I can add kernel parameters for starting raids > (see /usr/src/linux/Documentation/md.txt) I'm thinking about telling > the kernel explicitly to start md0 in the hope that this happens > before autodetection. > > Stay tuned ;) > Eureka! The kernel boot-parameter raid=noautodetect md=0,/dev/hda1,/dev/hdb1 md=1,/dev/hdd7,/dev/md0 seem to work. Now the raids are built in the right order.
signature.asc
Description: PGP signature
