Chapter 56. Installation and Booting

download PDF

Dell Latitude E6430 laptops shut down unexpectedly

When booting a Dell Latitude E6430 laptop with an Nvidia graphics card and Nvidia Optimus enabled in the BIOS, as soon as the system attempts to use the Nvidia GPU, the system shuts down. The BIOS then incorrectly displays a system board thermal trip error at next boot. To work around this problem, use the nouveau.runpm=0 parameter when booting. However, note that using nouveau.runpm=0 can increase power consumption. (BZ#1349827)

Insufficient /boot partition size may prevent the system from upgrading

The /boot partition, which contains installed kernels and initial ram disks, may become full if multiple kernels and additional packages such as kernel-debug are installed. This is caused by the default size of this partition being set to 500 MB during installation, and prevents the system from being upgraded.
As a workaround, use yum to remove older kernels if you do not need them.
This known issue only affects installation made with Red Hat Enterprise Linux 7.2 and earlier. In Red Hat Enterprise Linux 7.3, the default size of the /boot partition is increased to 1 GB, which avoids this problem in future upgrades. (BZ#1270883)

Anaconda Kickstart accepts passwords that are too short

When using a Kickstart file to install Red Hat Enterprise Linux 7, the Anaconda installer immediately accepts passwords that are shorter than the minimal length defined by the --minlen Kickstart option, if the password is sufficiently strong (quality value 50 or above by default). (BZ#1383718, BZ#1356975)

The SCAP password length requirement is ignored in the kickstart installation

The interactive kickstart installation does not enforce the password length check defined by the SCAP rule and accepts shorter root passwords. To work around this problem, use the --strict option with the pwpolicy root command in the kickstart file. (BZ#1372791)

No name server is included in /etc/resolv.conf after an iSCSI installation with a static IP address

When connecting to the root file system on an iSCSI target from an interface with a static IP address, the name server is not configured on the installed system. To work around this problem, add the nameserver=<IP> kernel option to the boot loader configuration of the installed system. (BZ#1363831)

Generating a partition scheme based on the Standard Partition recipe is not possible when installing on an EAV DASD

Installing to a large enough Common Disk Layout (CDL) Direct Access Storage Device (DASD), for example Extended Address Volumes (EAVs), prompts the installer to create the /home partition in addition to /, swap, and /boot. Since CDL DASDs can only have three partitions, an error occurs. To work around this problem, create the disk layout manually. You can also use LVM with multiple logical volumes (LVs), but /boot must exist only on a separate, standard partition. (BZ#1370173)

Anaconda does not allow creating users without passwords

Currently, it is not possible to unselect the Require a password to use this account option in the Anaconda GUI during an interactive installation. As a consequence, it is impossible to create a user account that does not have a password. To work around this problem, use a Kickstart file installation with an --emptyok option in the pwpolicy user line. (BZ#1380277)

Anaconda Kickstart installation does not respect the --changesok option

Currently, using the --changesok option when installing Red Hat Enterprise Linux 7 from a Kickstart file does not correctly allow the Anaconda installer to change the root password. (BZ#1356966)

ISO files on hard disk drives cannot be mounted by the Anaconda TUI

ISO files on hard disk drives cannot be mounted by the Anaconda Terminal User Interface (TUI). Consequently, it is not possible to use an ISO file on a hard disk as an installation source. If you try installing from an ISO file on a hard disk, a No mountable devices found error is displayed.
It is possible to use inst.repo=hd:/dev/<hard disk>:/ parameter on the command line, but you cannot change the network configuration in the installer. Consequently, the installation source is reset, and there is no chance to access the ISO file again. (BZ#1369818)

Initial Setup does not open in a graphical interface over SSH on IBM z Systems

When connecting to an IBM z Systems machine using SSH, the Initial Setup interface after Red Hat Enterprise Linux 7 installation is opened in the text version even if X forwarding is enabled. (BZ#1378082)

PXE boot with UEFI and IPv6 displays the grub2 shell instead of the operating system selection menu

When the Pre-Boot Execution Environment (PXE) starts on a client configured with UEFI and IPv6, the boot menu configured in the /boot/grub/grub.cfg file is not displayed Instead, the following occurs. The client obtains an IPv6 address from the expected DHCPv6 subnet, and downloads the .../grubx64.efi netboot image from the PXE server. After a timeout, the GRUB2 shell is displayed instead of the configured operating system selection menu. (BZ#1154226)

FIPS mode unsupported when installing from an HTTPS kickstart source

Installation images do not support FIPS mode during installation with an HTTPS kickstart source. As a consequence, it is currently impossible to to install a system with the fips=1 and inst.ks=https://<location>/ks.cfg options added to the command line. (BZ#1341280)

Extra time needed for installation when geolocation services are enabled

When installing Red Hat Enterprise Linux 7.3 with limited or no internet access, the installer pauses for a few minutes in the Installation Summary screen with the Security Policy section being Not ready. Consequently, this adds extra time before the installation proceeds to the next step.
To work around this problem, disable geolocation services by adding the inst.geoloc=0 option to the boot command line. (BZ#1380224)
Red Hat logoGithubRedditYoutubeTwitter


Try, buy, & sell


About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

© 2024 Red Hat, Inc.