Your message dated Fri, 31 Oct 2008 07:25:54 +0100 with message-id <1225434354.2294.2.camel@hidalgo> and subject line Re: Bug#503062: News? has caused the Debian Bug report #503062, regarding initramfs-tools: /conf/conf.d/cryptroot file is missing in initrd to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 503062: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=503062 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: initramfs-tools: /conf/conf.d/cryptroot file is missing in initrd
- From: Christian Jaeger <christian-novo@jaeger.mine.nu>
- Date: Wed, 22 Oct 2008 11:02:11 +0200
- Message-id: <[🔎] 20081022090211.11323.87402.reportbug@novo>
Package: initramfs-tools Version: 0.92j Severity: critical Justification: breaks the whole system I did install testing on my new ThinkPad last April, and choose to put the root partition under encryption on lvm, using the offered Debian installer functionality. This has worked fine and I soon switched to self-built kernels, and using update-initramfs to create the corresponding initrd's. IIRC I've successfully installed at least two or three versions of initrd's during this time. (On Jun 11 I wrote a wrapper script around update-initramfs to aid me remember which options to use.) Somehow initrd.img-2.6.26.3 from August or September was broken and didn't boot. It would not ask for the root partition password anymore but just hang upon boot. On September 11 and 12 I went through the trouble debugging the issue, and found out that the initrd was now missing the conf/conf.d/cryptroot file. I re-added that file back to the new initrd and the system would ask for the passphrase and boot again. Here's the diff: # diff -rubBN C D diff -rubBN C/conf/conf.d/cryptroot D/conf/conf.d/cryptroot --- C/conf/conf.d/cryptroot 1970-01-01 01:00:00.000000000 +0100 +++ D/conf/conf.d/cryptroot 2008-09-11 23:19:25.000000000 +0200 @@ -0,0 +1 @@ +target=sda8_crypt,source=/dev/sda8,key=none,lvm=main-root I didn't find out why this happened, but hoped that maybe somehow the problem would fix itself (maybe by update-initramfs looking at the old initrd, which is obviously not the case, or whatever). Now I installed a newer kernel recently and the problem happened again. What should I do, hack up a script that automatically fixes the generated initrd, or where lies the problem? -- Package-specific info: -- /proc/cmdline root=/dev/mapper/main-root ro quiet -- /proc/filesystems reiserfs ext3 -- lsmod Module Size Used by binfmt_misc 10060 1 nvidia 8105936 22 rfcomm 40288 0 l2cap 22720 5 rfcomm bluetooth 57764 4 rfcomm,l2cap uinput 8832 1 acpi_cpufreq 7952 1 cpufreq_powersave 2368 0 cpufreq_stats 5088 0 cpufreq_userspace 3948 0 cpufreq_ondemand 8464 1 cpufreq_conservative 8264 0 freq_table 5328 3 acpi_cpufreq,cpufreq_stats,cpufreq_ondemand ext3 136976 1 jbd 52776 1 ext3 mbcache 9476 1 ext3 loop 17420 0 firewire_sbp2 16408 0 snd_usb_audio 94880 0 snd_usb_lib 18176 1 snd_usb_audio arc4 2240 2 snd_seq_dummy 3460 0 ecb 3392 2 snd_hda_intel 449300 0 iwl4965 200520 0 pcmcia 38872 0 firmware_class 8960 2 iwl4965,pcmcia snd_seq_oss 33664 0 iwlcore 29700 1 iwl4965 snd_seq_midi 7424 0 snd_seq_midi_event 8512 2 snd_seq_oss,snd_seq_midi snd_seq 57888 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event snd_pcm_oss 43360 0 rfkill 7584 2 iwlcore snd_mixer_oss 17088 1 snd_pcm_oss snd_rawmidi 24992 2 snd_usb_lib,snd_seq_midi snd_pcm 86536 3 snd_usb_audio,snd_hda_intel,snd_pcm_oss mac80211 155284 2 iwl4965,iwlcore snd_seq_device 8212 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq,snd_rawmidi snd_hwdep 8776 1 snd_usb_audio yenta_socket 25676 1 rsrc_nonstatic 11392 1 yenta_socket joydev 11968 0 snd_timer 23888 2 snd_seq,snd_pcm rtc_cmos 11064 0 pcmcia_core 41060 3 pcmcia,yenta_socket,rsrc_nonstatic snd 67976 11 snd_usb_audio,snd_hda_intel,snd_seq_oss,snd_seq,snd_pcm_oss,snd_mixer_oss,snd_rawmidi,snd_pcm,snd_seq_device,snd_hwdep,snd_timer rtc_core 18820 1 rtc_cmos rtc_lib 3648 1 rtc_core iTCO_wdt 12048 0 soundcore 8416 1 snd snd_page_alloc 9616 2 snd_hda_intel,snd_pcm i2c_i801 9884 0 i2c_core 25824 2 nvidia,i2c_i801 cfg80211 28944 2 iwl4965,mac80211 pcspkr 3072 0 psmouse 42780 0 serio_raw 6340 0 battery 12680 0 ac 5320 0 thinkpad_acpi 61204 0 button 7584 0 intel_agp 30128 0 led_class 5000 2 iwlcore,thinkpad_acpi nvram 9164 2 thinkpad_acpi evdev 11328 8 reiserfs 241216 3 sha256_generic 9728 0 aes_x86_64 8384 2 aes_generic 28200 1 aes_x86_64 cbc 4160 1 dm_crypt 14472 1 crypto_blkcipher 19396 4 ecb,cbc,dm_crypt usbhid 30496 0 hid 42308 1 usbhid dm_mirror 18752 0 dm_log 10884 1 dm_mirror dm_snapshot 16712 2 dm_mod 58344 23 dm_crypt,dm_mirror,dm_log,dm_snapshot sg 36256 0 sr_mod 17284 0 cdrom 39080 1 sr_mod piix 8648 0 [permanent] ide_pci_generic 5252 0 [permanent] ide_core 137180 2 piix,ide_pci_generic sd_mod 28736 7 ata_piix 20676 0 ahci 30344 6 ata_generic 6276 0 firewire_ohci 23876 0 firewire_core 42272 2 firewire_sbp2,firewire_ohci libata 182048 3 ata_piix,ahci,ata_generic scsi_mod 170040 5 firewire_sbp2,sg,sr_mod,sd_mod,libata crc_itu_t 2496 1 firewire_core ehci_hcd 37836 0 dock 9888 1 libata e1000 131328 0 uhci_hcd 24864 0 thermal 18592 0 processor 37536 4 acpi_cpufreq,thermal fan 5256 0 -- /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 postinst_hook = update-grub postrm_hook = update-grub -- /etc/initramfs-tools/initramfs.conf MODULES=most BUSYBOX=y KEYMAP=n BOOT=local DEVICE=eth0 NFSROOT=auto -- /etc/crypttab sda8_crypt /dev/sda8 none luks -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26.5 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages initramfs-tools depends on: ii cpio 2.9-13 GNU cpio -- a program to manage ar ii findutils 4.4.0-2 utilities for finding files--find, ii klibc-utils 1.5.12-2 small utilities built with klibc f ii module-init-tools 3.4-1 tools for managing Linux kernel mo ii udev 0.125-7 /dev/ and hotplug management daemo Versions of packages initramfs-tools recommends: ii busybox 1:1.10.2-2 Tiny utilities for small and embed initramfs-tools suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---
- To: Christian Jaeger <christian@jaeger.mine.nu>, 503062-done@bugs.debian.org
- Subject: Re: Bug#503062: News?
- From: Yves-Alexis Perez <corsac@debian.org>
- Date: Fri, 31 Oct 2008 07:25:54 +0100
- Message-id: <1225434354.2294.2.camel@hidalgo>
- In-reply-to: <[🔎] 4909B711.6050202@jaeger.mine.nu>
- References: <[🔎] 1225347676.4311.6.camel@hidalgo> <[🔎] 490979BA.3090502@jaeger.mine.nu> <[🔎] 20081030102137.GA30610@corsac.net> <[🔎] 4909B711.6050202@jaeger.mine.nu>
On jeu, 2008-10-30 at 14:30 +0100, Christian Jaeger wrote: > chris@novo:/tmp/chris$ cat initrd.img-2.6.26.7/conf/conf.d/cryptroot > target=sda8_crypt,source=/dev/sda8,key=none,lvm=main-root > > So: the file is also in the newly built /boot/initrd.img-2.6.26.7 now. Ok, that's good news. > So my only explanation is that the problem has been fixed in > initramfs-tools with an upgrade I did after reporting the bug. Actually > I was somewhat more hesitant with upgrading after a few bigger breakages > in lenny, so at that point in time I may have been running a version of > the initramfs-tools that was a few weeks old -- but you should see that > from the bug report, shouldn't you? yep, the report says "Version: > 0.92j". I'm now running: > > chris@novo:~$ dpkgli initramfs-tools > ii initramfs-tools 0.92j tools for generating an initramfs > > Ehr, wait, isn't this the same version? Hmh yeah. > > Oh well, so much for the theory. So what am I gonna to do, try to build > 2.6.26.6 again just for * sake and not use the -v flag to the > update-initramfs script in case it should turn out to be a heisenbug? > > chris@novo:/tmp/chris/linux$ g-reset --hard v2.6.26.6 > HEAD is now at afc84da Linux 2.6.26.6 > chris@novo:/tmp/chris$ cat initrd.img-2.6.26.6/conf/conf.d/cryptroot > target=sda8_crypt,source=/dev/sda8,key=none,lvm=main-root > chris@novo:/tmp/chris$ > > Well now I'm really out of ideas. Well I guess it was a transcient bug. Or maybe a mistake, a wrong manipulation, whatever :/ > > novo:/etc# find -name '*cryptroot*' > novo:/etc# The config and hooks are provided by cryptsetup, and they are in /usr/share: /usr/share/initramfs-tools/conf-hooks.d /usr/share/initramfs-tools/conf-hooks.d/cryptsetup /usr/share/initramfs-tools/hooks /usr/share/initramfs-tools/hooks/cryptopensc /usr/share/initramfs-tools/hooks/cryptpassdev /usr/share/initramfs-tools/hooks/cryptroot /usr/share/initramfs-tools/hooks/cryptopenct > > I don't have the time to find out where it creates the cryptroof file > from and how it could get to fail now. Let's wish us best of luck and > hold our thumbs. Ok, I'm closing it. Thanks for the long description of what you did :) Cheers, -- Yves-AlexisAttachment: signature.asc
Description: This is a digitally signed message part
--- End Message ---