[Bug 1635049] Re: Boot fails with degraded mdadm raid

[Eero]

Is this bug report abandoned?

And why the bug is assigned to Dimitri John Ledkov? He is obviously
incompetent. In comment number 18 he even claimed that photographs and
screenshots aren't acceptable in bug reports even though Ubuntu's
website clearly states otherwise.

-- 
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/1635049

Title:
  Boot fails with degraded mdadm raid

Status in mdadm package in Ubuntu:
  Fix Released
Status in mdadm source package in Xenial:
  Fix Released
Status in mdadm package in Debian:
  Fix Released

Bug description:
  [Impact]

   * Systems fail to boot in certain status of mdadm arrays, requiring
  manual recovery / array assembly

   * Backport of boot logic from yakkety

  [Test Case]

   * Install a system with RAID1 and two hard-drives and boot the system with array in-sync
   * Shutdown
   * Disconnect one of the drives and thus boot, unexpectedly, degraded
   * The boot should complete.
   * Shutdown, and boot again, expecting degraded state.
   * The boot should complete.
   * Shutdown, reconnect disconnected drive, and boot again.
   * The boot should complete, add the device to the array, the array should be resyncing, and results with system with array in-sync, just like at the beginning of the testcase.

  [Regression Potential]

   * Systems may continue to fail to boot degraded.

  [Other Info]

   * Original report

  mdadm does not attempt to start partial md devices (incremental
  assembly) during initramfs and can cause system to fail to initramfs
  prompt if rootfs on md.

  http://askubuntu.com/questions/789953/how-to-enable-degraded-raid1
  -boot-in-16-04lts

  Fixed in debian mdadm 3.4-2: https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=784070

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