For what it's worth here's my grub.conf:
$ sudo more grub.conf
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/mapper/vg_server0-lv_root
# initrd /initrd-[generic-]version.img
#boot=/dev/sda
default=1
timeout=0
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Upgrade to Fedora 14 (Laughlin)
kernel /upgrade/vmlinuz preupgrade repo=hd::/var/cache/yum/preupgrade
ks=hd:UUID=706664cb-53af-4399-9f80-6554424247e9:/upgra
de/ks.cfg
stage2=http://mirrors.kernel.org/fedora/releases/14/Fedora/x86_64/os/images/install.img
initrd /upgrade/initrd.img
title Fedora (2.6.32.26-175.fc12.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.32.26-175.fc12.x86_64 ro
root=/dev/mapper/vg_server0-lv_root LANG=en_US.UTF-8
SYSFONT=latarcyrheb-sun16
KEYBOARDTYPE=pc KEYTABLE=us rhgb quiet
initrd /initramfs-2.6.32.26-175.fc12.x86_64.img
title Fedora (2.6.31.5-127.fc12.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.31.5-127.fc12.x86_64 ro
root=/dev/mapper/vg_server0-lv_root LANG=en_US.UTF-8
SYSFONT=latarcyrheb-sun16
KEYBOARDTYPE=pc KEYTABLE=us rhgb quiet
initrd /initramfs-2.6.31.5-127.fc12.x86_64.img
Now that I'm looking at it I realize I NEVER see this menu. I would not be
surprised if Amahi disabled this. Do I need to uncomment that "boot=..."
line?
-----Original Message-----
From: Bryan J Smith
Sent: Saturday, June 11, 2011 11:45 AM
To: Joe ; calug at unknownlamer.org
Subject: Re: [CALUG] Fedora upgrade unsuccessful
I just realized something. Your message about the file system not being
unmounted cleanly has nothing to do with Preupgrade. It has to do with the
init
process in Fedora 12 itself. Did your add-ons to Fedora 12 modify its init,
and
aren't unmounting the file system cleanly?
BTW, there is a directory specific to Preupgrade under /var, separate from
yum's
cache. And verify the files in /boot/grub/grub.conf for the Preupgrade
installer are actually all removed from /boot. You may have a corrupt
kernel
image that is in the normal /boot area. I'm not entirely sure you're
getting
everything, and would like to inspect the system.
I've been meaning to file an enhancement with Fedora to add a button to
"clean
up" all preupgrade components. This might be a good reason, as it's not
straight-forward to find everything.
----- Original Message ----
From: Joe <joe_tseng at hotmail.com>
To: calug at unknownlamer.org
Sent: Sat, June 11, 2011 10:23:44 AM
Subject: Re: [CALUG] Fedora upgrade unsuccessful
I removed the /boot/upgrade and /var/cache/yum/* directories and still no
dice. In fact I've not seen any difference in how the computer behaves.
After preupgrade is done with doing its thing and the computer reboots, I
still see that "unmounted cleanly" message box.
-----Original Message-----
From: Bryan J Smith
Sent: Saturday, June 11, 2011 8:56 AM
To: Joe ; calug at unknownlamer.org
Subject: Re: [CALUG] Fedora upgrade unsuccessful
Pre-upgrade does more exhaustive checking in never Fedora versions, I've
noted
that. Earlier versions did checking for speed, and would sometimes miss
incomplete boot files or packages, and that would be an issue if you have a
file
system fill up (it wouldn't fix the partial downloads).
That's why I mentioned that it might be best to blow away all of the
Preupgrade
/boot and /var files and start over. A file system (like /boot or /var
areas)
filling up is the #1 reason why I see Preupgrade fail. Again, newer Fedora
versions have gotten much better in dealing with all of the exceptions that
people run into, as people have reported such conditionals that need to be
accounted for.
As far as "flipping back," of course, once Preupgrade is done, the default
kernel boot is going to be Anaconda, not your prior distro. Just remove the
/boot and grub entry, along with the /var areas for Preupgrade and re-try.
Also
open up a Bugzilla and let them know what you ran into. Preupgrade is
actively
tracked for conditionals that have not been accounted for yet, or for
verifying
it's an issue that is already addressed in newer Fedora versions.
Remember, Fedora 12 went end-of-life (EoL) last year, so it hasn't received
more
recent Preupgrade logic.
-- Bryan
P.S. Remember, Preupgrade and DVD are the exact same program, Anaconda (a
series of Python modules, including YUM). The difference is that Preupgrade
pre-resolves dependencies and pre-downloads all packages specific for your
configured YUM repos to your hard drive, ensuring everything is there that
is
needed. As a side bonus, it runs from the hard drive, so it is faster. If
you
use the DVD, you're stuck with what's on the DVD by default, although
Anaconda
will offer to update from the Internet as well for the system's repos. In
every
case of a Preupgrade issue (almost always disk space issues), blowing away
the
/boot and /var files and re-starting always works.
----- Original Message ----
From: Joe <joe_tseng at hotmail.com>
Sent: Fri, June 10, 2011 8:14:41 PM
I'm not having any issues with preupgrade at all. It's when the computer
reboots after it run preupgrade. I get a small msg window with the msg I
got initially:
“The following file systems for your system were not unmounted cleanly.
Please boot your installation, let the file systems be checked and shut
down cleanly to upgrade. (/dev/sda1)”
After I click the OK button in that msg window the computer just sits; it
doesn't reboot. I have to flip the switch for it to boot back into F12.
_______________________________________________
CALUG mailing list
CALUG at unknownlamer.org
http://lists.unknownlamer.org/listinfo/calug