Interactively installing RHEL from installation media

Procedure

1. From the Installation Summary window, click Installation Destination. Perform the following operations in the Installation Destination window that opens:

   1. From the Local Standard Disks section, select the storage device that you require; a white check mark indicates your selection. Disks without a white check mark are not used during the installation process; they are ignored if you choose automatic partitioning, and they are not available in manual partitioning.

      The Local Standard Disks shows all locally available storage devices. For example, SATA, NVMe™ and SCSI disks, USB flash and external disks. Storage devices connected post starting the installation program are not detected, unless you follow the step 2 below. If you use a removable drive to install RHEL, your system is unusable if you remove the device.

   2. Optional: Click the Refresh link in the lower right-hand side of the window if you want to configure additional local storage devices connected after the installation program has started. The Rescan Disks dialog box opens.

      1. Click Rescan Disks and wait until the scanning process completes.

         All storage changes that you make during the installation are lost when you click Rescan Disks.

      2. Click OK to return to the Installation Destination window. All detected disks including any new ones are displayed under the Local Standard Disks section.

2. Optional: Click Add a disk…​ to add a specialized storage device.

   The Storage Device Selection window opens and lists all storage devices that the installation program has access to.

3. Optional: Under Storage Configuration, select the Automatic radio button for automatic partitioning.

   You can also configure custom partitioning. For more details, see Configuring manual partitioning.

4. Optional: Select Free up space by removing or shrinking existing partitions to reclaim space from an existing partitioning layout. For example, if a disk you want to use already has a different operating system and you want to make this system’s partitions smaller to allow more room for Red Hat Enterprise Linux.

5. Optional: Select Encrypt my data to encrypt all partitions except the ones needed to boot the system (such as /boot) by using Linux Unified Key Setup (LUKS). Encrypting your disk adds an extra layer of security.

   1. Click Done. The Disk Encryption Passphrase dialog box opens.

      1. Type your passphrase in the Passphrase and Confirm fields.

      2. Click Save Passphrase to complete disk encryption.

         Warning

         If you lose the LUKS passphrase, any encrypted partitions and their data is completely inaccessible. There is no way to recover a lost passphrase. However, if you perform a Kickstart installation, you can save encryption passphrases and create backup encryption passphrases during the installation.

6. Optional: Click the Full disk summary and bootloader link in the lower left-hand side of the window to select which storage device contains the boot loader. For more information, see Configuring boot loader.

   In most cases it is sufficient to leave the boot loader in the default location. Some configurations, for example, systems that require chain loading from another boot loader require the boot drive to be specified manually.

7. Click Done.

8. Optional: The Reclaim Disk Space dialog box appears if you selected automatic partitioning and the Free up space by removing or shrinking existing partitions option, or if there is not enough free space on the selected disks to install Red Hat Enterprise Linux. It lists all configured disk devices and all partitions on those devices. The dialog box displays information about the minimal disk space the system needs for an installation with the currently selected package set and how much space you have reclaimed. To start the reclaiming process:

   1. Review the displayed list of available storage devices. The Reclaimable Space column shows how much space can be reclaimed from each entry.
   2. Select a disk or partition to reclaim space.
   3. Use the Shrink button to use free space on a partition while preserving the existing data.
   4. Use the Delete button to delete that partition or all partitions on a selected disk including existing data.
   5. Use the Delete all button to delete all existing partitions on all disks including existing data and make this space available to install Red Hat Enterprise Linux.

   6. Click Reclaim space to apply the changes and return to graphical installations.

      No disk changes are made until you click Begin Installation on the Installation Summary window. The Reclaim Space dialog only marks partitions for resizing or deletion; no action is performed.

Procedure

1. From the Installation Destination window, click the Full disk summary and bootloader link. The Selected Disks dialog box opens.

   The boot loader is installed on the device of your choice, or, on a UEFI system; the EFI system partition is created on the target device and used to store the boot loader files.

2. To change the boot device, select a device from the list and click Set as Boot Device. You can set only one device as the boot device.

3. To disable a new boot loader installation, select the device currently marked for boot and click Do not install boot loader. This ensures GRUB2 is not installed on any device.

   Warning

   If you choose not to install a boot loader, you cannot boot the system directly and you must use another boot method, such as a standalone commercial boot loader application. Use this option only if you have another way to boot your system.

   The boot loader may also require a special partition to be created, depending on if your system uses BIOS or UEFI firmware, or if the boot drive has a GUID Partition Table (GPT) or a Master Boot Record (MBR, also known as msdos) label. If you use automatic partitioning, the installation program creates the partition.

Procedure

1. From the Installation Summary window, click Installation Destination. The Installation Destination window opens, listing all available drives.
2. Under the Specialized & Network Disks section, click Add a disk. The storage devices selection window opens.

3. Click the Search by tab to search by port, target, LUN, or WWID.

   Searching by WWID or LUN requires additional values in the corresponding input text fields.

4. Select the option that you require from the Search drop-down menu.
5. Click Find to start the search. Each device is presented on a separate row with a corresponding check box.

