initramfs not generated correctly on dist-upgrade
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
initramfs-tools (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Bug Description
After upgrading to dapper drake (through a dist-upgrade) and rebooting, my system did not start up.
I got the following message:
Decompressing Linux...Done
Booting the Kernel.
ALERT! /dev/hda1 does not exist. Dropping to a shell.
After this I was presented with the standard busybox shell and after checking the /dev directory of the initial ramfs root I noticed that there was indeed no /dev/hda1 or any /dev/hda for that matter.
As a bit of personal speculation, I think that it might be a problem with the associated initrd not having the ide drivers accessable or maybe something about its device nodes. I notice that the latest package of the amd64 kernel at this time (2.6.15-15) does not have inbuilt ATA drivers like breezys did and I think there might be a problem getting them loaded up properly.
I built my own kernel and initrd image with ATA/ATAPI/MFM/RLL (IDE), Enhanced IDE/MFM/RLL disk/cdrom/
description: | updated |
Changed in initramfs-tools: | |
status: | Incomplete → Confirmed |
Changed in initramfs-tools: | |
assignee: | adconrad → nobody |
Ok, I completely uninstalled my kernel image then reinstalled it and it worked. This makes me think that there was something wrong with the upgrade dependancy order that caused it to do its initrd stuff before the environment was properly set up. Thus it shouldn't affect new installations but may provide a confusing and discoraging barrier to people upgrading to test dapper.