Product SiteDocumentation Site

Chapter 7. Troubleshooting

7.1. Getting Help
7.1.1. Log Files Generated During the Installation
7.1.2. Transferring Log Files from the Installation System
7.2. Trouble Beginning the Installation
7.2.1. Problems with Booting into the Graphical Installation
7.2.2. Serial Console Not Detected
7.3. Trouble During the Installation
7.3.1. No Disks Detected
7.4. Problems After Installation
7.4.1. Resetting the Root Password
7.4.2. Are You Unable to Boot With Your RAID Card?
7.4.3. Trouble With the Graphical Boot Sequence
7.4.4. Booting into a Graphical Environment
7.4.5. No Graphical User Interface Present
7.4.6. X Server Crashing After User Logs In
7.4.7. Is Your RAM Not Being Recognized?
This chapter offers some pointers on how to get help when something goes wrong. It also discusses some common installation problems and their solutions.

7.1. Getting Help

There are many places on the internet which can help you when you encounter a problem not described in this chapter: discussion boards, blogs, IRC, and more. Some of the more popular places where you can find help include:
  • Ask Fedora - Fedora's knowledge base, available in multiple languages
  • The #fedora IRC channel on FreeNode - one of the main IRC channels used by Fedora users, English only
  • Fedora Project Wiki - the official wiki for Fedora Project
  • Stack Exchange - an English language Q&A board, not specific to Fedora

Note

The above list is by no means complete - you can find help in many other places as well. Additional information about available resources such as IRC channels and mailing lists is available at https://fedoraproject.org/wiki/Communicating_and_getting_help.
Before you open a new discussion or ask anyone for help on IRC, you should always do some research on your own. If you are encountering an issue, there is usually a good chance that someone else ran into the same problem before you and published a solution somewhere. Opening a discussion about something already explained elsewhere, or asking a common question which has been answered many times before, is not likely to result in a friendly, constructive response.
When you ask for help troubleshooting problems related to the installation, you may be asked to provide log files generated by the installer. The sections below explain which files are generated, what their contents are, and how to transfer them from the installation system.

7.1.1. Log Files Generated During the Installation

For debugging purposes, Anaconda logs installation actions into files in the /tmp directory. These files are listed in the following table.
Table 7.1. Log Files and Their Contents
Log file Contents
/tmp/anaconda.log general Anaconda messages
/tmp/program.log all external programs run during the installation
/tmp/storage.log extensive storage module information
/tmp/packaging.log dnf and rpm package installation messages
/tmp/syslog hardware-related system messages

If the installation fails, the messages from these files are consolidated into /tmp/anaconda-tb-identifier, where identifier is a random string.

7.1.2. Transferring Log Files from the Installation System

All of the files described in Section 7.1.1, “Log Files Generated During the Installation” reside in the installation program's RAM disk, which means they are not saved permamently and will be lost once the system is powered down. To store them permanently, copy those files to another system on the network using scp on the system running the installation program, or copy them to a mounted storage device (such as an USB flash drive). Details on how to transfer the log files are below. Note that if you use an USB flash drive or other removable media, you should make sure to back up any data on it before starting the procedure.

7.1.2.1. Transferring Log Files Onto a USB Drive

  1. On the system you are installing, press Ctrl+Alt+F2 to access a shell prompt. You will be logged into a root account and you will have access to the installation program's temporary file system.
  2. Connect a USB flash drive to the system and execute the dmesg command. A log detailing all recent events will be displayed. At the bottom of this log, you will see a set of messages caused by the USB flash drive you just connected. It will look like a set of lines similar to the following:
    [ 170.171135] sd 5:0:0:0: [sdb] Attached SCSI removable disk
    Note the name of the connected device - in the above example, it is sdb.
  3. Go to the /mnt directory and once there, create new directory which will serve as the mount target for the USB drive. The name of the directory does not matter; this example uses the name usb.
    # mkdir usb
  4. Mount the USB flash drive onto the newly created directory. Note that in most cases, you do not want to mount the whole drive, but a partition on it. Therefore, do not use the name sdb - use the name of the partition you want to write the log files to. In this example, the name sdb1 is used.
    # mount /dev/sdb1 /mnt/usb
    You can now verify that you mounted the correct device and partition by accessing it and listing its contents - the list should match what you expect to be on the drive.
    # cd /mnt/usb
    # ls
  5. Copy the log files to the mounted device.
    # cp /tmp/*log /mnt/usb
  6. Unmount the USB flash drive. If you get an error message saying that the target is busy, change your working directory to outside the mount (for example, /).
    # umount /mnt/usb
The log files from the installation are now saved on the USB flash drive.

7.1.2.2. Transferring Log Files Over the Network

  1. On the system you are installing, press Ctrl+Alt+F2 to access a shell prompt. You will be logged into a root account and you will have access to the installation program's temporary file system.
  2. Switch to the /tmp directory where the log files are located:
    # cd /tmp
  3. Copy the log files onto another system on the network using the scp command:
    # scp *log user@address:path
    Replace user with a valid user name on the target system, address with the target system's address or host name, and path with the path to the directory you wish to save the log files into. For example, if you want to log in as john to a system with an IP address of 192.168.0.122 and place the log files into the /home/john/logs/ directory on that system, the command will have the following form:
    # scp *log john@192.168.0.122:/home/john/logs/
    When connecting to the target system for the first time, you may encounter a message similar to the following:
    The authenticity of host '192.168.0.122 (192.168.0.122)' can't be established.
    ECDSA key fingerprint is a4:60:76:eb:b2:d0:aa:23:af:3d:59:5c:de:bb:c4:42.
    Are you sure you want to continue connecting (yes/no)?
    
    Type yes and press Enter to continue. Then, provide a valid password when prompted. The files will start transferring to the specified directory on the target system.
The log files from the installation are now permanently saved on the target system and available for review.