6. Select the check box to enable the device that you require during the installation process.

   Later in the installation process you can choose to install Red Hat Enterprise Linux on any of the selected devices, and you can choose to mount any of the other selected devices as part of the installed system automatically. Selected devices are not automatically erased by the installation process and selecting a device does not put the data stored on the device at risk.

   Note

   You can add devices to the system after installation by modifying the /etc/fstab file.

7. Click Done to return to the Installation Destination window.

   Any storage devices that you do not select are hidden from the installation program entirely. To chain load the boot loader from a different boot loader, select all the devices present.

Procedure

1. From the Installation Summary window, click Installation Destination. The Installation Destination window opens, listing all available drives.
2. Under the Specialized & Network Disks section, click Add a disk. The storage devices selection window opens.

3. Click Add iSCSI target. The Add iSCSI Storage Target window opens.

   Important

   You cannot place the /boot partition on iSCSI targets that you have manually added by using this method. An iSCSI target containing a /boot partition must be configured for use with iBFT. However, in instances where the installed system is expected to boot from iSCSI with iBFT configuration provided by a method other than firmware iBFT. For example, by using iPXE, you can remove the /boot partition restriction by using the inst.nonibftiscsiboot installer boot option.

4. Enter the IP address of the iSCSI target in the Target IP Address field.

5. Type a name in the iSCSI Initiator Name field for the iSCSI initiator in iSCSI qualified name (IQN) format. A valid IQN entry contains the following information:

   • The string iqn. (note the period).
   • A date code that specifies the year and month in which your organization’s Internet domain or subdomain name was registered, represented as four digits for the year, a dash, and two digits for the month, followed by a period. For example, represent September 2010 as 2010-09.
   • Your organization’s Internet domain or subdomain name, presented in reverse order with the top-level domain first. For example, represent the subdomain storage.example.com as com.example.storage.

   • A colon followed by a string that uniquely identifies this particular iSCSI initiator within your domain or subdomain. For example :diskarrays-sn-a8675309.

     A complete IQN is as follows: iqn.2010-09.storage.example.com:diskarrays-sn-a8675309. The installation program pre-populates the iSCSI Initiator Name field with a name in this format to help you with the structure. For more information about IQNs, see 3.2.6. iSCSI Names in RFC 3720 - Internet Small Computer Systems Interface (iSCSI) available from tools.ietf.org and 1. iSCSI Names and Addresses in RFC 3721 - Internet Small Computer Systems Interface (iSCSI) Naming and Discovery available from tools.ietf.org.

6. Select the Discovery Authentication Type drop-down menu to specify the type of authentication to use for iSCSI discovery. The following options are available:

   • No credentials
   • CHAP pair
   • CHAP pair and a reverse pair

7. Do one of the following:

   1. If you selected the CHAP pair as the authentication type, enter the user name and password for the iSCSI target in the CHAP Username and CHAP Password fields.
   2. If you selected the CHAP pair and a reverse pair as the authentication type, enter the user name and password for the iSCSI target in the CHAP Username and CHAP Password field, and the user name and password for the iSCSI initiator in the Reverse CHAP Username and Reverse CHAP Password fields.
8. Optional: Select the Bind targets to network interfaces check box.

9. Click Start Discovery.

   The installation program attempts to discover an iSCSI target based on the information provided. If discovery succeeds, the Add iSCSI Storage Target window displays a list of all iSCSI nodes discovered on the target.

10. Select the check boxes for the node that you want to use for installation.

    The Node login authentication type menu contains the same options as the Discovery Authentication Type menu. However, if you need credentials for discovery authentication, use the same credentials to log in to a discovered node.

11. Click the additional Use the credentials from discovery drop-down menu. When you provide the proper credentials, the Log In button becomes available.

12. Click Log In to initiate an iSCSI session.

    While the installer uses iscsiadm to find and log into iSCSI targets, iscsiadm automatically stores any information about these targets in the iscsiadm iSCSI database. The installer then copies this database to the installed system and marks any iSCSI targets that are not used for root partition, so that the system automatically logs in to them when it starts. If the root partition is placed on an iSCSI target, initrd logs into this target and the installer does not include this target in start up scripts to avoid multiple attempts to log into the same target.

Procedure

1. From the Installation Summary window, click Installation Destination. The Installation Destination window opens, listing all available drives.
2. Under the Specialized & Network Disks section, click Add a disk. The storage devices selection window opens.
3. Click Add FCoE SAN. A dialog box opens for you to configure network interfaces for discovering FCoE storage devices.
4. Select a network interface that is connected to an FCoE switch in the NIC drop-down menu.
5. Click Add FCoE disk(s) to scan the network for SAN devices.

6. Select the required check boxes:

   • Use DCB:Data Center Bridging (DCB) is a set of enhancements to the Ethernet protocols designed to increase the efficiency of Ethernet connections in storage networks and clusters. Select the check box to enable or disable the installation program’s awareness of DCB. Enable this option only for network interfaces that require a host-based DCBX client. For configurations on interfaces that use a hardware DCBX client, disable the check box.
   • Use auto vlan:Auto VLAN is enabled by default and indicates whether VLAN discovery should be performed. If this check box is enabled, then the FIP (FCoE Initiation Protocol) VLAN discovery protocol runs on the Ethernet interface when the link configuration has been validated. If they are not already configured, network interfaces for any discovered FCoE VLANs are automatically created and FCoE instances are created on the VLAN interfaces.
