With a freshly-installed F9 system, if you use SNAKE to tell it to install something else (e.g. Fedora 8), at reboot you'll either get: GRUB [hang] or GRUB GRUB GRUB GRUB [infinite loop] Perhaps it's invoking grub incorrectly somehow?
Interestingly I've seen similar complaints from people using Hibernate for the first time after boot. Maybe there's a deeper problem with GRUB?
Greetings Will. Can you note the version of snake used, the architecture you're seeing this on, and any cmdline arguments used? Any chance you have the {grub,yaboot,elilo}.conf before rebooting? Thanks! James
I'm using the F9 default snake - snake-0:0.11-0.5.fc9. grub.conf exists (and looks normal) before reboot. Workaround is to boot media into rescue mode and run: chroot /mnt/sysimage grub-install /dev/sda Which doesn't change grub.conf. So it's kind of perplexing.
Not able to reproduce on F-9 i386, x86_64 or ppc so far. Anything funky about the environment (e.g. kvm, qemu, bare metal, vmware)? Is there a non-default partitioning setup involved (e.g. grub on a partition instead of MBR)? Would you mind attaching the grub.conf and maybe /var/log/anaconda.log from the previous install? Thanks!
Bare metal machine. The only thing of note about the partitioning is that there's no /boot partition - we've got / and swap and that's it. Happens on i386 and x86_64.
Rats, no luck reproducing using the environment specified in comment#5. Any chance I can get access to the system you're seeing this on?
Not snake-specific, AFAICT. *** This bug has been marked as a duplicate of 446362 ***