Comment 1 for bug 1318351

On 11 May 2014 15:12, Martin Stjernholm <email address hidden> wrote:
> Public bug reported:
>
> I have a non-root Intel "fakeraid" volume which is not getting assembled
> automatically at startup. I can assemble it just fine with "sudo mdadm
> --assemble --scan".
>
> While trying to debug this, I encountered that it is being assembled
> when I'm booting in debug (aka recovery) mode. It turns out that
> nomdmonisw and nomdmonddf are passed to the kernel during normal boot
> only, and this is due to /etc/default/grub.d/dmraid2mdadm.cfg
> containing:
>
> GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT nomdmonddf
> nomdmonisw"
>
> Commenting out that line fixes the problem.
>
> I've gathered that this is an effort to migrate from dmraid to mdadm for
> fakeraids. I don't understand how it's supposed to work, but in my case
> dmraid is not installed, and this setting is an interference. (The
> background is that I recently added a 3 TB raid1 and was therefore
> forced to abandon dmraid in favor of mdadm since the former doesn't
> handle volumes larger than ~2 TB. So I dropped dmraid and set up mdadm
> from scratch for this new raid.)
>
> Also, I believe it's a bug that these kernel arguments are different
> between normal and recovery boot.
>
> My mdadm is 3.2.5-5ubuntu4 in a fresh trusty install.
>

Correct, I think i should be able to adjust packaging such that no
changes are required when dmraid is not installed.
At the moment automatic conversion to mdadm is not performed, as
/etc/fstab is not automatically updated to modify device names from
dmraid naming scheme to mdadm naming scheme.
Once, that is in place i'll drop dmraid2mdadm.cfg file.

--
Regards,

Dimitri.