This bug is still present and another scenario is btrfs. cryptroot is
written under the assumption there is exactly one device that needs to
be decrypted for root to be mounted, which can be very wrong for btrfs.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Thank you for reporting this bug to Ubuntu. Maverick reached EOL.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
I've tried recreating this bug with Maverick and was unable to, given
the information you've provided. Please either a) upgrade and
This bug still exists in Maverick.
I'm curious why there needs to be mappings of what device contains the
root volume, etc. Why can't it just use what is in crypttab? Is there a
reason that it needs to figure out which mount contains your root
filesystem and ignore other configured containers?
** Tags added: patch-needswork
** Tags removed: patch
--
initrd on Karmic does not support multiple encrypted LVM physical volumes.
https://bugs.launchpad.net/bugs/490917
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I can confirm that the patch works in some/maybe most instances, however
my setup requires a slight alteration to the sed line for the PVS part.
Jon's Patch Line:
if ! pvs=$(pvs | sed -r -e s| +/dev/mapper/([^ ]+) $vg
.*|\1|;tx;d;:x) ; then
My Altered Line:
if ! pvs=$(pvs | sed
Andreas the correct way would be something like pvdisplay and grepping
for the volume group that contains the root fs.
After being hit by this and finding this bugreport I decided to do
something about it. Attached is a patch that uses lvdisplay, pvs and sed
instead of dmsetup and sed to find lvm
** Tags added: patch
--
initrd on Karmic does not support multiple encrypted LVM physical volumes.
https://bugs.launchpad.net/bugs/490917
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: cryptsetup (Ubuntu)
Importance: Undecided = Low
** Changed in: cryptsetup (Ubuntu)
Status: New = Triaged
--
initrd on Karmic does not support multiple encrypted LVM physical volumes.
https://bugs.launchpad.net/bugs/490917
You received this bug notification because you
** Also affects: cryptsetup (Ubuntu)
Importance: Undecided
Status: New
--
initrd on Karmic does not support multiple encrypted LVM physical volumes.
https://bugs.launchpad.net/bugs/490917
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
nothing to fix upstream, this issue is about integration with the ubuntu
initramfs generator.
** Changed in: cryptsetup
Status: New = Invalid
--
initrd on Karmic does not support multiple encrypted LVM physical volumes.
https://bugs.launchpad.net/bugs/490917
You received this bug
vgchange -P is not the solution for this problem, because that causes a
read-only volume group, which is really unhelpful. Personally I've found
it easier to sort out the LVM situation in the initramfs busybox when
needed when having this really readonly root filesystem.
--
initrd on Karmic does
11 matches
Mail list logo
