[Bug 1279741] Re: Degraded array check, may not do what it says it's doing

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1279741

** Tags added: iso-testing

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

Title:
  Degraded array check, may not do what it says it's doing

Status in “mdadm” package in Ubuntu:
  Fix Released

Bug description:
  Degraded array check in the initramfs currently does:
  mdadm --misc --scan --detail --test

  and checks the return code. I happen to be using Intel Matrix Raid
  (container type), thus as it happens the container, and arrays are
  already assembled -> all arrays active, one disk active, one spare and
  rebuilding. At this state mdadm --misc --scan --detail --test returns
  error code 2, but it is to late to do anything but simply use that
  active array and continue to boot...

  So degraded_array question should die.

  We should attempt starting arrays with --no-degraded a few times, and
  after a timeout assemble them with --run, and if we don't have enough
  drives to start the array only then fall through to initramfs recovery
  shell.

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