[pkg-cryptsetup-devel] Bug#619010: FW: Re: Bug#619010: (no subject)

[Volker Schlecht]

Hi,

booting 2.6.38, I get:

Reading all physical volumes. This may take a while.
No volume groups found.
No volume groups found.

Plus the evms warning. Then the boot hangs until it drops me into the initrd rescue console.

regards,
Volker

> ----- Ursprüngliche Nachricht -----
> Von: Volker Schlecht
> Gesendet: 11.04.11 21:22 Uhr
> An: jonas
> Betreff: Re: [pkg-cryptsetup-devel] Bug#619010: (no subject)
> 
> Hi Jonas,
> 
> Yep, I tried with both linux-image-2.6.38-2-686-bigmem and linux-image-2.6.38-2-amd64, with the identical result.
> Any other kernel previous to 2.6.38 did not show me any LVM/EVMS warnings. All I get is "Unlocking device /dev/sda2 (cryptRoot)" 
> and then the password prompt.
> 
> Attached are crypttab and fstab - the warning I see when trying to boot 2.6.38 is "LVM: No volume groups found", but I'll follow up with an 
> exact copy the next time I reboot.
> 
> Playing around with lvm at the initrd rescue prompt kinda narrows it down to a problem with LVM for me: both vgscan and pvscan yielded 
> no results at all...
> 
> regards,
> Volker
> 
> $ cat /etc/crypttab
> # <target name> <source device>         <key file>      <options>
> # cryptRoot  /dev/sda2               none  luks
> cryptRoot UUID=013dabec-dd64-4fe0-8842-cd2f92f3348e none luks
> # cryptSda3  /dev/sda3  /root/sda3Keyfile  luks
> cryptSda3 UUID=2ff9fc4a-3a46-45ff-98ea-c58a94aecf2b /root/sda3Keyfile luks
> 
> $ cat /etc/fstab
> 
> # <filesystem>                                <mount point>                  <fstype>        <mount options>                          <dump> <pass>
> 
> tmpfs                           /tmp                           tmpfs size=1G,nr_inodes=200k,mode=01777 0 0
> 
> # /dev/sda1                             /boot                          ext2            defaults,noatime                           0      2
> UUID=e82ae634-2d9e-4a7b-9ee4-623e9a31d006                       /boot                          ext2            defaults,noatime                           0      2
> 
> /dev/mapper/cryptRoot           /                              ext2            defaults,errors=remount-ro,noatime         0      1
> 
> /dev/mapper/cryptVG-LVhome      /home                          ext4            defaults,noatime,nodiratime                0      2
> 
> /dev/mapper/cryptVG-LVusr       /usr                           ext2            defaults,noatime,nodiratime                0      2
> 
> /dev/mapper/cryptVG-LVvar       /var                           ext4           defaults,noatime,nodiratime                0      2
> 
> 
> 
> > ----- Ursprüngliche Nachricht -----
> > Von: jonas
> > Gesendet: 10.04.11 23:43 Uhr
> > An: Volker Schlecht, 619010 at bugs.debian.org
> > Betreff: Re: [pkg-cryptsetup-devel] Bug#619010: (no subject)
> > 
> > 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