Debug boot options

You can use several options when debugging issues to troubleshoot and fix issues.

inst.rescue
Use the inst.rescue option to run the rescue environment for diagnosing and fixing systems.
inst.updates=

Use the inst.updates= option to specify the location of the updates.img file that you want to apply during installation. The updates.img file can be derived from one of several sources.

Table 1. updates.img file sources
Source Description Example

Updates from a network

Specify the network location of updates.img. This does not require any modification to the installation tree. To use this method, edit the kernel command line to include inst.updates.

inst.updates=http://website.com/path/to/updates.img.

Updates from a disk image

Save an updates.img on a USB key.

inst.updates=sda1:/images/updates.img for an updates image located in the images directory on the sda1 device or inst.updates=UUID=b4234403-dafb-44c1-b878-4d57b40c9843:/updates.img for an update image located in the root directory of a partition identified by its UUID.

Updates from an installation tree

If you are using a CD, disk, HTTP, HTTPS, or FTP installation, save the updates.img in the installation tree so that all installations can detect the .img file. The file name must be updates.img.

For NFS installs, save the file in the images/ directory, or in the RHupdates/ directory.
inst.syslog=
Sends log messages to the syslog process on the specified host when the installation starts. You can use inst.syslog=<host>[:port] only if the remote syslog process is configured to accept incoming connections.
inst.virtiolog=
Use the inst.virtiolog=<name> option to specify which virtio port (a character device at /dev/virtio-ports/<name>) to use for forwarding logs. The default value is org.fedoraproject.anaconda.log.0.
rd.live.ram
Copies the stage 2 image in images/install.img into RAM. This increases the memory required for installation by the size of the image that might result in an additional requirement of approximately 1 GiB of RAM or more.
inst.nokill
Prevent the installation program from rebooting when a fatal error occurs, or at the end of the installation process. Use it capture installation logs which would be otherwise lost upon reboot.
inst.noshell
Prevent a shell on terminal session 2 (tty2) including tmux window 2, during installation.
inst.notmux
Prevent the use of tmux during installation. The output is generated without the terminal control characters and is meant for non-interactive uses.