Package: cryptsetup Version: 2:1.0.3-3 Severity: normal Hello,
The "cryptsetup" package installs /usr/share/initramfs-tools/hooks/cryptoroot which causes mkinitramfs to emit the misleading message: "Command failed" under certain not uncommon situations. A user trying to upgrade the kernel on a system which has cryptsetup installed could be led (erroneously) to conclude that the initramfs has not been correctly created. As far as I could make out this is happening as follows. The routine "get_lvm_device" is being called and it tries to find the base device for the root device (if it is an lvm device). It then tries to find parameters for this base device *assuming* that this base device is also an lvm device; this is the call to "dmsetup info". I believe that is the command that fails. Note that I have a system with no working entries in /etc/crypttab but I do use lvm to manage my disk. Regards, Kapil. -- -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-686 Locale: LANG=en_IN.UTF-8, LC_CTYPE=en_IN.UTF-8 (charmap=UTF-8) Versions of packages cryptsetup depends on: ii dmsetup 2:1.02.08-1 The Linux Kernel Device Mapper use ii libc6 2.3.6.ds1-4 GNU C Library: Shared libraries ii libdevmapper1.02 2:1.02.08-1 The Linux Kernel Device Mapper use ii libgcrypt11 1.2.3-2 LGPL Crypto library - runtime libr ii libgpg-error0 1.2-1 library for common error values an ii libpopt0 1.10-2 lib for parsing cmdline parameters ii libuuid1 1.39-1 universally unique id library cryptsetup recommends no packages. -- no debconf information
signature.asc
Description: Digital signature