Bug#304483: mkinitrd does not create "mdadm -A" record for /boot partition on raid1 when initrd.img is built
reassign 304483 madadm
stop
On Thu, 19 May 2005, rds wrote:
> I can't try this right now but I doubt this would help. The reason is that when
> the system boots initrd would not know how to assemble /dev/md1 because
> .../initrimg/script does not contain "mdadm -A" record for /dev/md1. This is
> the root of the problem.
no it is not!
initrd-tools enables the root partition for the pivot_root,
and if existing the swap partition,
everything else need to be done by mdadm init scripts.
you haven't answered my question: are you using udev?
anyway reassigning as that doesn't belong to initrd-tools.
hope the mdadm maintainers have a better clue what's going
wrong here. feel free to keep me on cc.
> >From the original bug report:
>
> When #mkinitrd -o /boot/initrd.img is run, it creates only records for /dev/md2
> (/) and /dev/md3 (swap) but not for /dev/md1 (/boot) [ even though /boot is
> mounted and fully functional when mkinitrd is run ].
>
yes indeed that's true and
i'm happy that the initrd-tools are working so far.
why mdadm doesn't assemble your /boot needs moreinfo,
that you haven't provided yet, what does the output
of cat /etc/default/mdadm show?
do you have a start up link in your default rl for mdadm?
--
maks
Reply to: