Bug#582481: [pkg-cryptsetup-devel] Bug#582481: initramfs-tools: System won't boot anymore if it was encrypted by debian squeeze setup
I've found it. It wasn't an error in the initramfs-tools. The idea came to me when I logged on to a system via RDP. I use a german keyboard and a us layout. The layout changed with the new initramfs-tools and so the keys I entered where wrong. It's definitely no bug. I'm sorry for causing troubles. At the moment I worked with the new initrd image. Thanks Andre Pawlowski --- Vorstellungskraft ist wichtiger als Wissen, denn Wissen ist Begrenzt. -Albert Einstein On 05/25/2010 01:22 PM, Jonas Meurer wrote: > hey andre, > > On 25/05/2010 Andre Pawlowski wrote: >> Today I could copy all the output the error does. > > thanks, let's see ... > >> Here is what the system shows when I boot with the new >> initrd.img-2.6.32-trunk-amd64: >> >> Loading, please wait... >> Volume group "laptop-vg" not found >> Skipping volume group laptop-vg >> Unable to find LVM volume laptop-vg/root >> Unlocking the disk >> /dev/disk/by-uuid/e7bf2609-7a87-447c-9827-694bc164debb (sda2_crypt) >> Enter passphrase: >> udevd-work[422]: kernel-provided name 'dm-0' and NAME= >> 'mapper/temporary-cryptsetup-414' disagree, please use SYMLINK+= or >> change the kernel to provide the proper name >> udevd-work[422]: kernel-provided name 'dm-0' and NAME= >> 'mapper/temporary-cryptsetup-414' disagree, please use SYMLINK+= or >> change the kernel to provide the proper name >> No key available with this passphrase >> cryptsetup: cryptsetup failed, bad password or options? >> Unlocking the disk >> /dev/disk/by-uuid/e7bf2609-7a87-447c-9827-694bc164debb (sda2_crypt) >> Enter passphrase: > > did you try to submit the correct passphrase at all? as already written, > these udevd-work messages are just warnings, they shouldn't have any > impact on the functionality after all. in fact, they appear on my system > as well since last udev upgrade. but unlocking the disk still works. > >> Ok, now the output when I use the initrd.img-2.6.32-trunk-amd64.bak: >> >> Loading, please wait... >> Volume group "laptop-vg" not found >> Skipping volume group hantuch-vg >> Unable to find LVM volume laptop-vg/root >> Unlocking the disk >> /dev/disk/by-uuid/e7bf2609-7a87-447c-9827-694bc164debb (sda2_crypt) >> Enter passphrase: >> Key slot 0 unlocked >> [normal booting output follows] >> >> The system is up to date with the newest squeeze packets. > > so unlocking the disk works with old initramfs, while it fails with the > new initramfs (ignoring the udev warnings)? or does it work with the new > initramfs as well, despite cluttering the passphrase prompt with udev > warnings? > > in the former case you most probably spotted another bug (or > misconfigured your system), in the latter case this bugreport should be > reassigned to package dmsetup, where the respective udev rules need to > be updated. > > greetings, > jonas -- 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/4bfbfeab.4090...@h4des.org
Bug#582481: [pkg-cryptsetup-devel] Bug#582481: initramfs-tools: System won't boot anymore if it was encrypted by debian squeeze setup
Today I could copy all the output the error does. Here is what the system shows when I boot with the new initrd.img-2.6.32-trunk-amd64: Loading, please wait... Volume group "laptop-vg" not found Skipping volume group laptop-vg Unable to find LVM volume laptop-vg/root Unlocking the disk /dev/disk/by-uuid/e7bf2609-7a87-447c-9827-694bc164debb (sda2_crypt) Enter passphrase: udevd-work[422]: kernel-provided name 'dm-0' and NAME= 'mapper/temporary-cryptsetup-414' disagree, please use SYMLINK+= or change the kernel to provide the proper name udevd-work[422]: kernel-provided name 'dm-0' and NAME= 'mapper/temporary-cryptsetup-414' disagree, please use SYMLINK+= or change the kernel to provide the proper name No key available with this passphrase cryptsetup: cryptsetup failed, bad password or options? Unlocking the disk /dev/disk/by-uuid/e7bf2609-7a87-447c-9827-694bc164debb (sda2_crypt) Enter passphrase: Ok, now the output when I use the initrd.img-2.6.32-trunk-amd64.bak: Loading, please wait... Volume group "laptop-vg" not found Skipping volume group hantuch-vg Unable to find LVM volume laptop-vg/root Unlocking the disk /dev/disk/by-uuid/e7bf2609-7a87-447c-9827-694bc164debb (sda2_crypt) Enter passphrase: Key slot 0 unlocked [normal booting output follows] The system is up to date with the newest squeeze packets. Regards Andre Pawlowski --- Warum fallen wir? Damit wir lernen können, uns wieder aufzurappeln. -Batman Begins (Thomas Wayne) On 05/25/2010 08:59 AM, maximilian attems wrote: > tags 582481 moreinfo > stop > > On Tue, May 25, 2010 at 07:46:16AM +0200, Andre Pawlowski wrote: >> Hi, >> >> if it is a bug in udev, why does the system start with the old initramfs? >> > > dude you have not provided the error message or presumed failure > of the new initramfs!? > > how about telling that as a start. > can you still reproduce it with latest initramfs-tools? > > thanks. -- 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/4bfbaff0.40...@h4des.org
Bug#582481: [pkg-cryptsetup-devel] Bug#582481: initramfs-tools: System won't boot anymore if it was encrypted by debian squeeze setup
Hi, if it is a bug in udev, why does the system start with the old initramfs? Greetings, Andre Pawlowski --- Die Schriftsteller können nicht so schnell schreiben, wie die Regierungen Kriege machen, denn das Schreiben verlangt Denkarbeit. -Bertolt Brecht On 05/22/2010 01:13 PM, Jonas Meurer wrote: > hey, > > On 21/05/2010 maximilian attems wrote: >> On Fri, 21 May 2010, Andre Pawlowski wrote: >>> This bugreport was written with the initrd.img-2.6.32-trunk-amd64.bak >>> before updating yesterday >>> to initramfs-tools 0.94.4. I have an encrytped lvm which contains every >>> partition except /boot. >>> It was created by the Debian squeeze setup when I installed the system. >>> Today I tried to boot >>> the system with the new initramfs-tools and after I entered the password I >>> get this message: >>> >>> kernel-provided name 'dm-0' and NAME='/mapper/sda2_crypt' disagree, please >>> use SYMLINK+= >>> or change the kernel to provide the proper name >>> >>> This bug appears after I upgraded >>> >>> libudev0 >>> udev >>> insserv >>> groff-base >>> initramfs-tools >>> libglib2.0-0 >>> libglib2.0-dev >>> libglib2.0-data >>> libgps19 >>> libgudev-1.0-0 >>> libjack0 >>> libschroedinger-1.0-0 >>> libwebkit-1.0-common >>> libwebkit-1.0-2 >>> xserver-xorg-video-intel >>> xterm >>> >>> because I only changed the initrd.img and after that I could boot the >>> system again >>> I think it is a bug in initramfs-tools. >> >> no we dont set udev symlinks, so it is either a crytsetup >> or an udev bug. > > i strongly believe it's a udev bug. the same warnings appear on my > system since last udev upgrade. the apear both at cryptdisks and lvm > initscript invokation. > > didn't have time to further investigate it though. > > greetings, > jonas -- 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/4bfb6428.5050...@h4des.org
Bug#582481: initramfs-tools: System won't boot anymore if it was encrypted by debian squeeze setup
Package: initramfs-tools Version: 0.94.4 Severity: important This bugreport was written with the initrd.img-2.6.32-trunk-amd64.bak before updating yesterday to initramfs-tools 0.94.4. I have an encrytped lvm which contains every partition except /boot. It was created by the Debian squeeze setup when I installed the system. Today I tried to boot the system with the new initramfs-tools and after I entered the password I get this message: kernel-provided name 'dm-0' and NAME='/mapper/sda2_crypt' disagree, please use SYMLINK+= or change the kernel to provide the proper name This bug appears after I upgraded libudev0 udev insserv groff-base initramfs-tools libglib2.0-0 libglib2.0-dev libglib2.0-data libgps19 libgudev-1.0-0 libjack0 libschroedinger-1.0-0 libwebkit-1.0-common libwebkit-1.0-2 xserver-xorg-video-intel xterm because I only changed the initrd.img and after that I could boot the system again I think it is a bug in initramfs-tools. -- Package-specific info: -- /proc/cmdline BOOT_IMAGE=/vmlinuz-2.6.32-trunk-amd64 root=/dev/mapper/handtuch--vg-root ro quiet -- /proc/filesystems ext4 fuseblk -- lsmod Module Size Used by nf_conntrack_ipv4 9817 2 nf_defrag_ipv4 1139 1 nf_conntrack_ipv4 xt_state1303 2 nf_conntrack 46359 2 nf_conntrack_ipv4,xt_state xt_tcpudp 2319 2 iptable_filter 2258 1 ip_tables 13899 1 iptable_filter x_tables 12813 3 xt_state,xt_tcpudp,ip_tables vboxnetadp 4225 0 vboxnetflt 9978 0 vboxdrv 1710854 2 vboxnetadp,vboxnetflt fuse 50078 1 loop 11767 0 firewire_sbp2 11450 0 snd_hda_codec_conexant21789 1 joydev 8411 0 snd_hda_intel 18147 0 arc41274 2 ecb 1841 2 snd_hda_codec 54212 2 snd_hda_codec_conexant,snd_hda_intel snd_hwdep 5364 1 snd_hda_codec snd_pcm_oss32399 0 snd_mixer_oss 12606 1 snd_pcm_oss iwlagn 71452 0 iwlcore77494 1 iwlagn snd_pcm60615 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss snd_seq_midi4208 0 snd_rawmidi15291 1 snd_seq_midi snd_seq_midi_event 4628 1 snd_seq_midi snd_seq42769 2 snd_seq_midi,snd_seq_midi_event mac80211 135407 2 iwlagn,iwlcore snd_timer 15502 2 snd_pcm,snd_seq pcmcia 19426 0 uvcvideo 51663 0 cfg80211 101253 3 iwlagn,iwlcore,mac80211 videodev 29977 1 uvcvideo thinkpad_acpi 50043 0 yenta_socket 19051 1 v4l1_compat11442 2 uvcvideo,videodev rsrc_nonstatic 7294 1 yenta_socket snd_seq_device 4477 3 snd_seq_midi,snd_rawmidi,snd_seq v4l2_compat_ioctl32 8538 1 videodev i2c_i8017766 0 rfkill 12996 2 cfg80211,thinkpad_acpi pcspkr 1699 0 pcmcia_core24054 3 pcmcia,yenta_socket,rsrc_nonstatic snd44718 11 snd_hda_codec_conexant,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device battery 4998 0 ac 2192 0 wmi 4307 0 psmouse49521 0 soundcore 4598 1 snd nvram 5061 1 thinkpad_acpi snd_page_alloc 6217 2 snd_hda_intel,snd_pcm evdev 7336 24 serio_raw 3752 0 processor 29479 2 ext4 285067 4 mbcache 4970 1 ext4 jbd2 66855 1 ext4 crc16 1319 1 ext4 sha256_generic 8692 2 cryptd 5366 0 aes_x86_64 7340 2 aes_generic25714 1 aes_x86_64 cbc 2539 1 dm_crypt 10507 1 dm_mod 53658 15 dm_crypt fan 3346 0 sg 18728 0 sr_mod 12602 0 sd_mod 29673 3 crc_t10dif 1276 1 sd_mod cdrom 29399 1 sr_mod uhci_hcd 18457 0 firewire_ohci 19452 0 ahci 31494 2 sdhci_pci 5565 0 sdhci 13966 1 sdhci_pci i915 247359 2 drm_kms_helper 18883 1 i915 libata131655 1 ahci ricoh_mmc 3069 0 mmc_core 45456 1 sdhci led_class 2401 3 iwlcore,thinkpad_acpi,sdhci firewire_core 36560 2 firewire_sbp2,firewire_ohci crc_itu_t 1307 1 firewire_core ehci_hcd 30578 0 thermal11674 0 drm 137190 3 i915,drm_kms_helper i2c_algo_bit4225 1 i915 i2c_core
