linux-image-2.6.31-7.27-generic fails to boot lvm

[ilf]

Binary package hint: linux-image-2.6.31-7-generic

On my fresh and up-to-date karmic, I got linux-image-2.6.31-7-generic 2.6.31-7.27 with today's apt-get upgrade.

Upon reboot, the kernel fails to boot.
Right after entering the passphrase for my crypto lvm root, it just sits there doing nothing, "quiet" disbled in GRUB2.

When CTRL+ALT+DEL-ing the machine, the message "md: stopping all md devices." is displayed with a correct timestamp in front of it.

Booting linux-image-2.6.31-6-generic works as expected.
There's nothing in syslog about the other boot attempts though.

[Daniel T Chen (crimsun)]

Easily reproducible across all encrypted lvm configurations in current Karmic. 2.6.31-rc7 mainline does _not_ exhibit this symptom.

[Randall Leeds (randall-leeds)]

I have the same behavior.
Using lvm but no encryption.
Changing the description to reflect this.

[Anton¡o Sch¡fano (skiantoz)]

I don't know if it is the same bug, but my netbook (eeepc1000HD), with LUKS swap and home, fails to boot the kernel from package linux-image-2.6.31-7-generic ; it hangs on the following command:

cryptsetup -x aes-cbc-essiv:sha256 -s 256 -h sha256 --key-file=/dev/urandom create cryptoswap /dev/sda8

The last displayed message is:

modprobe: FATAL: Error inserting padlock_sha (...): No such device

This last message is displayed also by the (working) kernel 2.6.31-6-generic.

[Tormod Volden (tormodvolden)]

I do not have root on my LVM so I am not sure if it is the same issue. I am booting from a USB drive, and in the initramfs panic shell, I can not see the drive, not even the /dev/sdg. Is it somehow related to udev being stuck processing the device?

[Tormod Volden (tormodvolden)]

Please ignore my above comment. I have the same issue with the mainline kernel, so I filed 419231 instead.

[Daniel T Chen (crimsun)]

cf. https://lists.ubuntu.com/archives/kernel-team/2009-August/007009.html

[Daniel T Chen (crimsun)]

Built (waiting acceptance in binary NEW)

[neferty (roman-semko)]

since today's updates I am getting this error, again:
modprobe: FATAL: Error inserting padlock_sha (...): No such device

[Luka Renko (lure)]

neferty: this is false alarm and not a bug as such. Kernel tries to load paddlock_sha module, which fails to load as it does not find appropriate HW (some VIA crypto HW module). I agree that it should fail more gracefully (FATAL sounds scary), but this does not cause any problem.

[Tony Narlock (borneo)]

I suppose a good question would be how to fix borked comp.

Answer here for me was to run 'fsck'