[pkg-cryptsetup-devel] Bug#619010: Bug#619010: (no subject)
jonas
jonas at freesources.org
Sun Apr 10 21:43:45 UTC 2011
Hello Volker,
Sorry for the long delay, I was away the last two weeks.
Unfortunately I'm unable to reproduce your bugreport so far. Did you
try the latest linux-image-2.6.38-2-686-bigmem package with cryptsetup
2:1.2.0-2?
I only checked the amd64 2.6.38 debian kernel
(linux-image-2.6.38-2-amd64), but that one worked with several different
LVM-on-LUKS setups.
On Wed, Sun, 20 Mar 2011 13:43:59 +0100, "Volker Schlecht"
<vschlecht at gmx.net> wrote:
> Booting a stock 686-bigmem 2.6.38 kernel hangs after loading the
> initrd with the message "LVM no volumes found" and "evms_activate
> failed".
Both warnings are ok if your setup is LVM on top of LUKS. The initramfs
script searches for a LVM or EVMS group to enable before unlocking the
device.
Please provide more precise information about your setup:
- content of /etc/crypttab
- content of /etc/fstab
- exact output of the boot process: what is the last output you see?
> Booting an older 2.6.37 stock kernel works on the same system.
You should see the LVM/EVMS warnings with the 2.6.37 kernel as well,
right?
greetings,
jonas
More information about the pkg-cryptsetup-devel
mailing list