[Bug 1030292] Re: initramfs does not boot with mdadm (3.2.5-1ubuntu0.1)

Mon Aug 13 19:43:18 UTC 2012

This bug was fixed in the package mdadm - 3.2.5-1ubuntu0.2

---------------
mdadm (3.2.5-1ubuntu0.2) precise-proposed; urgency=low

  * Patch udev-md-raid.rules to not auto-start arrays based on detection
    of ddf or isw (imsm) signatures; this conflicts with dmraid usage in
    precise and requires more analysis before it can be enabled in SRU.
    LP: #1030292.

mdadm (3.2.5-1ubuntu0.1) precise-proposed; urgency=low

  * Stable Micro Point Bug Fix release:
    - SRU master bug (LP: #1009973)
    - Fixes segfault upon update-initramfs (LP: #969384)
    - Fixes does not allow internal bitmap on version 1.2 arrays (LP: #1022915)
  * Preserved previous behaviour, by reverting:
    - bitmap chunk size of 0 will continue to mean 512B
    - Modify the below fix, to accept previous syntax
      "b10c663 config: fix handing of 'homehost' in AUTO line."
  * Use upstream version of udev rules, instead of three slightly
    different ubuntu udev rules (LP: #968074) (LP: #1002357)
  * Add missing mdmon utility. This enables external metadata RAID
    formats: DDF and Intel Matrix Storage Management (IMSM). (LP: #957494)
  * Copy udev rule from /etc/udev/rules.d/ as well as the
    /lib/udev/rules.d/, to allow local administrator to override mdadm
    rules file (LP: #1017407)
  * debian/initramfs/local-premount: add call wait_for_udev to wait a
    little longer for RAID devices to appear. This improves
    boot reliability. (LP: #942106)

mdadm (3.2.5-1) unstable; urgency=low

  [ Michael Tokarev ]
  * new upstream (bugfix) release, fixing regression when --add'ing
    device to an array, introduced in 3.2.4, plus other minor fixes
    (Closes: #673104, #673344)
  * new patch: sha1-includes.diff to fix #include mess in new sha1.h
  * added a check into debian/checkarray to skip checking arrays created
    less than 2 weeks ago (Closes: #624273)

  [ Dmitrijs Ledkovs ]
  * Remove obsolete documentation dating back to ~etch release
  * Remove reference to obsolete documention from debconf templates
  * Update debconf templates translations
  * Remove compatability with acient initramfs-tools
  * Remove debian-specific mdadm-startall.8 in clean target

mdadm (3.2.4-1) unstable; urgency=low

  * new upstream (bugfix) release (Closes: #664088, #661552)
  * removed debian-run-udev.diff (applied upstream), and
    all RUNDIR handling from debian/rules (it is the default now)
  * add build-arch and build-indep targets to debian/rules, and
    bump Standards-Version to 3.9.3

mdadm (3.2.3-3) unstable; urgency=low

  * switch from topgit to plain 3.0 (quilt) layout, creating
    debian/patches.  Don't build-depend on quilt as patching
    is done automatically by dpkg-source.
  * debian/patches/debian-run-udev.diff by Roger Leigh (Closes: #644319, #627774)
  * update debian/mdadm.logcheck.ignore.server to recognize "k" in
    addition of "blocks" in kernel messages.  Thanks to Frédéric Brière
    for the patch (Closes: #656038)
 -- Steve Langasek <steve.langasek at ubuntu.com>   Fri, 03 Aug 2012 23:08:39 -0700

** Changed in: mdadm (Ubuntu Precise)
       Status: Fix Committed => Fix Released

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

Title:
  initramfs does not boot with mdadm (3.2.5-1ubuntu0.1)

Status in “mdadm” package in Ubuntu:
  Triaged
Status in “mdadm” source package in Precise:
  Fix Released
Status in “mdadm” source package in Quantal:
  Triaged

Bug description:
  [Impact]
  This is an SRU regression confined to precise-proposed.  Reverting part of the upstream changes is sufficient to resolve this for precise.  The issue remains unfixed in quantal; this is not a blocker for the SRU.

  [Test case]
  Verify that the submitter's machine boots successfully with the latest mdadm installed.

  [Regression potential]
  Since the existing mdadm in precise does not do auto-assembly of imsm or ddf arrays using udev rules, the risk of regression by continuing to not assemble them is minimal.  Only risk of regression is a mis-edit causing some other array, previously handled correctly in precise, to no longer be assembled; the risk of this is very small.

  After upgrading to the mdadm in precise-proposed, all newly created
  initrds do not boot. I'm using a pseudo raid with to harddisks on a
  Sony Vaio Z. Raid level is 0.  I have one  unencrypted boot partition
  and an encrypted root.

  During startup the system asks for the password to decrypt the root
  partition as usual but fails to mount the partition afterwards. I
  always get the message that there are one or more degraded partitions.
  However, with an older version of mdadm everything works perfectly.

  My current solution: Downgrade to latest stable mdadm (precise).

  Please let me know what additional information is required. I can also perform some tests as long as my (prodcutive) system is not in danger.
  ---
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: amd64
  DistroRelease: Ubuntu 12.04
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
  MDadmExamine.dev.sda: Error: command ['/sbin/mdadm', '-E', '/dev/sda'] failed with exit code 1: mdadm: cannot open /dev/sda: Permission denied
  MDadmExamine.dev.sdb: Error: command ['/sbin/mdadm', '-E', '/dev/sdb'] failed with exit code 1: mdadm: cannot open /dev/sdb: Permission denied
  MDadmExamine.dev.sdc: Error: command ['/sbin/mdadm', '-E', '/dev/sdc'] failed with exit code 1: mdadm: cannot open /dev/sdc: Permission denied
  MachineType: Sony Corporation VPCZ21C5E
  Package: mdadm 3.2.3-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-6-generic root=/dev/mapper/volumegrp01-root ro ^ kopt=root=/dev/mapper/volumegrp01-root quiet splash video=intelfb pcie_aspm=force i915.i915_enable_rc6=1 i915.lvds_downclock=1 i915.i915_enable_fbc=1 vt.handoff=7
  ProcMDstat:
   Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
   unused devices: <none>
  ProcVersionSignature: Ubuntu 3.5.0-6.6~precise1-generic 3.5.0
  Tags:  precise
  Uname: Linux 3.5.0-6-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin audio cdrom debian-tor dialout lpadmin plugdev sambashare
  dmi.bios.date: 02/09/2012
  dmi.bios.vendor: INSYDE
  dmi.bios.version: R0172H5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: dmi:bvnINSYDE:bvrR0172H5:bd02/09/2012:svnSonyCorporation:pnVPCZ21C5E:pvrJ004PS0X:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VPCZ21C5E
  dmi.product.version: J004PS0X
  dmi.sys.vendor: Sony Corporation
  etc.blkid.tab: Error: [Errno 2] No such file or directory: '/etc/blkid.tab'

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