Comment 10 for bug 609280

This is not a duplicate of bug #496435 as this was a fresh install, not an upgrade. The cause of this bug is likely that the installer installed grub to a drive other than the one which is first in the boot order. This situation is very difficult to prevent as the boot drive can't be determined from within linux. One possible solution would be installing to all hard drives by default, but that is likely unacceptable in many circumstances.

To clarify, the reason that I believe grub failed to load is that the machine was actually booting from a hard drive with an old install of grub2 in its mbr+embedded area. When this old install tried to use the newer, incompatible, modules from /boot/grub it failed. There was a drive with a recent and working grub install, it just wasn't the drive being booted from.