7. Discovered FCoE devices are displayed under the Other SAN Devices tab in the Installation Destination window.

Procedure

1. From the Installation Summary window, click Installation Destination. The Installation Destination window opens, listing all available drives.
2. Under the Specialized & Network Disks section, click Add a disk. The storage devices selection window opens.
3. Click Add DASD ECKD. The Add DASD Storage Target dialog box opens and prompts you to specify a device number, such as 0.0.0204, and attach additional DASDs that were not detected when the installation started.
4. Type the device number of the DASD that you want to attach in the Device number field.

5. Click Start Discovery.

   If a DASD with the specified device number is found and if it is not already attached, the dialog box closes and the newly-discovered drives appear in the list of drives. You can then select the check boxes for the required devices and click Done. The new DASDs are available for selection, marked as DASD device 0.0.xxxx in the Local Standard Disks section of the Installation Destination window.

   If you entered an invalid device number, or if the DASD with the specified device number is already attached to the system, an error message appears in the dialog box, explaining the error and prompting you to try again with a different device number.

Procedure

1. From the Installation Summary window, click Installation Destination. The Installation Destination window opens, listing all available drives.
2. Under the Specialized & Network Disks section, click Add a disk. The storage devices selection window opens.

3. Click Add ZFCP LUN. The Add zFCP Storage Target dialog box opens allowing you to add a FCP (Fibre Channel Protocol) storage device.

   64-bit IBM Z requires that you enter any FCP device manually so that the installation program can activate FCP LUNs. You can enter FCP devices either in the graphical installation, or as a unique parameter entry in the parameter or CMS configuration file. The values that you enter must be unique to each site that you configure.

4. Type the 4 digit hexadecimal device number in the Device number field.

5. Provide following details when the zFCP device is not configured in NPIV mode or auto LUN scanning is disabled by the zfcp.allow_lun_scan=0 kernel module parameter:

   1. Type the 16 digit hexadecimal World Wide Port Number (WWPN) in the WWPN field.
   2. Type the 16 digit hexadecimal FCP LUN identifier in the LUN field.

6. Click Start Discovery to connect to the FCP device.

   The newly-added devices are displayed in the IBM Z tab of the Installation Destination window.

   Use only lower-case letters in hex values. If you enter an incorrect value and click Start Discovery, the installation program displays a warning. You can edit the configuration information and retry the discovery attempt. For more information about these values, consult the hardware documentation and check with your system administrator.

Procedure

1. From the Installation Summary window, click Installation Destination.

   The Installation Destination window opens, listing all available devices. This includes local (PCI Express transport) NVMe™ devices.

2. Under the Specialized & Network Disks section, click Add a disk…​.

   The storage devices selection window opens.

3. Click the NVMe™ Fabrics Devices tab.
4. Optional: If the device list is too long, use the Filter by option to view specific devices.
5. Select the devices from the list by using check boxes.

6. Click Done to return to the Installation Destination window.

   The NVMe™ device that you reconfigured is displayed in the Specialized & Network Disks section.

7. Click Done to return to the Installation Summary window.

Procedure

1. From the Installation Summary window, select User Settings > Root Account. The Root Account window opens.

   By default, the Disable root account option is selected.

2. To enable root account, select the Enable root account option.

3. Type your password in the Root Password field.

   The root password is case-sensitive and must be at least eight characters long containing numbers, letters (upper and lower case) and symbols.

4. Type the same password in the Confirm field.
5. Optional: Select the Allow root SSH login with password option to enable SSH access (with password) to this system as the root user. By default the password-based SSH root access is disabled.

6. Click Done to confirm your root password and return to the Installation Summary window.

   If you proceed with a weak password, you must click Done twice.

Procedure

1. On the Installation Summary window, select User Settings > User Creation. The Create User window opens.
2. Type the user account name into the Full name field, for example: John Smith.

3. Type the username into the User name field, for example: jsmith.

   The User name is used to log in from a command line; if you install a graphical environment, then your graphical login manager uses the Full name.

4. The Add administrative privileges to this…​ option is selected by default. Deselect this option if you do not want to share administrative privileges to this account. By default, new users have administrative privileges to the system.

   An administrator user can use the sudo command to perform tasks that are only available to root by using the user password, instead of the root password. Though it is more convenient, it can also introduce a security risk.

5. The Require a password to use this account option is selected by default. Disable it if you want to use this account without a password.

   If you give administrator privileges to a user, ensure the account is password protected. Never give a user administrator privileges without assigning a password to the account.

6. Type a password into the Password field.
7. Type the same password into the Confirm password field.
8. Click Done to apply the changes and return to the Installation Summary window.

Procedure

1. On the Create User window, click Advanced.
2. Edit the details in the Home directory field, if required. The field is populated by default with /home/username .

3. In the User and Groups IDs section you can:

   1. Select the Specify a user ID manually check box and use + or - to enter the required value.

      The default value is 1000. User IDs (UIDs) 0-999 are reserved by the system so they cannot be assigned to a user.

   2. Select the Specify a group ID manually check box and use + or - to enter the required value.

      The default group name is the same as the user name, and the default Group ID (GID) is 1000. GIDs 0-999 are reserved by the system so they cannot be assigned to a user group.

4. Specify additional groups as a comma-separated list in the Group Membership field. Groups that do not already exist are created; you can specify custom GIDs for additional groups in parentheses. If you do not specify a custom GID for a new group, the new group receives a GID automatically.

   The user account created always has one default group membership (the user’s default group with an ID set in the Specify a group ID manually field).

5. Click Save Changes to apply the updates and return to the Create User window.

Procedure

1. Select disks for installation:

   1. Click Installation Destination to open the Installation Destination window.
   2. Select the disks that you require for installation by clicking the corresponding icon. A selected disk has a check-mark displayed on it.
   3. Under Storage Configuration, select the Custom radio-button.
   4. Click Done.

2. Detected mount points are listed in the left-hand pane. The mount points are organized by detected operating system installations. As a result, some file systems may be displayed multiple times if a partition is shared among several installations.

   1. Select the mount points in the left pane; the options that can be customized are displayed in the right pane.
   2. Optional: If your system contains existing file systems, ensure that enough space is available for the installation. To remove any partitions, select them in the list and click the - button. The dialog has a check box that you can use to remove all other partitions used by the system to which the deleted partition belongs.

   3. Optional: If there are no existing partitions and you want to create a set of partitions as a starting point, select your preferred partitioning scheme from the left pane (default for Red Hat Enterprise Linux is LVM) and click the Click here to create them automatically link.

      Note

      A /boot partition, a / (root) volume, a swap volume proportional to the size of the available storage and optionally some other partitions, depending on system properties, such as architecture, are created and listed in the left pane. These are the file systems for a typical installation, but you can add additional file systems and mount points.

3. Optional: Continue with adding mount points and configuring the individual mount points.
4. Click Done to confirm any changes and return to the Installation Summary window.

Procedure

1. Click + to create a new file system and related mount point. The Add a New Mount Point dialog opens.
2. Select one of the preset paths from the Mount Point drop-down menu or type your own; for example, select / for the root partition or /boot for the boot partition.

3. Enter the size of the file system into the Desired Capacity field; for example, 2GiB.

   If you do not specify a value in Desired Capacity, or if you specify a size bigger than available space, then all remaining free space is used.

4. Click Add mount point to create the partition and return to the Manual Partitioning window.

Procedure

1. To change the devices that a single non-LVM mount point should be located on, select the required mount point from the left-hand pane.
2. Under the Device(s) heading, click Modify. The Configure Mount Point dialog opens.
3. Select one or more devices and click Select to confirm your selection and return to the Manual Partitioning window.
4. Click Update Settings to apply the changes.
5. In the lower left-hand side of the Manual Partitioning window, click the storage device selected link to open the Selected Disks dialog and review disk information.
6. Optional: Click the Rescan button (circular arrow button) to refresh all local disks and partitions; this is only required after performing advanced partition configuration outside the installation program. Clicking the Rescan Disks button resets all configuration changes made in the installation program.

Procedure

1. From the left pane, select the mount point.

2. From the right-hand pane, you can customize the following options:

   1. Enter the file system mount point into the Mount Point field. For example, if a file system is the root file system, enter /; enter /boot for the /boot file system, and so on. For a swap file system, do not set the mount point as setting the file system type to swap is sufficient.
   2. Enter the size of the file system in the Desired Capacity field. You can use common size units such as KiB or GiB. The default is MiB if you do not set any other unit.

   3. Select the device type that you require from the drop-down Device Type menu: Standard Partition, LVM, or LVM Thin Provisioning.

      Note

      RAID is available only if two or more disks are selected for partitioning. If you choose RAID, you can also set the RAID Level. Similarly, if you select LVM, you can specify the Volume Group.

   4. Select the Encrypt check box to encrypt the partition or volume. You must set a password later in the installation program.

   5. Select the appropriate file system type for this partition or volume from the File system drop-down menu.

      Note

      Support for the VFAT file system is not available for Linux system partitions. For example, /, /var, /usr, and so on.

   6. Select the Reformat check box to format an existing partition, or clear the Reformat check box to retain your data. The newly-created partitions and volumes must be reformatted, and the check box cannot be cleared.
   7. Type a label for the partition in the Label field. Use labels to easily recognize and address individual partitions.
   8. Type a name in the Name field. The standard partitions are named automatically when they are created and you cannot edit the names of standard partitions. For example, you cannot edit the /boot name sda1.
3. Click Update Settings to apply your changes and if required, select another partition to customize. Changes are not applied until you click Begin Installation from the Installation Summary window.
4. Optional: Click Reset All to discard your partition changes.

5. Click Done when you have created and customized all file systems and mount points. If you choose to encrypt a file system, you are prompted to create a passphrase.

   A Summary of Changes dialog box opens, displaying a summary of all storage actions for the installation program.

6. Click Accept Changes to apply the changes and return to the Installation Summary window.

Procedure

1. Click Installation Destination to open the Installation Destination window.
2. Under Storage Configuration, select the Custom radio button. Click Done.
3. Click Done, the Manual Partitioning window opens.

4. Choose the /home partition, fill in /home under Mount Point: and clear the Reformat check box.

   Figure 10.1. Ensuring that /home is not formatted

   
5. Optional: You can also customize various aspects of the /home partition required for your Red Hat Enterprise Linux 10 system as described in Customizing a mount point file system. However, to preserve /home from your RHEL 9 system, it is necessary to clear the Reformat check box.
6. After you customized all partitions according to your requirements, click Done. The Summary of changes dialog box opens.
7. Verify that the Summary of changes dialog box does not show any change for /home. This means that the /home partition is preserved.
8. Click Accept Changes to apply the changes, and return to the Installation Summary window.

Procedure

1. From the left pane of the Manual Partitioning window, select the required partition.
2. Click the Device Type drop-down menu and select RAID.
3. Under the Device(s) section, click Modify. The Configure Mount Point dialog box opens.
4. Select the disks that you want to include in the RAID device and click Select to close the dialog box.
5. Click the File System drop-down menu and select your preferred file system type.
6. Click the RAID Level drop-down menu and select your preferred level of RAID.
7. Click Update Settings to save your changes.
8. Click Done to apply the settings to return to the Installation Summary window.

Procedure

1. From the Manual Partitioning window, create a new mount point by using any of the following options:

   • Use the Click here to create them automatically option or click the + button.
   • Select Mount Point from the drop-down list or enter manually.

   • Enter the size of the file system in to the Desired Capacity field; for example, 70 GiB for /, 1 GiB for /boot.

     Note: Skip this step to use the existing mount point.

2. Select the mount point.

3. Select LVM in the drop-down menu. The Volume Group drop-down menu is displayed with the newly-created volume group name.

   Note

   You cannot specify the size of the volume group’s physical extents in the configuration dialog. The size is always set to the default value of 4 MiB. If you want to create a volume group with different physical extents, you must create it manually by switching to an interactive shell and by using the vgcreate command, or use a Kickstart file with the volgroup --pesize=size command.

4. Click Done to return to the Installation Summary window.

Procedure

1. From the Manual Partitioning window, create a mount point by using any of the following options:

   • Use the Click here to create them automatically option or click the + button.
   • Select Mount Point from the drop-down list or enter manually.

   • Enter the size of the file system in to the Desired Capacity field; for example, 70 GiB for /, 1 GiB for /boot.

     Skip this step to use the existing mount point.

2. Select the mount point.
3. Click the Device Type drop-down menu and select LVM. The Volume Group drop-down menu is displayed with the newly-created volume group name.

4. Click Modify to configure the newly-created volume group. The Configure Volume Group dialog box opens.

   Note

   You cannot specify the size of the volume group’s physical extents in the configuration dialog. The size is always set to the default value of 4 MiB. If you want to create a volume group with different physical extents, you must create it manually by switching to an interactive shell and by using the vgcreate command, or use a Kickstart file with the volgroup --pesize=size command. For more information, see the Automatically installing RHEL document.

5. Optional: From the RAID Level drop-down menu, select the RAID level that you require.

   The available RAID levels are the same as with actual RAID devices.

6. Select the Encrypt check box to mark the volume group for encryption.

7. From the Size policy drop-down menu, select any of the following size policies for the volume group:

   The available policy options are:

   Automatic

   The size of the volume group is set automatically so that it is large enough to contain the configured logical volumes. This is optimal if you do not need free space within the volume group.

   As large as possible

   The volume group is created with maximum size, regardless of the size of the configured logical volumes it contains. This is optimal if you plan to keep most of your data on LVM and later need to increase the size of some existing logical volumes, or if you need to create additional logical volumes within this group.

   Fixed

   You can set an exact size of the volume group. Any configured logical volumes must then fit within this fixed size. This is useful if you know exactly how large you need the volume group to be.

8. Click Save to apply the settings and return to the Manual Partitioning window.
9. Click Update Settings to save your changes.
10. Click Done to return to the Installation Summary window.

Procedure

1. From the Installation Summary window, click Network and Host Name.
2. From the list in the left-hand pane, select an interface. The details are displayed in the right-hand pane.

3. Toggle the ON/OFF switch to enable or disable the selected interface.

   You cannot add or remove interfaces manually.

4. Click + to add a virtual network interface, which can be either: Bond, Bridge, or VLAN.
5. Click - to remove a virtual interface.
6. Click Configure to change settings such as IP addresses, DNS servers, or routing configuration for an existing interface (both virtual and physical).

