[pkg-cryptsetup-devel] Bug#659688: Bug#659688: cryptsetup: LVM on cryptsetup won't boot

[Roland Mas]

Jonas Meurer, 2012-02-14 00:03:37 +0100 :

> Hey Roland,

Hi,

> Am 13.02.2012 09:35, schrieb Roland Mas:
>> Package: cryptsetup Version: 2:1.4.1-2 Severity: critical
>
> To be honest I don't agree with you on the severity of this bug. 

Feel free to downgrade it; I only picked "critical" because the effects
were the same as for #659235, but I agree my setup may be a bit more
involved than usual.

[...]

> Are you confident that the bug didn't exist in 2:1.3.1-3 yet? Actually
> the only change in activating LVM volume groups from 2:1.3.1-3 to
> 2:1.4.1-1 was, that the option --sysinit is given to vgchange now.

  I don't seem to have a trace of any 2:1.3.1-3 version; I am confident
it didn't exist with 2:1.3.0-3 or 2:1.3.0-3.1.  I've been tracking
unstable with this setup for ~6 months.

> Please remove --sysinit option from line 156 of
> /usr/share/initramfs-tools/scripts/local-top/cryptroot, update your
> initramfs with 'update-initramfs -u' and see whether the problem
> disappears.

  It doesn't.  I still need to activate the LVs manually from the
initramfs shell, with --partial.

> 2:1.4.1-1 introduced much more changes in the initramfs cryptroot hook
> than in the initramfs cryptroot script. Maybe these changes introduced
> the bug you reported. Any messages given by 'update-initramfs -u'
> would be helpful to identify possible problems here.

Only the following:

# update-initramfs -u
update-initramfs: Generating /boot/initrd.img-3.2.0-1-686-pae
cryptsetup: WARNING: target obelix_crypt uses a key file, skipped
cryptsetup: WARNING: target obelix_crypt uses a key file, skipped
#

Roland.
-- 
Roland Mas

'ALL your base? No!! One tiny base continue bravely to resist.'
  -- <wiggy> in #debian-devel