Kernel updates broken for LUKs cryptoroot: Failed to find suitable ramdisk generation tool for kernel version

[Greg]

Quick summary: Updating the kernel with apt-get fails with the message "Failed to find suitable ramdisk generation tool for kernel version". Running edgy with LUKs cryptoroot.

I have been using a LUKs cryptoroot with edgy for a couple of months. I installed the cryptoroot using these instructions: https://help.ubuntu.com/community/EncryptedFilesystem.

All was well until a kernel upgrade appeared in apt-get update. The output is as follows:

The following packages will be upgraded:
   linux-headers-2.6.17-11 (2.6.17.1-11.35 => 2.6.17.1-11.37)
   linux-headers-2.6.17-11-generic (2.6.17.1-11.35 => 2.6.17.1-11.37)
   linux-image-2.6.17-11-generic (2.6.17.1-11.35 => 2.6.17.1-11.37)
3 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 31.3MB of archives.
After unpacking 0B of additional disk space will be used.
Preconfiguring packages ...
(Reading database ... 93295 files and directories currently installed.)
Preparing to replace linux-headers-2.6.17-11 2.6.17.1-11.35 (using .../linux-headers-2.6.17-11_2.6.17.1-11.37_i386.deb) ...
Unpacking replacement linux-headers-2.6.17-11 ...
Preparing to replace linux-headers-2.6.17-11-generic 2.6.17.1-11.35 (using .../linux-headers-2.6.17-11-generic_2.6.17.1-11.37_i386.deb) ...
Unpacking replacement linux-headers-2.6.17-11-generic ...
Preparing to replace linux-image-2.6.17-11-generic 2.6.17.1-11.35 (using .../linux-image-2.6.17-11-generic_2.6.17.1-11.37_i386.deb) ...
Could not find /usr/sbin/mkinitramfs. at /var/lib/dpkg/tmp.ci/preinst line 239, <STDIN> line 9.
The directory /lib/modules/2.6.17-11-generic still exists. Continuing as directed.
Done.
Unpacking replacement linux-image-2.6.17-11-generic ...
Running postrm hook /sbin/update-grub .
Searching for GRUB installation directory ... found: /boot/grub
Testing for an existing GRUB menu.list file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found kernel: /vmlinuz-2.6.17-11-generic
Found kernel: /vmlinuz-2.6.17-10-generic
Found kernel: /memtest86+.bin
Updating /boot/grub/menu.lst ... done

Setting up linux-headers-2.6.17-11 (2.6.17.1-11.37) ...

Setting up linux-headers-2.6.17-11-generic (2.6.17.1-11.37) ...
Setting up linux-image-2.6.17-11-generic (2.6.17.1-11.37) ...
Running depmod.
Finding valid ramdisk creators.
Failed to find suitable ramdisk generation tool for kernel version
2.6.17-11-generic on running kernel 2.6.17-11-generic in /usr/sbin/mkinitramfs
dpkg: error processing linux-image-2.6.17-11-generic (--configure):
 subprocess post-installation script returned error exit status 9
Errors were encountered while processing:
 linux-image-2.6.17-11-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)

There has been talk of this in the forums:
- http://ubuntuforums.org/showthread.php?p=2449964
- http://ubuntuforums.org/archive/index.php/t-367421.html
- http://ubuntuforums.org/showthread.php?t=286311

but the advice to remove the mkinitramfs line from /etc/kernel-img.conf will break LUKs. I know because I tried this after the pervious edgy kernel update arrived and got an unusable initrd and had to re-install from scratch :( I have initramfs-tools installed, so /usr/sbin/mkinitramfs _does_ exist.

I'm hoping the upgrade process hasn't broken my original initrd and I will still be able to reboot OK....

More system info follows:

uname -a
Linux laptopwired 2.6.17-11-generic #2 SMP Thu Feb 1 19:52:28 UTC 2007 i686 GNU/Linux

cat /etc/kernel-img.conf
do_symlinks = yes
relative_links = yes
do_bootloader = no
do_bootfloppy = no
do_initrd = yes
link_in_boot = no
postinst_hook = /sbin/update-grub
postrm_hook = /sbin/update-grub
ramdisk = /usr/sbin/mkinitramfs

cat /etc/initramfs-tools/modules
# List of modules that you want to include in your initramfs.
#
# Syntax: module_name [args ...]
#
# You must run update-initramfs(8) to effect this change.
#
# Examples:
#
# raid1
# sd_mod
dm_mod
dm_crypt
sha256
aes_i586

[xteejx (xteejx-deactivatedaccount)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release (Jaunty)? Thanks in advance.

[Greg (g6)]

Wow, blast from the past! I've been happily using the LUKS setup from the alternate CD for the past few distros with no problems. I couldn't see how to close this bug, but feel free to.

[xteejx (xteejx-deactivatedaccount)]

Very sorry about the delay, it isn't often that bugs are completely missed! I am closing this bug report due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status . Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.