Upgrade of encrypted Jaunty to Karnic results in non bootable system

Bug #454507 reported by gmud
This bug report is a duplicate of:  Bug #428435: luks encrypted partition not detected. Edit Remove
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
initramfs-tools (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: initramfs-tools

Upgrading a kubuntu jaunty system which has been installed with the alternate installation cd and is fully encrypted with luks (cryptsetup) to karnic beta results in an unbootable system. Upon restart the system waits for some time and then drops to BusyBox with the following error message:

Boot froCheck cryptopts=source= bootarg cat /proc/cmdlinec20f
Startingor missing modules, devices: cat /proc/moduules ls /dev
-r ALERT! /dev/disk/by-uuid/8a3cb1e8-2981-4aab-863f-216bcb8611de does not exist.
 Dropping to a shell!

BusyBox v1.13.3 (Ubuntu 1:1.13.3-1ubuntu7) built-in shell (ash) .....

The dist-upgrade to karnic beta was done via "update-manager -d" (gnome upgrade tool, although it was a kubuntu installation)

Expected results:
Propper uppgrade of grub information and initramfs, so that the system prompts for a password and then boots normally.

Tags: karmic
gmud (gmud)
tags: added: karmic
removed: karnic
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.