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

[Ubuntu QA's Bug Bot]

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

-- 
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:
  New

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