thanks a lot,
you told me the rigt way. I had to add the lines "raid1" and "md_mod" to
/etc/mkinitrd/modules. After recreating the initrd image "mkinitrd -o
/boot/initrd.img-2.6.17.8 /lib/modules/2.6.17.8" the server boots into
both raid disk correctly.
isp:~# cat /proc/mdstat
Personalities : [raid1]
md0 : active raid1 hda1[0] hdb1[1]
154191744 blocks [2/2] [UU]
unused devices: <none>
Andreas Pelzner
>
> On Monday August 28, Andreas.Pelzner@xxxxxxxxxxxxx wrote:
> > Pls. find the kernel messages here.
>
> Thanks.
>
> 'md' and the drivers for you disks are not compiled into the kernel
> but are present as modules in an 'initrd'.
> So the kernel parameter or
> md=0,/dev/hda1,/dev/hdb1
> is ignored and the code in the inird is completely responsible for
> assembling md0.
> You have a look at what it does:
>
> mkdir /foo
> mount -t cramfs /initrd.img /foo
> ^^^^^^^^^^^
>
> You have to find the initrd that is being used and use that name here.
> Then have a look at etc mdadm.conf in /foo.
>
> Once you understand the problem you will need to remake your initrd to
> get this right.
>
> NeilBrown
> -
> 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
>
-
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
