[Pkg-cryptsetup-devel] Bug#478268: Bug#478268: cryptsetup: LUKS device no more recognized at boot
jonas at freesources.org
Wed May 14 08:58:36 UTC 2008
severity 478268 important
On 28/04/2008 Luca Capello wrote:
> The only partion not encrypted on my system is /dev/sda1, i.e. /boot.
> Thus, /dev/sda2 is the LVM PV which contains /, /home, swap and four
> others /mnt LVs.
I just tried to reproduce your bug, but so far I failed. I installed
debian/testing with encrypted /dev/hda2 as LVM PV containing / and
/home, and I used cryptsetup 1.0.6-1. At first boot after successfull
install the system correctly starts the cryptroot partition.
As you're the only one reporting this bug, I do believe that either your
setup is broken or you discovered a cornercase.
I'm thus downgrading severity to important.
> > do you get a busybox rescue prompt after the cryptsetup failure?
> No busybox rescue prompt, after having failed for three times cryptsetup
> again starts asking me for the passhprase and after three more failures
> the system "blocks" (but I still see what I type) on:
> And the machine restart :-(
> Booting with the "break" kernel option (as suggested at bug #466573 )
> causes the machine to reboot before prompting for the cryptsetup
> password, at least with kernel 2.6.25-trunk-amd64.
That's indeed strange. I'm not initramfs expert, but I thought that
something like break=init or break=bottom should give you a rescue
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-cryptsetup-devel/attachments/20080514/c2513e1d/attachment.pgp
More information about the Pkg-cryptsetup-devel