[Bug 942106] Re: software raid doesn't assemble before mount on boot

[Launchpad Bug Tracker]

This bug was fixed in the package mdadm - 3.2.5-1ubuntu1

---------------
mdadm (3.2.5-1ubuntu1) quantal; urgency=low

  * Merge from Debian testing. (LP: #920324)  Remaining changes:
    - Call checks in local-premount to avoid race condition with udev
      and opening a degraded array.
    - d/initramfs/mdadm-functions: Record in /run when boot-degraded
      question has been asked so that it is only asked once
    - pass --test to mdadm to enable result codes for degraded arrays.
    - debian/control: we need udev and util-linux in the right version. We
      also remove the build dependency from quilt and docbook-to-man as both
      are not used in Ubuntus mdadm.
    - debian/initramfs/hook: kept the Ubuntus version for handling the absence
      of active raid arrays in <initramfs>/etc/mdadm/mdadm.conf
    - debian/initramfs/script.local-top.DEBIAN, debian/mdadm-startall,
      debian/mdadm.raid.DEBIAN: removed. udev does its job now instead.
    - debian/mdadm-startall.sgml, debian/mdadm-startall.8: documentation of
      unused startall script
    - debian/mdadm.config, debian/mdadm.postinst - let udev do the handling
      instead. Resolved merge conflict by keeping Ubuntu's version.
    - debian/mdadm.postinst, debian/mdadm.config, initramfs/init-premount:
      boot-degraded enablement; maintain udev starting of RAID devices;
      init-premount hook script for the initramfs, to provide information at
      boot
    - debian/mkconf.in is the older mkconf. Kept the Ubuntu version.
    - debian/rules: Kept Ubuntus version for installing apport hooks, not
      installing un-used startall script.
    - debian/install-rc, check.d/_numbers, check.d/root_on_raid: Ubuntu partman
      installer changes
    - debian/presubj: Dropped this unused bug reporting file. Instead use
      source_mdadm.py act as an apport hook for bug handling.
    - d/p/debian-changes-3.1.4-1+8efb9d1ubuntu4: mdadm udev rule
      incrementally adds mdadm member when detected. Starting such an
      array in degraded mode is possible by mdadm -IRs. Using mdadm
      -ARs without stopping the array first does nothing when no
      mdarray-unassociated device is available. Using mdadm -IRs to
      start a previously partially assembled array through incremental
      mode. Keeping the mdadm -ARs for assembling arrays which were for
      some reason not assembled through incremental mode (i.e through
      mdadm's udev rule).

  * Additional Ubuntu changes:
      - debian/initramfs/local-premount: add call wait_for_udev to wait a
      little longer for RAID devices to appear (LP: #942106)

  * Dropped Ubuntu changes:
    - Build udeb with -O2 on ppc64, working around a link error. Builds
      fine without it on debian.
    - rename debian/mdadm.vol_id.udev to debian/mdadm.mdadm-blkid.udev so
      that the rules file ends up with a more reasonable name. debian/rules
      changes for adding ubuntu's udev rule corresponding to mdadm. As we
      are now using 'upstream' udev rules see 3.2.3-2ubuntu2.

  * Changes to Ubuntu changes:
    - debian/source_mdadm.py: make apport hook python 2 and 3 compatible
      (LP: #1013171).

  * New upstream release closes this bugs:
    - mdadm --detail --scan segfaults during update-initramfs (LP: #969384)
 -- Dmitrijs Ledkovs <dmitrij.ledkov at ubuntu.com>   Fri, 15 Jun 2012 15:31:59 +0100

** Changed in: mdadm (Ubuntu Quantal)
       Status: Confirmed => Fix Released

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

Title:
  software raid doesn't assemble before mount on boot

Status in “mdadm” package in Ubuntu:
  Fix Released
Status in “update-manager” package in Ubuntu:
  Fix Released
Status in “mdadm” source package in Precise:
  Confirmed
Status in “update-manager” source package in Precise:
  Fix Released
Status in “mdadm” source package in Quantal:
  Fix Released
Status in “update-manager” source package in Quantal:
  Fix Released

Bug description:
  Booting a system with a software raid device can randomly or systematically
  fail.

  The system boot will fail at the initramfs stage and the system complain
  that it can't find the software raid device.

  The user ends up on the initramfs console. Rebooting might solve the issue
  (or not).

  ---

  Happens at once on boot.

  I happened to use the kernel 3.0.0-17, because the computer would not boot because of the bug that the line
  udevadm settle
  is missing in function degraded_arrays() in the file /usr/share/initramfs-tools/scripts/mdadm-functions which results in a halt on an initram fs console.

  ---

  ProblemType: Crash
  Date: Mon Feb 27 17:46:23 2012
  ExecutablePath: /usr/bin/update-manager
  ExecutableTimestamp: 1326448883
  InterpreterPath: /usr/bin/python2.7
  ProcCmdline: /usr/bin/python ./xorg_fix_proprietary.py
  ProcCwd: /tmp/update-manager-Qp_QfE
  PythonArgs: ['/usr/bin/update-manager']
  Traceback:
   Traceback (most recent call last):
     File "./xorg_fix_proprietary.py", line 160, in <module>
       if ver and apt_pkg.VersionCompare(ver, "2:1.5.0") > 0:
   ValueError: _system not initialized
  UserGroups:

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