failure to install the kernel during upgrade

Thanks for taking the time to report this bug and helping to make Ubuntu better. I believe that the ability to power off the system is intertwined with the kernel and since you are running a kernel not provided by Ubuntu I am not sure how we can help you.

You're right. It's starting to make sense now. The main reason I wanted to keep using my custom kernel was to get round an annoyance to do with P4 clock modulation, but that seems to have been fixed in Feisty. The feisty kernel basically works fine, although it did bring up some other issues which needed sorting out.

Do you want this bug to be about one of those other issues or can I close this?

The device-mapper stuff was a consequence of using the non-standard kernel.

However the failure to install the kernel during upgrade is a separate issue. so yes, I would be grateful if that issue could be dealt with.

I suspect it is something to do with evms or UUIDs or something. My fstab called the boot partition /dev/hda1, but evms wants to call it /dev/evms/boot. I had to change this in fstab after the upgrade because, even though edgy was happy with it being called /dev/hda1, feisty wasn't.

Another odd thing I noticed about the boot partition was that even when I deleted all the files df still thought it was 21% full (in other words, with about 6 or 7Mb in use. Perhaps this is just something to do with evms, but I mention it just in case.

The log files for the upgrade process are kept in '/var/log/dist-upgrade/'. Could you please add them as attachments to your bug report? Thanks again.

The cause of the failure was
=====
Setting up linux-image-2.6.20-15-generic (2.6.20-15.27) ...
Running depmod.
update-initramfs: Generating /boot/initrd.img-2.6.20-15-generic
r, or without a controlling terminal.)
W: mdadm: unchecked configuration file: /etc/mdadm/mdadm.conf
W: mdadm: please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz .
W: mdadm: no arrays defined in configuration file.
W: mdadm: falling back to emergency procedure in initramfs.
Running postinst hook script /sbin/update-grub.
Your /etc/kernel-img.conf needs to be updated. Read grub's NEWS.Debian[1]
file and follow its instructions.
 1. /usr/share/doc/grub/NEWS.Debian.gz
You shouldn't call /sbin/update-grub. Please call /usr/sbin/update-grub instead!
r, or without a controlling terminal.)
Searching for GRUB installation directory ...
No GRUB directory found. To create a template run 'mkdir /boot/grub' first. To install grub, install it manually or try the 'grub-install' command. ### Warning, grub-install is used to change your MBR. ###
User postinst hook script [/sbin/update-grub] exited with value 1
dpkg: error processing linux-image-2.6.20-15-generic (--configure):
 subprocess post-installation script returned error exit status 1
=====
affecting to linux. grub was not properly installed.

Is it still an issue ?

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!