2. Installation-Related Notes
2.1. All Architectures
- The Anaconda now offers the option of switching to Virtual Network Computing (VNC) to complete the installation.installation of
- Creating or using encrypted software RAID member disks (i.e.
software RAIDpartitions) is not supported. However, creating encrypted software RAID arrays (e.g.
/dev/md0) is supported.
- The NFS default for RHEL5 is "locking". Therefore, to mount nfs shares from the %post section of anaconda, use the
mount -o nolock,udpcommand to start the locking daemon before using nfs to mount shares.
- When installing from CD-ROM or DVD-ROM on a system with an iBFT-configured network device, Anaconda will not include any iBFT-configured storage devices unless networking is configured. To enable networking for the installation, use the command
linux updates=http://[any]at the installation boot prompt. Note that
[any]can be replaced with any URL.If your system requires a static IP configuration, use the command
linux updates=http://[any] ip=[IP address] netmask=[netmask] dns=[dns].
- When installing Red Hat Enterprise Linux 5.3 on a fully virtualized guest, do not use the
kernel-xenkernel. Using this kernel on fully virtualized guests can cause your system to hang.If you are using an Installation Number when installing Red Hat Enterprise Linux 5.3 on a fully virtualized guest, be sure to deselect the
Virtualizationpackage group during the installation. The
Virtualizationpackage group option installs the
kernel-xenkernel.Note that paravirtualized guests are not affected by this issue. Paravirtualized guests always use the
- If you are using the Virtualized kernel when upgrading from Red Hat Enterprise Linux 5 to 5.2, you must reboot after completing the upgrade. You should then boot the system using the updated Virtualized kernel.The hypervisors of Red Hat Enterprise Linux 5 and 5.2 are not ABI-compatible. If you do not boot the system after upgrading using the updated Virtualized kernel, the upgraded Virtualization RPMs will not match the running kernel.
- When upgrading to Red Hat Enterprise Linux 5.1 or later from Red Hat Enterprise Linux 4.6,
gcc4may cause the upgrade to fail. As such, you should manually remove the
gcc4package before upgrading.
firstbootlanguage plugin has been removed, as it does not properly and completely reconfigure the system when a new language is selected.
- When provisioning guests during installation, theoption will not be available. When this occurs, the system will require an additional entitlement, separate from the entitlement used by
dom0.To prevent the consumption of additional entitlements for guests, install the
rhn-virtualization-commonpackage manually before attempting to register the system to Red Hat Network.
- Installing Red Hat Enterprise Linux 5.3 on a system with multiple network interfaces and manually specified IPv6 addresses may result in a partially incorrect networking setup. When this occurs, your IPv6 settings will not be visible on the installed system.To work around this, set
/etc/sysconfig/network. Then, restart your network connection using the command
service network restart.
- If your system has
yum-rhn-plugin-0.5.2-5.el5_1.2(or an earlier version) installed, you will be unable to upgrade to Red Hat Enterprise Linux 5.3 through
yum update. To work around this, upgrade your
yum-rhn-pluginto the latest version (using
yum update yum-rhn-plugin) before running
- Previously, anaconda could not access more than 8 SmartArray controllers. In this update, this issue has been resolved.
- A driver disk, supplied by an OEM, is a single image file (*
.img), containing potentially multiple driver packages and kernel modules. These drivers are used during installation to support hardware that otherwise would not be recognized by Red Hat Enterprise Linux 5. Once the driver packages and kernel modules are installed on the system, they are placed in the initial RAM disk (
initrd) so that they are loaded when the system boots.With this release, installation can automatically detect a driver disk (based on its file system label), thereby using the content of that disk during installation. This behavior is controlled by the installation command line option
dlabel=on, which enables the automatic search.
dlabel=onis the default setting for this release.All block devices with the file system label
OEMDRVare examined and drivers are loaded from these devices in the order by which they are detected.
- Existing encrypted block devices that contain
vfatfile systems will appear as type
foreignin the partitioning interface; as such, these devices will not be mounted automatically during system boot. To ensure that such devices are mounted automatically, add an appropriate entry for them to
/etc/fstab. For details on how to do so, refer to
2.2. PowerPC Architectures
- The minimum RAM required to install Red Hat Enterprise Linux 5.2 is 1GB; the recommended RAM is 2GB. If a machine has less than 1GB RAM, the installation process may hang.Further, PowerPC-based machines that have only 1GB of RAM experience significant performance issues under certain RAM-intensive workloads. For a Red Hat Enterprise Linux 5.2 system to perform RAM-intensive processes optimally, 4GB of RAM is recommended. This ensures the system has the same number of physical pages as was available on PowerPC machines with 512MB of RAM running Red Hat Enterprise Linux 4.5 or earlier.
2.3. s390x Architectures
anacondanow supports both ports on CHPID for OSA Express3 cards. The installer will prompt for the port number in the initial stage of the installation. The value provided for the port also affects installed network interface startup script. When port 1 is selected, the value
portno=1is added to OPTIONS parameter of
NoteWhen installing under z/VM, you can add either
PORTNO=0(to use port 0) or
PORTNO=1(to use port 1) to the CMS configuration file to avoid being prompted for the mode.
- Installation on a machine with existing Linux or non-Linux filesystems on DASD block devices may cause the installer to halt. If this happens, it is necessary to clear out all existing partitions on the DASD devices you want to use and restart the installer.
2.4. ia64 Architecture
- If your system only has 512MB of RAM, attempting to install Red Hat Enterprise Linux 5.3 may fail. To prevent this, perform a base installation first and install all other packages after the installation finishes.
yumto install packages from the
32-bit Compatibility Layerdisc may fail. If it does, it is because the Red Hat package signing key was not imported into the RPM database. This happens if you have not yet connected to Red Hat Network and obtained updates. To import the key manually, run the following command as root:
rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-releaseOnce the Red Hat GPG key is imported, you may now use
yumto install packages from the
32-bit Compatibility Layerdisc.Note that when installing from this disc, it is advisable to use
rpmto ensure that base OS dependencies are addressed during installation.