I found no /dev/hd?? devices. But here is the whole procedure: * Add /dev/md0, /dev/hda1,/dev/hd... to /etc/minitrd/files * Execute mkinitrd to create image. It should now have the needed /dev nodes. * Mount image and copy to a directory: -- mkdir mnt -- mount -o loop,ro -t cramfs initrd.img-2.6.8-2-386 mnt -- cd mnt -- tar cf ../initrd.tar . -- cd .. -- mkdir initrd -- cd initrd -- tar xf ../initrd.tar * Edit file called script * Add mdadm command to assemble md device:
mdadm -A /dev/md0 -R -u \ 5db17407:3ad7f157:fa8e6ea1:abe0953f /dev/hda1 /dev/hdc1 /dev/hde1 * Create new image from directory: mkcramfs initrd initrd.img-2.6.8-2-386 That should do it. No need to add kernel parameters. David On Sunday 23 October 2005 10:54 am, David Koski wrote: > I have compiled raid drivers into the kernel to get raid on root working. > But now I am trying to get another kernel without drivers compiled in to > work. mkinitrd did not add the raid1 module needed for the root partition > so I added it to /etc/mkinitrd/modules. Now the initrd.img image looks good > and includes /dev/md0 as well as raid1 in loadmodules. But md0 (boot) will > not assemble and it fails to boot. However, md2 (root) assembles fine. I > have tried the following kernel parameter without success: > > md=0,/dev/hda1,/dev/hdc1,/dev/hde1 > > menu.list: > > 106 title Debian GNU/Linux, kernel 2.6.8-2-386 > 107 root (hd0,0) > 108 kernel /vmlinuz-2.6.8-2-386 root=/dev/md2 ro > md=0,/dev/hda1,/dev/hdc1,/dev/hde1 > 109 initrd /initrd.img-2.6.8-2-386 > 110 savedefault > 111 boot > > Any ideas? > > Regards, > David Koski > [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
