[pkg-cryptsetup-devel] Bug#552412: Bug#552412: More info as requested

[Jonas Meurer]

hey steve,

On 27/10/2009 SteveM wrote:
> Thanks for taking the time on this.  I guessed it would be hard to 
> reproduce, since the other 2 kernels show no problems.  A diff of the 
> configs between 6.2.30-1 & 30-2 showed nothing.  Yet, 6.2.30-2 
> consistantly fails to boot while 30-1 works as always.  Both are stock 
> Debian kernels.  I reinstalled 6.2.30-2 but no change.  Not that I 
> expected any.  I figured it couldn't hurt.

are you still able to reproduce the bug? did you try to recreate the
2.6.30-2 initramfs in the meantime: 'update-initramfs -u -k 2.6.30-2'


> Here's my pretty accurate transcript of the boot messages (wrapped)
> ...
> Enter passphrase: <entered>
> [   18.000811] device-mapper: ioctl: unable to remove open device 
> temporary-cryptsetup-658
> device mapper: remove ioctl failed: Device or resource busy
> Key slot 0 unlocked
> File descriptor 3 (conf/conf.d/cryptroot) leaked on lvm invocation.  
> Parent PID 652: /bin/sh
>   Volume group "vulteeVG" not found
> done.
> Begin: waiting for root file system... <long pause> done.
>  Gave up waiting for root device.  Common problems:
>   - Boot args (cat /proc/cmdline)
>     - Check rootdelay= (did the system wait long enough?)
>     - Check root= (did the system wait for the right device?)
>   - Missing modules: (cat /proc/modules; ls /dev)
> Alert!  /dev/mapper/vulteeVG-rootLV does not exist.  Dropping to a shell.
> 
> <busybox info> ... then the "(initramfs): " prompt.
> 
> Really not much info here.  I see the "leaked on invocation" message with 
> the other kernels so I figure it's not significant.
> 
> Let me know if I can supply any other info.

did you give other kernels a try? this seems like an issue with your
initramfs to me. the cryptsetup unlocking seems to work, but the volume
group cannot be found and thus the root filesystem is not available.

please tell me whether you still suffer from this problem, before I put
more effort into debugging it. i believe that it is related to a config
problem on your side.

greetings,
 jonas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 490 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-cryptsetup-devel/attachments/20100304/571bc333/attachment.pgp>