7. Type a host name for your system in the Host Name field.

   The host name can either be a fully qualified domain name (FQDN) in the format hostname.domainname, or a short hostname without the domain. Many networks have a Dynamic Host Configuration Protocol (DHCP) service that automatically supplies connected systems with a domain name. To allow the DHCP service to assign the domain name to this system, specify only the short host name.

   Host names can only contain alphanumeric characters and - or .. Host name should be equal to or less than 64 characters. Host names cannot start or end with - and .. To be compliant with DNS, each part of a FQDN should be equal to or less than 63 characters and the FQDN total length, including dots, should not exceed 255 characters.

   The value localhost means that no specific static host name for the target system is configured, and the actual host name of the installed system is configured during the processing of the network configuration, for example, by NetworkManager using DHCP or DNS.

   When using static IP and host name configuration, it depends on the planned system use case whether to use a short name or FQDN. Red Hat Identity Management configures FQDN during provisioning but some 3rd party software products may require a short name. In either case, to ensure availability of both forms in all situations, add an entry for the host in /etc/hosts in the format IP FQDN short-alias.

8. Click Apply to apply the host name to the installer environment.
9. Alternatively, in the Network and Hostname window, you can choose the Wireless option. Click Select network in the right-hand pane to select your wifi connection, enter the password if required, and click Connect.

Procedure

1. From the Network & Host name window, click the + button to add a virtual network interface. The Add a device dialog opens.

2. Select one of the four available types of virtual interfaces:

   • Bond: NIC (Network Interface Controller) Bonding, a method to bind multiple physical network interfaces together into a single bonded channel.
   • Bridge: Represents NIC Bridging, a method to connect multiple separate networks into one aggregate network.
   • Vlan (Virtual LAN): A method to create multiple distinct broadcast domains which are mutually isolated.
3. Select the interface type and click Add. An editing interface dialog box opens, allowing you to edit any available settings for your chosen interface type. For more information, see Editing network interface.
4. Click Save to confirm the virtual interface settings and return to the Network & Host name window.
5. Optional: To change the settings of a virtual interface, select the interface and click Configure.

Procedure

1. Click the General tab.
2. Select the Connect automatically with priority check box to enable connection by default. Keep the default priority setting at 0.

3. Optional: Enable or disable all users on the system from connecting to this network by using the All users may connect to this network option. If you disable this option, only root will be able to connect to this network.

   Important

   When enabled on a wired connection, the system automatically connects during startup or reboot. On a wireless connection, the interface attempts to connect to any known wireless networks in range. For further information about NetworkManager, including the nm-connection-editor tool, see the Configuring and managing networking document.

4. Click Save to apply the changes and return to the Network and Host name window.

   It is not possible to only allow a specific user other than root to use this interface, as no other users are created at this point during the installation. If you need a connection for a different user, you must configure it after the installation.

Procedure

1. To set static network configuration, navigate to one of the IPv Settings tabs and from the Method drop-down menu, select a method other than Automatic, for example, Manual. The Addresses pane is enabled.
2. Optional: In the IPv6 Settings tab, you can also set the method to Ignore to disable IPv6 on this interface.
3. Click Add and enter your address settings.
4. Type the IP addresses in the Additional DNS servers field; it accepts one or more IP addresses of DNS servers, for example, 10.0.0.1,10.0.0.8.

5. Select the Require IPvX addressing for this connection to complete check box.

   Selecting this option in the IPv4 Settings or IPv6 Settings tabs allow this connection only if IPv4 or IPv6 was successful. If this option remains disabled for both IPv4 and IPv6, the interface is able to connect if configuration succeeds on either IP protocol.

6. Click Save to apply the changes and return to the Network & Host name window.

Procedure

1. In the IPv4 Settings and IPv6 Settings tabs, click Routes to configure routing settings for a specific IP protocol on an interface. An editing routes dialog specific to the interface opens.
2. Click Add to add a route.
3. Select the Ignore automatically obtained routes check box to configure at least one static route and to disable all routes not specifically configured.

4. Select the Use this connection only for resources on its network check box to prevent the connection from becoming the default route.

   This option can be selected even if you did not configure any static routes. This route is used only to access certain resources, such as intranet pages that require a local or VPN connection. Another (default) route is used for publicly available resources. Unlike the additional routes configured, this setting is transferred to the installed system. This option is useful only when you configure more than one interface.

5. Click OK to save your settings and return to the editing routes dialog that is specific to the interface.
6. Click Save to apply the settings and return to the Network and Host Name window.

Procedure

1. Log in to your system.
2. From the top left-hand side of the window, click Activities.
3. From the menu options, click the Show Applications icon.
4. Click the Settings icon, or enter Settings Manager in the search.

5. In the left side column, select the System options, then on the new screen select Registration.

   The Registration screen displays the current status of your Subscription.

6. Click the Remove Registration… button and confirm your choice.

7. Enter your administrator password in the Authentication Required dialog box. The system is unregistered from the Subscription Management Server, and the status System Not Registered is displayed with the Register System… button enabled.

   To continue uninterrupted services, re-register the system with either of the management services. If you do not register the system with a management service, you may fail to receive the system updates.

Procedure

1. Select the Install Red Hat Enterprise Linux option from the boot menu.
2. Press the Tab key on BIOS-based systems or the e key on UEFI-based systems to edit the selected boot options.

