This script has gone and it is now done from udev which should not loop
** Changed in: lvm-common (Ubuntu)
Status: Unconfirmed => Fix Released
--
lvm on cryptsetup with initramfs infinite loop
https://bugs.launchpad.net/bugs/69217
You received this bug notification because you are a memb
FWIW, it may not be the right thing to do, but John Lenz's modification
works for me (^_^)
--
lvm on cryptsetup with initramfs infinite loop
https://launchpad.net/bugs/69217
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
This long delay at every boot is most annoying on a laptop, where
battery time is precious. Ironically, laptops are also where having an
encrypted filesystem makes a lot of sense...
More than 3 months after this bug has been submitted, the status is
still "Unconfirmed", with an importance "Undecid
I have also hit this bug (see also bug #21878).
I have /dev/hda3 as a LUKS partition which gets mounted on
/dev/mapper/cdisk. This then uses lvm to give me /dev/mapper/ubuntu-root
and /dev/mapper/ubuntu-home which are mounted at the obvious points.
As my root volume can't appear until cryptroot i
Well ok. At the very least, you need to provide some option of
disabling the lvm script... assuming a device is in /dev/mapper is not
really all that good to go into an infinite loop!
So I see a few options:
1) At the very least, check /proc/cmdline for something like
"norootlvm", to allow to di
I believe that this breaks the intended functionality of the loop. The
purpose of the loop is to keep scanning devices until the ones
containing the volume group appear, then enable the volume group. The
line you added performs essentially the same scan only once, and if it
is not found the first
