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 /tm p 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 /hom e/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
7.1. Trouble Beginning the Installation
7.1.1. Problems with Booting into the Graphical Installation
Systems with some video cards have trouble booting into the graphical installation program. If the
installation program does not run using its default settings, it attempts to run in a lower resolution mode. If that still fails, the installation program attempts to run in text mode.
There are several possible solutions to display issues, most of which involve specifying custom boot options. For more information, see Section 20.1, “Configuring the Installation System at the Boot Menu”.
Use the basic graphics mode
You can attempt to perform the installation using the basic graphics driver. To do this, either select Troubleshooting > Install Red Hat Enterprise Linux 7.0 in basic graphics mode in the boot menu, or edit the installation program's boot options and append inst.xdriver=vesa at the end of the command line.
Specify the display resolution manually
If the installation program fails to detect your screen resolution, you can override the automatic detection and specify it manually. To do this, append the inst.resolution=x option at the boot menu, where x is your display's resolution (for example, 1024 x768).
Use an alternate video driver
You can also attempt to specify a custom video driver, overriding the installation program's automatic detection. To specify a driver, use the inst.xdriver=x option, where x is the device driver you want to use (for example, nouveau).
Note
If specifying a custom video driver solves your problem, you should report it as a bug at https://bugzilla.redhat.com under the anaconda component. Anaconda should be able to detect your hardware automatically and use the appropriate driver without your
intervention.
Perform the installation using VNC
If the above options fail, you can use a separate system to access the graphical installation over the network, using the Virtual Network Computing (VNC) protocol. For details on installing using VNC, see Chapter 22, Installing Using VNC.
7.1.2. Serial Console Not Detected
In some cases, attempting to install in text mode using a serial console will result in no output on the console. This happens on systems which have a graphics card, but no monitor connected. If Anaconda detects a graphics card, it will attempt to use it for a display, even if no display is connected.
If you want to perform a text-based installation on a serial console, use the inst.text and console=
boot options. See Chapter 20, Boot Options for more details.
7.2. Trouble During the Installation
7.2.1. No Disks Detected
When the installation starts, you might receive the following error message:
No disks detected. Please shut down the computer, connect at least one disk, and restart to complete installation
The message indicates that Anaconda did not find any storage devices to install on. In that case, first make sure that your system does have at least one storage device attached.
If your system uses a hardware RAID controller, verify that the controller is properly configured and working. See your controller's documentation for instructions.
If you are installing into one or more iSCSI devices and there is no local storage present on the system, make sure that all required LUNs (Logical Unit Numbers) are being presented to the appropriate HBA (Host Bus Adapter). For additional information about iSCSI, see Appendix B, iSCSI Disks.
If you made sure you have a connected and properly configured storage device and the message still appears after you reboot the system and start the installation again, it means that the installer failed to detect the storage. In most cases this message appears when you attempt to install on an SCSI device which has not been recognized by the installation program.
In that case, you will have to perform a driver update before starting the installation. Check your hardware vendor's website to determine if a driver update is available that fixes your problem. For more general information on driver updates, see Chapter 4, Updating Drivers During Installation on AMD64 and Intel 64 Systems.
You can also consult the Red Hat Hardware Compatibility List, available online at https://hardware.redhat.com.
7.2.2. Reporting Traceback Messages
If the graphical installation program encounters an error, it presents you with a crash reporting dialog box.
You can then choose to send information about the problem you encountered to Red Hat. To send a crash report, you will need to enter your Customer Portal credentials. If you do not have a Customer Portal account, you can register at https://www.redhat.com/wapps/ugc/register.html. Automated crash reporting also requires a working network connection.
Figure 7.1. The Crash Reporting Dialog Box
When the dialog appears, select Report Bug to report the problem, or Quit to exit the installation.
Optionally, click More Info to display detailed output that may help determine the cause of the error. If you are familiar with debugging, click Debug. This will take you to virtual terminal tty1, where you can request more precise information that will enhance the bug report. To return to the graphical interface from tty1, use the continue command.
Figure 7.2. The Expanded Crash Reporting Dialog Box
If you want to report the bug to the customer portal, follow the procedure below.