[Bug 32123] Re: initramfs not generated correctly on upgrade to Dapper

[Patricia Hawkins]

I have a system currently in this state, and I've made a backup of the
whole system in this state, preserving original timestamps etc, so let
me know if need anything else s.a. system logs, directory listings, dpkg
logs,  forensic reports on system changes, etc.

Here is my  <a
href="www.connact.com/~phawkins/toast/initrd.img-2.6.15-23-386">initrd.img-2.6.15-23-386</a>

How I got here:
A third-party installation script had upgraded my system to dapper, leaving the system in a mostly-breezy/a few dapper apps state; I decided to upgrade core apps, and upgraded the kernel from 2.6.12-10-386 to 2.6.15-23-386, using the dummy "always points to the latest available kernel" package.  Never futz with the system late at night.

I get the same symptoms as others, including not being able to boot from the 2.6.12-10-386 image; when I boot using the 2.6.15-23-386 recovery from the grub menu, the last few lines I see are:
Begin: Loading essential drivers ...
Capability LSM initialized
Done.
Begin: Running /scripts/init-premount ...
Done.
Begin: Running /scripts/local-top
Done.
Begin: Waiting for root file system ... ...
Done.
ALERT! /dev/hda1 does not exist. Dropping to a shell!

and then the BusyBox banner.

-- 
initramfs not generated correctly on upgrade to Dapper
https://launchpad.net/bugs/32123