[pkg-cryptsetup-devel] Bug#618584: Bug#618584: Encrypted system hangs on boot after giving the password

[Jonas Meurer]

Hello mahashakti89,

On 17/03/2011 mahashakti wrote:
> > > Booting an encrypted system on a self-compiled 2.6.38 kernel fails after
> > > giving the password , I get following error message : cryptpart setup
> > > successfully , cryptsetup : lvm not available , cryptsetup : evms not
> > > available.
> > > 
> > > In fact I don't use lvm or evms. Booting on a stock debian kernel works.
> > > I am not sure if this is acryptsetup bug. Bootinf self compiled
> > > kernels always worked before. Googling around didn't give a decisive
> > > hint.
> > 
> > this sounds to me like a problem with your custom kernel configuration.

> You are certainly right , I will look further. Sorry for the noise

I guess that your custom 2.6.38 kernel misses the drivers to access your
root filesystem (maybe xfs drivers).

> > there is no message "cryptart setup successfully". please send the exact
> > console output.
> 
>  Hi, I am not at home.
> But the message is as follows 
> 
> crypsetup : cryptpart setup successfully 

You mean "cryptpart set up successfully". That message indicates, that
cryptsetup luksOpen was successful.

>  cryptsetup : lvm not available 
>  cryptsetup : evms not available

You can ignore these messages. The cryptroot initramfs script tries to
start lvm and evms in case that the device is not available after
luksOpen.

After waiting some time, you will be dropped into the initramfs
emergency shell. There, you should check the following:

1. was the encrypted root device really unlocked (i.e. does
   /dev/mapper/cryptpart exist).

2. is the UUID of the root fileystem you configured in /etc/fstab
   (f3231831-66c3-4f40-be43-ccde2144fba2) the same as for
   /dev/mapper/cryptpart?

   check this with 'blkid /dev/mapper/cryptpart, or by checking the
   symlink at /dev/disk/by-uuid/f3231831-66c3-4f40-be43-ccde2144fba2.

3. does the unlocked device at /dev/mapper/cryptpart contain your root
   filesystem?

4. are you able to mount the root filesystem at /dev/mapper/cryptpart?

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