Bug#689336: initramfs-tools 0.108 cannot decrypt dm_crypt filesystems
Hi Raphael, I was indeed missing the console-setup package, and with it works as expected. (But I don't know what sequence of install / uninstall I must have done, since aptitude selects the Recommends by defaults; but this debian was installed some years ago, its history is long… In particular, I don't know if the added Recommends would have changed my running into the problem). Cheers Sam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/capf38clo_qsyodkadujmptp0ogmsz6n3hy8neovc2gmgdw7...@mail.gmail.com
Bug#689336: initramfs-tools 0.108 cannot decrypt dm_crypt filesystems
Control: severity -1 normal Control: retitle -1 provide instructions when keymap support is requested but when loadkeys or setupcon is missing Dropping the severity since most people will have console-setup installed. On Fri, 05 Oct 2012, Samuel Hym wrote: I was indeed missing the console-setup package, and with it works as expected. I believe that the update-initramfs keymap hook should display a warning about missing packages when KEYMAP=y and when some of the required executables are missing. But that's all that is needed to fix this bug. Cheers, -- Raphaël Hertzog ◈ Debian Developer Get the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121005115202.gb20...@x230-buxy.home.ouaza.com
Processed: Re: Bug#689336: initramfs-tools 0.108 cannot decrypt dm_crypt filesystems
Processing control commands: severity -1 normal Bug #689336 [initramfs-tools] initramfs-tools 0.108 cannot decrypt dm_crypt filesystems Severity set to 'normal' from 'critical' retitle -1 provide instructions when keymap support is requested but when loadkeys or setupcon is missing Bug #689336 [initramfs-tools] initramfs-tools 0.108 cannot decrypt dm_crypt filesystems Changed Bug title to 'provide instructions when keymap support is requested but when loadkeys or setupcon is missing' from 'initramfs-tools 0.108 cannot decrypt dm_crypt filesystems' -- 689336: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689336 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.b689336.134943792830396.transcr...@bugs.debian.org
Bug#689336: initramfs-tools 0.108 cannot decrypt dm_crypt filesystems
On 05/10/2012 13:52, Raphael Hertzog wrote: Dropping the severity since most people will have console-setup installed. On Fri, 05 Oct 2012, Samuel Hym wrote: I was indeed missing the console-setup package, and with it works as expected. I believe that the update-initramfs keymap hook should display a warning about missing packages when KEYMAP=y and when some of the required executables are missing. But that's all that is needed to fix this bug. And as long as this not fixed, I'm not sure we should allow this package to migrate to testing. Even if most people might have console-setup installed, this new revision may break their setup without any notification. Thus, I don't think downgrading severity to normal is the right action. Regards. -- Mehdi -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/506ed475.3090...@debian.org
Bug#689336: initramfs-tools 0.108 cannot decrypt dm_crypt filesystems
Hi, On Tue, 02 Oct 2012, Samuel Hym wrote: With 0.107, I have a line: Adding binary /bin/loadkeys not with 0.108. I bet that you're missing the console-setup package because you're not installing Recommends by default (kbd which provides loadkeys recommends console-setup which provides setupcon, initramfs-tools version 0.108 requires both loadkeys and setupcon). If that's the case, can you install console-setup and see whether it works again? I don't really know what's the proper solution though. Should initramfs-tools add a Recommends of its own on console-setup, kbd? Cheers, -- Raphaël Hertzog ◈ Debian Developer Get the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121004143835.ga12...@x230-buxy.home.ouaza.com
Bug#689336: initramfs-tools 0.108 cannot decrypt dm_crypt filesystems
Hi Michael, 2012/10/1 Michael Prokop m...@debian.org * Samuel Hym [Mon Oct 01, 2012 at 06:41:10PM +0200]: My disk is dm_crypted. After upgrading from 0.107 to 0.108, my system could not boot anymore with the newly generated ramfs: entering the passphrase did not unlock the disk, yielding the same error message as a wrong passphrase. Downgrading to 0.107 solved the problem. [...] What version of cryptsetup are you using? I'm using package version 2:1.4.3-2 but this might just be irrelevant since: Is there any visible difference between running update-initramfs -u -v for 0.107 and 0.108? Yes! With 0.107, I have a line: Adding binary /bin/loadkeys not with 0.108. What about differences between the generated initramfs (check e.g. with lsinitramfs /boot/initrd.img-$(uname -r))? Similarly, the diff is: --- /dev/fd/632012-10-02 17:26:29.136907406 +0200 +++ /dev/fd/622012-10-02 17:26:29.116907309 +0200 @@ -1,4 +1,4 @@ -/root/initrd.img-3.2.0-3-amd64-0.107 +initrd.img-3.2.0-3-amd64 . scripts scripts/functions @@ -955,7 +955,6 @@ bin/reboot bin/mkdir bin/nuke -bin/loadkeys bin/gunzip bin/umount bin/false @@ -990,7 +989,6 @@ etc/ld.so.conf etc/lvm etc/lvm/lvm.conf -etc/boottime.kmap.gz etc/modprobe.d etc/modprobe.d/blacklist-cups-usblp.conf etc/modprobe.d/alsa-base.conf Does setting KEYMAP=y in /etc/initramfs-tools/initramfs.conf help? No change. It was set to n, but there does not seem to make any difference, strangely enough. Regards Sam
Bug#689336: initramfs-tools 0.108 cannot decrypt dm_crypt filesystems
Package: initramfs-tools Version: 0.108 Severity: critical Justification: breaks the whole system My disk is dm_crypted. After upgrading from 0.107 to 0.108, my system could not boot anymore with the newly generated ramfs: entering the passphrase did not unlock the disk, yielding the same error message as a wrong passphrase. Downgrading to 0.107 solved the problem. Best regards Samuel Hym --- System information. --- Architecture: amd64 Kernel: Linux 3.2.0-3-amd64 Debian Release: wheezy/sid 990 unstable ftp.fr.debian.org 500 testing ftp.fr.debian.org 500 stable ftp.fr.debian.org 1 experimental ftp.fr.debian.org --- Package information. --- Depends (Version) | Installed =-+- klibc-utils (= 2.0-1~) | 2.0.1-1 cpio | 2.11-8 kmod | 9-2 OR module-init-tools | 9-2 udev | 175-7 Recommends (Version) | Installed -+-=== busybox (= 1:1.01-3) | OR busybox-initramfs | OR busybox-static | 1:1.20.0-7 Suggests (Version) | Installed ==-+-=== bash-completion | 1:2.0-1 --- Output from package bug script --- -- initramfs sizes -- /proc/cmdline BOOT_IMAGE=/vmlinuz-3.2.0-3-amd64 root=/dev/mapper/salme-root ro quiet -- resume RESUME=/dev/mapper/salme-swap_1 -- /proc/filesystems ext3 fuseblk iso9660 -- lsmod Module Size Used by ip6table_filter 12540 0 ip6_tables 22175 1 ip6table_filter iptable_filter 12536 0 ip_tables 22042 1 iptable_filter ebtable_nat 12580 0 ebtables 26235 1 ebtable_nat x_tables 19073 5 ebtables,ip_tables,iptable_filter,ip6_tables,ip6table_filter ppdev 12763 0 lp 17149 0 uinput 17440 1 nls_utf8 12456 1 isofs 35171 1 fuse 61981 3 firewire_sbp2 17993 0 loop 22641 2 kvm_intel 121968 0 kvm 287662 1 kvm_intel snd_hda_codec_idt 53792 1 snd_hda_intel 26345 2 snd_hda_codec 78031 2 snd_hda_intel,snd_hda_codec_idt snd_hwdep 13186 1 snd_hda_codec snd_pcm_oss 41081 0 snd_mixer_oss 17916 1 snd_pcm_oss snd_pcm 63900 3 snd_pcm_oss,snd_hda_codec,snd_hda_intel snd_page_alloc 13003 2 snd_pcm,snd_hda_intel snd_seq_midi 12848 0 snd_seq_midi_event 13316 1 snd_seq_midi arc4 12458 2 snd_rawmidi 23060 1 snd_seq_midi snd_seq 45093 2 snd_seq_midi_event,snd_seq_midi iwl3945 51641 0 iwl_legacy 48145 1 iwl3945 snd_seq_device 13176 3 snd_seq,snd_rawmidi,snd_seq_midi mac80211 192768 2 iwl_legacy,iwl3945 cfg80211 137140 3 mac80211,iwl_legacy,iwl3945 snd_timer 22917 2 snd_seq,snd_pcm snd 52850 15 snd_timer,snd_seq_device,snd_seq,snd_rawmidi,snd_pcm,snd_mixer_oss,snd_pcm_oss,snd_hwdep,snd_hda_codec,snd_hda_intel,snd_hda_codec_idt joydev 17266 0 iTCO_wdt 17081 0 iTCO_vendor_support 12704 1 iTCO_wdt i2c_i801 16870 0 pcmcia 32691 0 soundcore 13065 1 snd dell_laptop 17120 0 rfkill 19012 3 dell_laptop,cfg80211 acpi_cpufreq 12935 0 parport_pc 22364 1 psmouse 64455 0 yenta_socket 22899 0 parport 31858 3 parport_pc,lp,ppdev pcmcia_rsrc 17533 1 yenta_socket dell_wmi 12477 0 sparse_keymap 12760 1 dell_wmi rng_core 12652 0 mperf 12453 1 acpi_cpufreq dcdbas 13307 1 dell_laptop ac 12624 0 processor 28157 3 acpi_cpufreq coretemp 12898 0 pcmcia_core 18294 3 pcmcia_rsrc,yenta_socket,pcmcia evdev 17562 21 battery 13109 0 power_supply 13475 3 battery,ac,dell_laptop serio_raw 12931 0 ext3 161867 3 mbcache 13065 1 ext3 jbd 56902 1 ext3 sha256_generic 16797 2 cryptd 14517 0 aes_x86_64 16796 4 aes_generic 33026 1 aes_x86_64 cbc 12754 2 dm_crypt 22586 1 microcode 25793 0 dm_mirror 17707 0 dm_region_hash 13459 1 dm_mirror dm_log 13528 2 dm_region_hash,dm_mirror dm_mod 63545 15 dm_log,dm_mirror,dm_crypt usbhid 36379 0 hid 81288 1 usbhid sg 25874 0 sd_mod 36136 3 crc_t10dif 12348 1 sd_mod ata_generic 12479 0 i915 356043 3 ata_piix 29535 2 sdhci_pci 17976 0 libata 140589 2 ata_piix,ata_generic firewire_ohci 35772 0 uhci_hcd 26865 0 firewire_core 48407 2 firewire_ohci,firewire_sbp2 sdhci 27053 1 sdhci_pci tg3 118925 0 mmc_core 72460 2 sdhci,sdhci_pci video 17628 1 i915 i2c_algo_bit 12841 1 i915 drm_kms_helper 27227 1 i915 drm 167670 4 drm_kms_helper,i915 thermal 17383 0 ehci_hcd 40215 0 crc_itu_t 12347 1 firewire_core wmi 13243 1 dell_wmi button 12937 1 i915 libphy 19018 1 tg3 scsi_mod 162372 4 libata,sd_mod,sg,firewire_sbp2 usbcore 128498 4 ehci_hcd,uhci_hcd,usbhid usb_common 12354 1 usbcore i2c_core 23876 5 drm,drm_kms_helper,i2c_algo_bit,i915,i2c_i801 thermal_sys 18040 3 thermal,video,processor -- /etc/initramfs-tools/modules -- /etc/kernel-img.conf # Kernel image management overrides # See kernel-img.conf(5) for details do_symlinks = yes relative_links = yes do_bootloader = no do_bootfloppy = no do_initrd = yes link_in_boot = no -- /etc/initramfs-tools/initramfs.conf MODULES=most BUSYBOX=y KEYMAP=n COMPRESS=gzip DEVICE= NFSROOT=auto -- /etc/initramfs-tools/update-initramfs.conf update_initramfs=yes backup_initramfs=no -- /etc/crypttab # hda5_crypt /dev/hda5 none luks hda5_crypt UUID=0e05f1cf-9a96-4ba7-a7e0-4ef0fdbcd2ba none luks -- mkinitramfs hooks /etc/initramfs-tools/hooks/: /usr/share/initramfs-tools/hooks:
Bug#689336: initramfs-tools 0.108 cannot decrypt dm_crypt filesystems
* Samuel Hym [Mon Oct 01, 2012 at 06:41:10PM +0200]: My disk is dm_crypted. After upgrading from 0.107 to 0.108, my system could not boot anymore with the newly generated ramfs: entering the passphrase did not unlock the disk, yielding the same error message as a wrong passphrase. Downgrading to 0.107 solved the problem. [...] What version of cryptsetup are you using? Is there any visible difference between running update-initramfs -u -v for 0.107 and 0.108? What about differences between the generated initramfs (check e.g. with lsinitramfs /boot/initrd.img-$(uname -r))? Does setting KEYMAP=y in /etc/initramfs-tools/initramfs.conf help? regards, -mika- signature.asc Description: Digital signature