I had the same problem on an Apr 26 update with both of my i386 rawhide
systems, which I also resolved with a rescue disk boot and grub
reinstall. This seems like a pretty scary bug just pre-release, though I
also don't know exactly what to blame.
Initially I thought it was something quirky on one of the systems (which
has two hard drives, which seem to have swapped between sda and sdb with
the upgrade to F9, which I thought might have confused grub), but then
it happened on my other system as well, which has a much more
straightforward configuration.
The yum log from one of the offending updates is below: the only obvious
culprit I see is the kernel upgrade -- is there any way that could mess
up grub? Clearly it touches grub.conf but that seemed fine.
Apr 26 18:06:35 Updated: system-config-network-tui-1.5.7-1.fc9.noarch
Apr 26 18:06:39 Updated: system-config-network-1.5.7-1.fc9.noarch
Apr 26 18:06:47 Updated: imsettings-libs-0.99.6-2.fc9.i386
Apr 26 18:07:18 Updated: metacity-2.22.0-3.fc9.i386
Apr 26 18:07:24 Updated: imsettings-0.99.6-2.fc9.i386
Apr 26 18:07:32 Updated: gvfs-0.2.3-11.fc9.i386
Apr 26 18:07:33 Updated: nash-6.0.52-1.fc9.i386
Apr 26 18:07:34 Updated: mkinitrd-6.0.52-1.fc9.i386
Apr 26 18:07:54 Updated: 1:java-1.6.0-openjdk-1.6.0.0-0.9.b09.fc9.i386
Apr 26 18:08:03 Updated: xulrunner-1.9-0.57.beta5.fc9.i386
Apr 26 18:08:55 Installed: kernel-2.6.25-8.fc9.i686
Apr 26 18:08:57 Updated: im-chooser-0.99.6-2.fc9.i386
Apr 26 18:09:05 Updated: vnc-4.1.2-30.fc9.i386
Apr 26 18:09:09 Updated: firstboot-1.97-1.fc9.i386
Apr 26 18:09:10 Updated: PackageKit-libs-0.1.12-7.20080425.fc9.i386
Apr 26 18:09:13 Updated: PackageKit-0.1.12-7.20080425.fc9.i386
Apr 26 18:09:14 Updated: yum-packagekit-0.1.12-7.20080425.fc9.i386
Apr 26 18:09:38 Installed: kernel-2.6.25-8.fc9.i686
--
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list