3. Append inst.debug to the options. For example:

   vmlinuz ... inst.debug

4. Press the Enter key on your keyboard. The system stores the pre-installation log files in the /tmp/pre-anaconda-logs/ directory before the installation program starts.
5. Press Ctrl + Alt + F2 to switch to the console and access the log files.

6. Change to the /tmp/pre-anaconda-logs/ directory:

   # cd /tmp/pre-anaconda-logs/

Procedure

1. Press Ctrl + Alt + F2 to access a shell prompt on the system you are installing.

2. Connect a USB flash drive to the system and run the dmesg command:

   # dmesg

   A log detailing all recent events is displayed. At the end of this log, a set of messages is displayed. For example:

   [ 170.171135] sd 5:0:0:0: [sdb] Attached SCSI removable disk

3. Note the name of the connected device. In the above example, it is sdb.

4. Navigate to the /mnt directory and create a new directory that serves as the mount target for the USB drive. This example uses the name usb:

   # mkdir usb

5. Mount the USB flash drive onto the newly created directory. In most cases, you do not want to mount the whole drive, but a partition on it. 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

6. Verify that you mounted the correct device and partition by accessing it and listing its contents:

   # cd /mnt/usb

   # ls

7. Copy the log files to the mounted device.

   # cp /tmp/*log /mnt/usb

8. Unmount the USB flash drive. If you receive an error message that the target is busy, change your working directory to outside the mount (for example, /).

   # umount /mnt/usb

Procedure

1. Press Ctrl + Alt + F2 to access a shell prompt on the system you are installing.

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

   1. 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 where you want to save the log files. For example, if you want to log in as john on 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 is as follows:

      # scp *log john@192.168.0.122:/home/john/logs/

      When connecting to the target system for the first time, the SSH client asks you to confirm that the fingerprint of the remote system is correct and that you want to continue:

      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)?

   2. Type yes and press Enter to continue. Provide a valid password when prompted. The files are transferred to the specified directory on the target system.

Procedure

1. Log in to the root account on your system.

2. Use the grubby tool to find the default GRUB2 kernel:

   # grubby --default-kernel

   /boot/vmlinuz-6.12.0-0.el10_0.x86_64

3. Use the grubby tool to remove the rhgb boot option from the default kernel in your GRUB2 configuration. For example:

   # grubby --remove-args="rhgb" --update-kernel /boot/vmlinuz-6.12.0-0.el10_0.x86_64

4. Reboot the system. The graphical boot sequence is no longer used. If you want to enable the graphical boot sequence, follow the same procedure, replacing the --remove-args="rhgb" parameter with the --args="rhgb" parameter. This restores the rhgb boot option to the default kernel in your GRUB2 configuration.

Procedure

1. Start your system and wait until the boot loader menu is displayed. If you set your boot timeout period to 0, press the Esc key to access it.
2. From the boot loader menu, use your cursor keys to highlight the entry you want to boot. Press the Tab key on BIOS-based systems or the e key on UEFI-based systems to edit the selected entry options.
3. In the list of options, find the kernel line - that is, the line beginning with the keyword linux. On this line, locate and delete rhgb.

4. Press F10 or Ctrl+X to boot your system with the edited options.

   If the system started successfully, you can log in normally. However, if you do not disable graphical boot permanently, you must perform this procedure every time the system boots.

Procedure

1. Boot the system from either minimal boot media, or a full installation DVD or USB drive, and wait for the boot menu to be displayed.
2. From the boot menu, either select Troubleshooting > Rescue a Red Hat Enterprise Linux system option, or append the inst.rescue option to the boot command line. To enter the boot command line, press the Tab key on BIOS-based systems or the e key on UEFI-based systems.

3. Optional: If your system requires a third-party driver provided on a driver disc to boot, append the inst.dd=driver_name to the boot command line:

   inst.rescue inst.dd=driver_name

4. Optional: If a driver that is part of the Red Hat Enterprise Linux distribution prevents the system from booting, append the modprobe.blacklist= option to the boot command line:

   inst.rescue modprobe.blacklist=driver_name

5. Press Enter (BIOS-based systems) or Ctrl+X (UEFI-based systems) to boot the modified option. Wait until the following message is displayed:

   The rescue environment will now attempt to find your Linux installation and mount it under the directory: /mnt/sysroot/. You can then make any changes required to your system. Choose 1 to proceed with this step. You can choose to mount your file systems read-only instead of read-write by choosing 2. If for some reason this process does not work choose 3 to skip directly to a shell.
   
   1) Continue
   2) Read-only mount
   3) Skip to shell
   4) Quit (Reboot)

   If you select 1, the installation program attempts to mount your file system under the directory /mnt/sysroot/. You are notified if it fails to mount a partition. If you select 2, it attempts to mount your file system under the directory /mnt/sysroot/, but in read-only mode. If you select 3, your file system is not mounted.

   For the system root, the installer supports two mount points /mnt/sysimage and /mnt/sysroot. The /mnt/sysroot path is used to mount / of the target system. Usually, the physical root and the system root are the same, so /mnt/sysroot is attached to the same file system as /mnt/sysimage. The only exceptions are rpm-ostree systems, where the system root changes based on the deployment. Then, /mnt/sysroot is attached to a subdirectory of /mnt/sysimage. Use /mnt/sysroot for chroot.

