Karmic update "Waiting for encrypted source device..." error
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
My initial post to answers.
Upgraded 64bit Desktop from Jaunty to Karmic Beta using "update-manager -d". The upgrade completed successfully but, on reboot, it is unable to find the encrypted harddrive. This is on a laptop which was initially installed using the Jaunty alternate iso image so that the entire harddisk could be encrypted. At present, it prints a message about not finding the disk and drops me out to a Busybox "(initramfs)" prompt.
Update:
Confirmed on another, older laptop that the same problem exists for upgrades on 32bit systems.
Update:
Hmm, this may be bug #430496. I will dig further tonight and link to the bug if it turns out to be the same.
Update:
OK, this doesn't look like the same bug. I changed "splash" to "nosplash" on the kernel arguments in grub and all I see on boot is:
Boot from (hd0,4) ext2 9df54a9f-
Starting up ...
The cursor sits there blinking under the 'B' and then it appears that some timeout it reached and it writes to the screen without first clearing it leaving me with:
Boot froCheck cryptopts=source= bootarg cat /proc/cmdline5c65
Startingor missing modules. devices: cat /proc/modules ls /dev
-r ALERT! /dev/disk/
Dropping to a shell!
BusyBox v1.13.3 (Ubuntu 1:1.13.3-1ubuntu7)
Enter 'help' for a list of built-in command
(initramfs) _
At this point, I have two unbootable systems (although they boot the Karmic Beta LiveCD just fine). The 64bit system is a Lenovo laptop and the 32bit system is an HP Pavillian laptop. If I recall correctly, the steps I followed when initially installing both of these systems with Jaunty on an encrypted disk using the alternate CD image where the same as those posted at http://
FYI, If possible, I would like to recover data from one of the two systems.
summary: |
- Karmic update results in systems that won't boot + Laptops with encrypted harddisks won't boot after Karmic Update |
summary: |
- Laptops with encrypted harddisks won't boot after Karmic Update + Karmic update "Waiting for encrypted source device..." error |
OK, it looks like I also needed to remove "quiet" from the boot arguments to see what was really going on. On both systems, before it hangs waiting for the timeout, the last messages are:
Begin: Running /scripts/ init-premount ...
Done.
Begin: Mounting root file system... ...
Begin: Running /scripts/local-top ...
Begin: Waiting for encrypted source device... ...