Although I have a single-boot system (on an HP Proliant microserver), I appear to be getting the preupgrade symptoms normally associated with dual-boot systems.
After running preupgrade, when I reboot, all I get is Fedora 15 back again.
/boot/grub/menu.lst does not appear to be the file that grub is using, because preupgrade has updated that file for the upgrade. The first entry is:
title Upgrade to Fedora 16 (Verne)
kernel /upgrade/vmlinuz preupgrade repo=hd::/var/cache/yum/preupgrade ks=hd:UUID=5e5d56d2-b685-4ec1-9744-1f6935045c01:/upgrade/ks.cfg
The system installation is slightly strange, because the system disk is the fifth disk and was originally installed before sda to sdd were installed. I believe I installed the Fedora 15 before installing the other drives with the system disk in that position. (This is because I moved the low-capacity drive that came with the system into the optical drive bay, so that the higher power-consumption 2TB drives could sit in an area with plenty of cooling).
The mtab entry for /boot is:
/dev/sde1 /boot ext4 rw,relatime,user_xattr,barrier=1,data=ordered 0 0
I want to understand precisely what I am doing before proceeding. I prefer to delay the upgrade over risking a non-bootable system.
My first initial question is "How do I find and edit the menu.lst that grub is actually using?".