6. Select 1 to continue. Once your system is in rescue mode, a prompt appears on VC (virtual console) 1 and VC 2. Use the Ctrl+Alt+F1 key combination to access VC 1 and Ctrl+Alt+F2 to access VC 2:

   sh-4.2#

7. Even if your file system is mounted, the default root partition while in rescue mode is a temporary root partition, not the root partition of the file system used during normal user mode (multi-user.target or graphical.target). If you selected to mount your file system and it mounted successfully, you can change the root partition of the rescue mode environment to the root partition of your file system by executing the following command:

   sh-4.2# chroot /mnt/sysroot

   This is useful if you need to run commands, such as rpm, that require your root partition to be mounted as /. To exit the chroot environment, type exit to return to the prompt.

8. If you selected 3, you can still try to mount a partition or LVM2 logical volume manually inside rescue mode by creating a directory, such as /directory/, and typing the following command:

   sh-4.2# mount -t xfs /dev/mapper/VolGroup00-LogVol02 /directory

   In the above command, /directory/ is the directory that you created and /dev/mapper/VolGroup00-LogVol02 is the LVM2 logical volume you want to mount. If the partition is a different type than XFS, replace the xfs string with the correct type (such as ext4).

9. If you do not know the names of all physical partitions, use the following command to list them:

   sh-4.2# fdisk -l

   If you do not know the names of all LVM2 physical volumes, volume groups, or logical volumes, use the pvdisplay, vgdisplay or lvdisplay commands.

Procedure

1. Change the root directory to the /mnt/sysroot/ directory:

   sh-4.2# chroot /mnt/sysroot/

2. Execute sos report to generate an archive with system configuration and diagnostic information:

   sh-4.2# sos report

   sos report prompts you to enter your name and the case number you received from Red Hat Support. Use only letters and numbers because adding any of the following characters or spaces could render the report unusable: # % & { } \ < > > * ? / $ ~ ' " : @ + ` | =

3. Optional: If you want to transfer the generated archive to a new location by using the network, it is necessary to have a network interface configured. In this scenario, use the dynamic IP addressing as no other steps are required. However, when using static addressing, enter the following command to assign an IP address (for example 10.13.153.64/23) to a network interface, for example dev eth0:

   bash-4.2# ip addr add 10.13.153.64/23 dev eth0

4. Exit the chroot environment:

   sh-4.2# exit

5. Store the generated archive in a new location, from where it can be easily accessible:

   sh-4.2# cp /mnt/sysroot/var/tmp/sos report new_location

6. For transferring the archive through the network, use the scp utility:

   sh-4.2# scp /mnt/sysroot/var/tmp/sos report username@hostname:sos report

Procedure

1. Change the root partition:

   sh-4.2# chroot /mnt/sysroot/

2. Reinstall the GRUB2 boot loader, where the install_device block device was installed:

   sh-4.2# /sbin/grub2-install install_device

   Important

   Running the grub2-install command could lead to the machine being unbootable if all the following conditions apply:

   • The system is an AMD64 or Intel 64 with Extensible Firmware Interface (EFI).
   • Secure Boot is enabled.

   After you run the grub2-install command, you cannot boot the AMD64 or Intel 64 systems that have Extensible Firmware Interface (EFI) and Secure Boot enabled. This issue occurs because the grub2-install command installs an unsigned GRUB2 image that boots directly instead of using the shim application. When the system boots, the shim application validates the image signature, which when not found fails to boot the system.

3. Reboot the system.

Procedure

1. To add a new driver using dnf:

   1. Make the RPM package that contains the driver available. For example, mount a CD or USB flash drive and copy the RPM package to a location of your choice under /mnt/sysroot/, for example: /mnt/sysroot/root/drivers/.

   2. Change the root directory to /mnt/sysroot/:

      sh-4.2# chroot /mnt/sysroot/

   3. Use the dnf install command to install the driver package. For example, run the following command to install the xorg-x11-drv-wacom driver package from /root/drivers/:

      sh-4.2# dnf install /root/drivers/xorg-x11-drv-wacom-0.23.0-6.el7.x86_64.rpm

      Note

      The /root/drivers/ directory in this chroot environment is the /mnt/sysroot/root/drivers/ directory in the original rescue environment.

   4. Exit the chroot environment:

      sh-4.2# exit

2. To remove a driver by using dnf:

   1. Change the root directory to the /mnt/sysroot/ directory:

      sh-4.2# chroot /mnt/sysroot/

   2. Use the dnf remove command to remove the driver package. For example, to remove the xorg-x11-drv-wacom driver package, run:

      sh-4.2# dnf remove xorg-x11-drv-wacom

   3. Exit the chroot environment:

      sh-4.2# exit

      If you cannot remove a malfunctioning driver for some reason, you can instead blocklist the driver so that it does not load at boot time.

   4. When you have finished removing drivers, reboot the system.