Ubuntu
casper package

[PATCH] mapper and mdadm fail at boot

Bug #865529 reported by Tyler Gates on 2011-10-03

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	casper (Ubuntu)	Fix Released	Medium	Unassigned

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.

Tags:

Revision history for this message

Tyler Gates (tgates81) wrote on 2011-10-03:

Add support for mapper and md devices so casper doesn't panic panic when the volumes are found Edit (1.1 KiB, text/plain)

Revision history for this message

Tyler Gates (tgates81) wrote on 2011-10-03:

I should point out this only happens when the appropriate tools to read the devices are installed on the live environment.

Revision history for this message

Ubuntu Foundations Team Bug Bot (crichton) wrote on 2011-10-03:

The attachment "Add support for mapper and md devices so casper doesn't panic panic when the volumes are found" of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-sponsors please also unsubscribe the team from this bug report.

[This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.]

tags:

added: patch

Brian Murray (brian-murray) on 2011-10-20

Changed in casper (Ubuntu):
importance:	Undecided → Medium

Stéphane Graber (stgraber) on 2012-10-03

Changed in casper (Ubuntu):
status:	New → Fix Committed

Revision history for this message

Launchpad Janitor (janitor) wrote on 2012-10-03:

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 <email address hidden> Wed, 03 Oct 2012 17:46:39 -0400