[Bug 490917] Re: initrd on Karmic does not support multiple encrypted LVM physical volumes.
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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/490917 Title: initrd on Karmic does not support multiple encrypted LVM physical volumes. To manage notifications about this bug go to: https://bugs.launchpad.net/cryptsetup/+bug/490917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 490917] Re: initrd on Karmic does not support multiple encrypted LVM physical volumes.
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 test or b) increase the verbosity of the steps to recreate it so we can try again. Please feel free to report any other bugs you may find. ** Changed in: cryptsetup (Ubuntu) Status: Triaged = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/490917 Title: initrd on Karmic does not support multiple encrypted LVM physical volumes. To manage notifications about this bug go to: https://bugs.launchpad.net/cryptsetup/+bug/490917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 490917] Re: initrd on Karmic does not support multiple encrypted LVM physical volumes.
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? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/490917 Title: initrd on Karmic does not support multiple encrypted LVM physical volumes. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 490917] Re: initrd on Karmic does not support multiple encrypted LVM physical volumes.
** 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 490917] Re: initrd on Karmic does not support multiple encrypted LVM physical volumes.
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 -r -e s| +/dev/mapper/([^ ]+)\s+$vg .*|\1|;tx;d;:x) ; then The reason being one space character between the PV column and the VG column can't be guaranteed, so the \s+ will match any number of spaces. Here's the output of my pvs currently, note the 2 spaces on the latter two physical volumes: PV VG Fmt Attr PSize PFree /dev/mapper/sda5_crypt octopus lvm2 a- 232.64G 0 /dev/mapper/sdb1_crypt octopus lvm2 a- 698.63G 0 /dev/mapper/sdd_crypt octopus lvm2 a- 698.64G 0 /dev/mapper/sde_crypt octopus lvm2 a- 931.51G 33.92G -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 490917] Re: initrd on Karmic does not support multiple encrypted LVM physical volumes.
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 dependencies. Only tested for lvm on luks. Will definitely not work for dm subsystems other than lvm (but as the function name is get_lvm_deps I don't think that was supposed to work anyway.) Also, it will happily ignore any regular devices (/dev/sdx) that lvm depends on, so if your lvm volume group is not encrypted, it will issue a warning, but will probably work anyway. ** Patch added: cryptroot.diff http://launchpadlibrarian.net/39751587/cryptroot.diff -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 490917] Re: initrd on Karmic does not support multiple encrypted LVM physical volumes.
** 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 490917] Re: initrd on Karmic does not support multiple encrypted LVM physical volumes.
** 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 are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 490917] Re: initrd on Karmic does not support multiple encrypted LVM physical volumes.
** 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 490917] Re: initrd on Karmic does not support multiple encrypted LVM physical volumes.
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 490917] Re: initrd on Karmic does not support multiple encrypted LVM physical volumes.
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 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
