Bug#304483: mkinitrd does not create "mdadm -A" record for /boot partition on raid1 when initrd.img is built

[Erik van Konijnenburg <ekonijn@xs4all.nl>]

On Wed, May 18, 2005 at 04:52:55PM -0700, rds wrote:
> 
> Re: Bug#304483: mkinitrd does not create "mdadm -A" record for /boot partition
> on raid1 when initrd.img is built
> 
> > i'm a bit puzzled why you expect from initrd to mount all the mdadm
> > partitions, from your report i see that the initrd is loaded
> > and booted. it also seems to find your root device.
> > seems more a failure of mdadm to bring up all your raid?
> 
> The /boot partition is on /dev/md1 which is mdadm RAID1 array. I would expect
> that initrd assembles the /dev/md1 array when the system boots, right? It does
> assemble /dev/md2 (/) and /dev/md3  (swap), but not /dev/md1. As a result, fsck
> on /boot (which hosted on /dev/md1) fails and normal system's boot-up sequence
> stops.
> 
> I had to disable fsck on /boot to bring up the system. And after that I have to
> assemble /dev/md1 and mount it to /boot MANUALLY EVERY TIME I REBOOT THE
> SYSTEM.
> 
> Please let me know if you need any other info.

Quick question: why not add an auto=md clause to /etc/mdadm/mdadm.conf?
That way you have the option of *not* assembling some md drives if necessary.

Regards,
Erik