On 2009/05/30 20:04 (GMT-0500) Allen Kistler composed: > On a multi-disk system, start with at least the first disk (sda) > uninitialized and at least one of the others initialized (e.g., sdb, > partitioned or not). Install with any partitioning you desire. When > you get to the "install boot loader" screen, anaconda wants to install > grub on the first previously initialized disk (sdb in this example), not > on the actual first disk (sda). > There are two workarounds. > 1. Click "Change Device" and tell anaconda to recognize a different > (i.e., the correct) BIOS order > 2. After installation, boot into the DVD rescue mode to reinstall grub > and (very important!) to edit grub.conf for the correct hd numbers > Big deal or not? My take is it's a bug worth fixing at some point. For > F11 GA, it's probably enough to include it in the Release Notes as a > known issue (but still fix it for real later). > I've filed https://bugzilla.redhat.com/show_bug.cgi?id=503299 but I thought I'd point it out for consideration > in the Release Notes if somebody thinks it's worth it. Since I never ever install Grub on any MBR, I might not be able to reproduce. What happens if you leave generic code on the MBR and try to have Anaconda put Grub on /boot or /, particularly by using partition labels? These would amount to additional, and possibly easier, workarounds. -- "A fool gives full vent to his anger, but a wise man keeps himself under control." Proverbs 29:11 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
