[Bug 1318351] Re: mdadm doesn't assemble imsm raids during normal boot

[Eren]

Hello,

This bug persists in fresh Ubuntu 14.04.2 Server (I confirm #3). I have
a FakeRAID controller in one of our supermicro servers. Installation
occurs normally, but when first booted, it doesn't boot correctly. I see
that "nomdmonddf nomdmonisw" is appended to the boot parameters. For
first boot, I needed to remove those lines via grub before booting, boot
the box, and comment out the file:

/etc/default/grub.d/dmraid2mdadm.cfg

When those parameters are not included, it runs perfectly. I didn't need
to change any mdadm.conf or other. I just needed to remove those boot
parameters.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to mdadm in Ubuntu.
https://bugs.launchpad.net/bugs/1318351

Title:
  mdadm doesn't assemble imsm raids during normal boot

Status in mdadm package in Ubuntu:
  Confirmed

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1318351/+subscriptions