[Bug 865529] Re: [PATCH] mapper and mdadm fail at boot

[Launchpad Bug Tracker]

This bug was fixed in the package casper - 1.327

---------------
casper (1.327) quantal; urgency=low

  [ Tim Lunn ]
  * add gnome-shell favorites tweak to 25adduser
  * Add 16gdmnopasswd script, removes gdm password dialog for live user.

  [ Stéphane Graber ]
  * Fix casper when running on some RAID systems. (LP: #1047316, LP: #965735)
  * Apply patch by Tyler Gates to try and better handle dm devices, should help
    with the above change too. (LP: #865529)
  * Use /sys/class/net/ instead of hardcoded eth* devices.
    (LP: #905828, LP: #962546)
  * Allow overriding username/userfullname/hostname on the boot command line
    as is mentioned in the manpage but was never implemented.
    Note that when using persistence, those used for the first boot will be
    remembered through /etc/casper.conf (LP: #907482)
  * Reset oem-config/enable to false every boot. (LP: #838680)
  * Add Breaks/Replaces to ubiquity-casper to properly upgrade when both
    casper and ubiquity-casper are installed. (LP: #1046300)
  * Apply patch by cleary to avoid hang in 41apt_cdrom when .disk/info doesn't
    exist. (LP: #909919)
  * Eject by block device instead of mountpoint, this should avoid ejecting
    the cdrom on USB installations. (LP: #869238)
  * Add 'check' target to debian/rules based on ubiquity's (LP: #570243)
 -- Stephane Graber <stgraber at ubuntu.com>   Wed, 03 Oct 2012 17:46:39 -0400

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

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

Title:
  [PATCH] mapper and mdadm fail at boot

Status in “casper” package in Ubuntu:
  Fix Released

Bug description:
  Booting from a CD in a local environment with mdadm or lvm devices
  (/dev/md* and /dev/mapper/*) that have file systems created on them
  causes casper to fall back to the 'ugly hack' section in
  find_livefs(). This in turn returns the livefs_root variable to be
  these devices which will cause the boot process to panic since it
  can't find the appropriate file structure.

  The attached patch will check if these devices exist and run check_dev
  on them (just as the rest of the code does for other types of devices)
  to determine if they are a valid livefs device. Then, if a valid
  livefs is not found on the block device, the 'ugly hack' can be
  honored.

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