mdadm + initramfs-tools fail to boot

Bug #493772 reported by dtaylor84
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
mdadm (Ubuntu)
Fix Released
Medium
Colin Watson
Nominated for Lucid by dtaylor84

Bug Description

Binary package hint: mdadm

/usr/share/initramfs-tools/hooks/mdadm is run through sh -e,
so exits on the first error. It attempts to copy
/lib/udev/rules.d/65-mdadm.vol_id.rules on to the initrd,
however in mdadm 2.6.7.1-1ubuntu14, this file is called
/lib/udev/rules.d/65-vol_id.rules.

As a result the copy fails. Due to the -e option, the script immediately exits, and does not copy mdadm.conf, nor any of the required kernel modules on to the initrd. An error message is produced, but update-initramfs continues and produces the initrd anyway. This leads to much confusion and great difficulty trying to manually boot the system...

The obvious fix - update hooks/mdadm to point to 65-vol_id.rules. It would, however, be nice to fix update-initramfs to NOT completely hose the system in this situation, and refuse to replace the initrd (by default, at least), but I guess that is a bug in update-initramfs.

ProblemType: Bug
Architecture: amd64
Date: Mon Dec 7 21:07:43 2009
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
Lsusb:
 Bus 002 Device 002: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 003: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MDadmExamine.dev.sda: Error: command ['/sbin/mdadm', '-E', '/dev/sda'] failed with exit code 1: mdadm: No md superblock detected on /dev/sda.
MDadmExamine.dev.sda1: Error: command ['/sbin/mdadm', '-E', '/dev/sda1'] failed with exit code 1: mdadm: No md superblock detected on /dev/sda1.
MDadmExamine.dev.sde1: Error: command ['/sbin/mdadm', '-E', '/dev/sde1'] failed with exit code 1: mdadm: No md superblock detected on /dev/sde1.
MDadmExamine.dev.sdf1: Error: command ['/sbin/mdadm', '-E', '/dev/sdf1'] failed with exit code 1: mdadm: No md superblock detected on /dev/sdf1.
MDadmExamine.dev.sdg: Error: command ['/sbin/mdadm', '-E', '/dev/sdg'] failed with exit code 1: mdadm: No md superblock detected on /dev/sdg.
MDadmExamine.dev.sdg1: Error: command ['/sbin/mdadm', '-E', '/dev/sdg1'] failed with exit code 1: mdadm: No md superblock detected on /dev/sdg1.
MachineType: System manufacturer System Product Name
NonfreeKernelModules: nvidia
Package: mdadm 2.6.7.1-1ubuntu14
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.31-16-generic root=/dev/mapper/MIRROR-root ro single
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-16.52-generic
SourcePackage: mdadm
Tags: lucid
Uname: Linux 2.6.31-16-generic x86_64
dmi.bios.date: 07/09/2009
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS M2N32-SLI DELUXE ACPI BIOS Revision 2208
dmi.board.name: M2N32-SLI DELUXE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.XX
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2N32-SLIDELUXEACPIBIOSRevision2208:bd07/09/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N32-SLIDELUXE:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
etc.blkid.tab: Error: [Errno 2] No such file or directory: '/etc/blkid.tab'

Revision history for this message
dtaylor84 (davidt-launchpad) wrote :
Revision history for this message
dtaylor84 (davidt-launchpad) wrote :
Revision history for this message
MarcRandolph (mrand) wrote :

Thank you for helping to improve Ubuntu by opening this ticket, and especially for proposing a fix!

Changed in mdadm (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Colin Watson (cjwatson) wrote :

I think it would be more correct to figure out why the rules file got renamed (perhaps an accident due to a change in dh_installudev?) and rename it back the way it used to be.

Colin Watson (cjwatson)
Changed in mdadm (Ubuntu):
assignee: nobody → Colin Watson (cjwatson)
status: Triaged → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mdadm - 2.6.7.1-1ubuntu15

---------------
mdadm (2.6.7.1-1ubuntu15) lucid; urgency=low

  * Rename debian/mdadm.vol_id.udev to debian/mdadm.mdadm-blkid.udev so that
    the rules file ends up with a more reasonable name following changes in
    debhelper 7.4.2, and adjust the initramfs hook to match (LP: #493772).
  * Build-depend on debhelper 7.4.2.
 -- Colin Watson <email address hidden> Sat, 12 Dec 2009 14:36:53 +0000

Changed in mdadm (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.