[pkg-cryptsetup-devel] Bug#582481: initramfs-tools: System won't boot anymore if it was encrypted by debian squeeze setup
Andre Pawlowski
sqall at h4des.org
Tue May 25 05:46:16 UTC 2010
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
More information about the pkg-cryptsetup-devel
mailing list