Comment 12 for bug 541058

@Surbhi

mdadm is supposed to be able to assemble arrays that are not explicitly
specified in the configuration file by scanning superblocks during bootup.
That's what this bug is about. Explicitly specifying arrays in mdadm.conf is
a workaround, not the solution.

On Wed, Sep 15, 2010 at 8:00 AM, Surbhi Palande
<email address hidden>wrote:

> @tombert, I suggest you to do the following:
> 1) /usr/share/mdadm/mkconf
> 2) compare the output of step1 with the output of /etc/mdadm/mdadm.conf. If
> your array definition is not found in
> /etc/mdadm/mdadm.conf, then you will need to add this array definition
> manually (using its uuids).
> (* The initramfs/hook for mdadm shall soon be updated. It should create a
> mdadm.conf for you or warn you when an active array definition is not found
> in mdadm.conf)
> 3) update-initramfs -c -k <kernel-version>. (Verify that the initramfs has
> your array definition in it)
> 4) update-grub
> 5) reboot
>
> This should ensure that your raid is configured while booting. * If
> /var/run/mdadm is not present then mdadm makes a map in /var/run/ which is
> already present in initramfs. So this should not be a show stopper for raid
> bring up. (please refer to man mdadm for more information)
> Marking this bug as invalid as of now.
>
>
> ** Changed in: mdadm (Ubuntu)
> Status: Confirmed => Invalid
>
> --
> [->UUIDudev] mdadm fails to assemble raid during boot
> https://bugs.launchpad.net/bugs/541058
> You received this bug notification because you are a direct subscriber
> of the bug.
>