Recently I filed a bug report with bugzilla regarding Fedora 18′s inability to boot after successful installation from all types of installation methods. Check the comment section of the Fedora 18 Review post for a direct link to the bug report.
Fedora 18, like many other fresh distros, utilizes GRUB2. However, Fedora 18 is the only distro I have personally encountered this problem of not booting after a successful install. This problem seems to be related to older hardware, or devices that lack the ability / video memory to use the highly graphical GRUB2 boot screen. There is no science in my previous statement, just an educated guess.
Most particularly, I have encountered this problem on HP Proliant G4 device, as well as in Virtual Box on a Windows host.
Symptoms: After successful installation, GRUB2 will briefly flash after post, and then the video output will go black or stop. The system will never continue booting.
Resolution: Boot the system with installation media and instead of selecting “Install,” select “Troubleshooting”. On the following screen, select “Rescue System.”
Continue with the default options, which includes automatically detecting and mounting the system’s root directory to /mnt/sysimage/
After you a dropped to a shell, run chroot /mnt/sysimage to change the root of the system to the freshly installed system. Next, we need to update our GRUB2 config file to disable the graphical mode. That is achieve by peforming the following:
echo “GRUB_TERMINAL=console” >> /etc/default/grub
grub2-mkconfig -o /boot/grub2/grub.cfg
These two commands will reinstall GRUB2 with the new argument GRUB_TERMINAL=console; unlike legacy GRUB, simply editing a text file is not enough, you must run the grub2-mkconfig command as described above.
Now, exit out of the chroot environment with the simple “exit” command, and reboot the system. If everything went correctly, you should now see the GRUB2 menu in solid black and white (how Linux on a server should be). Unfortunately, it’s now time to make yourself a cup of tea, because we have to wait for SELinux to relabel the filesystem. While it doesn’t take forever, it does take about 3 or 4 minutes.
You can skip to the end and leave a response. Pinging is currently not allowed.