Product SiteDocumentation Site

Chapter 9. Troubleshooting Installation on an Intel or AMD System

9.1. You are unable to boot Fedora
9.1.1. Are You Unable to Boot With Your RAID Card?
9.1.2. Is Your System Displaying Signal 11 Errors?
9.2. Trouble Beginning the Installation
9.2.1. Problems with Booting into the Graphical Installation
9.3. Trouble During the Installation
9.3.1. No devices found to install Fedora Error Message
9.3.2. Saving traceback messages
9.3.3. Trouble with Partition Tables
9.3.4. Using Remaining Space
9.3.5. Other Partitioning Problems
9.3.6. Are You Seeing Python Errors?
9.4. Problems After Installation
9.4.1. Trouble With the Graphical GRUB Screen on an x86-based System?
9.4.2. Booting into a Graphical Environment
9.4.3. Problems with the X Window System (GUI)
9.4.4. Problems with the X Server Crashing and Non-Root Users
9.4.5. Problems When You Try to Log In
9.4.6. Is Your RAM Not Being Recognized?
9.4.7. Your Printer Does Not Work
9.4.8. Apache-based httpd service/Sendmail Hangs During Startup
This section discusses some common installation problems and their solutions.
For debugging purposes, anaconda logs installation actions into files in the /tmp directory. These files include:
/tmp/anaconda.log
general anaconda messages
/tmp/program.log
all external programs run by anaconda
/tmp/storage.log
extensive storage module information
/tmp/yum.log
yum package installation messages
/tmp/syslog
hardware-related system messages
If the installation fails, the messages from these files are consolidated into /tmp/anacdump.txt.
All of the files above reside in the installer's ramdisk and are thus volatile. To make a permanent copy, copy those files to another system on the network using scp on the installation image (not the other way round).

9.1. You are unable to boot Fedora

9.1.1. Are You Unable to Boot With Your RAID Card?

If you have performed an installation and cannot boot your system properly, you may need to reinstall and create your partitions differently.
Some BIOSes do not support booting from RAID cards. At the end of an installation, a text-based screen showing the boot loader prompt (for example, GRUB: ) and a flashing cursor may be all that appears. If this is the case, you must repartition your system.
Whether you choose automatic or manual partitioning, you must install your /boot partition outside of the RAID array, such as on a separate hard drive. An internal hard drive is necessary to use for partition creation with problematic RAID cards.
You must also install your preferred boot loader (GRUB or LILO) on the MBR of a drive that is outside of the RAID array. This should be the same drive that hosts the /boot/ partition.
Once these changes have been made, you should be able to finish your installation and boot the system properly.

9.1.2. Is Your System Displaying Signal 11 Errors?

A signal 11 error, commonly know as a segmentation fault, means that the program accessed a memory location that was not assigned to it. A signal 11 error may be due to a bug in one of the software programs that is installed, or faulty hardware.
If you receive a fatal signal 11 error during your installation, it is probably due to a hardware error in memory on your system's bus. Like other operating systems, Fedora places its own demands on your system's hardware. Some of this hardware may not be able to meet those demands, even if they work properly under another OS.
Ensure that you have the latest installation updates and images. Review the online errata to see if newer versions are available. If the latest images still fail, it may be due to a problem with your hardware. Commonly, these errors are in your memory or CPU-cache. A possible solution for this error is turning off the CPU-cache in the BIOS, if your system supports this. You could also try to swap your memory around in the motherboard slots to check if the problem is either slot or memory related.
Another option is to perform a media check on your installation DVD. Anaconda, the installation program, has the ability to test the integrity of the installation media. It works with the DVD, hard drive ISO, and NFS ISO installation methods. Red Hat recommends that you test all installation media before starting the installation process, and before reporting any installation-related bugs (many of the bugs reported are actually due to improperly-burned DVDs). To use this test, type the following command at the boot: or yaboot: prompt:
	linux mediacheck
For more information concerning signal 11 errors, refer to:
	http://www.bitwizard.nl/sig11/