Download Red Hat Enterprise Linux 5 5.8 Technical Notes

Chapter 2. Known Issues
In the above setup, Anaconda created the PReP partition on mpath0 (sdb/sdd), but set the bootlist to
boot from sda. T o work around this issue, follow these steps:
1. Add m path to the append line in the /etc/yaboot.conf file.
2. Use the --ondisk=m apper/m path0 in all part directives of the kickstart file.
3. Add the following script to the %post section of the kickstart file.
%post
# Determine the boot device
device=;
# Set the bootlist in NVRAM
if [ "z$device" != "z" ]; then
bootlist -m normal $device;
# Print the
bootlist -m
bootlist -m
else
echo "Could
exit 1;
fi
resulting boot list in the log
normal -o;
normal -r;
not determine boot device!";
T he above script simply ensures that the bootlist is set to boot from the disk with the PReP
partition.
Mounting an NFS volume in the rescue environment requires portmap to be running. T o start
portmap, run:
/usr/sbin/portmap
Failure to start portmap will return the following NFS mount errors:
sh-3.2# mount 192.168.11.5:/share /mnt/nfs
mount: Mounting 192.168.11.5:/share on /mnt/nfs failed: Input/output error
T he order of device names assigned to USB attached storage devices is not guaranteed. Certain
USB attached storage devices may take longer to initialize than others, which can result in the device
receiving a different name than you expect (for example, sdc instead of sda).
During installation, be sure to verify the storage device size, name, and type when configuring
partitions and file systems.
anaconda occasionally crashes while attempting to install on a disk containing partitions or file
systems used by other operating systems. T o workaround this issue, clear the existing partition
table using the command:
clearpart --initlabel [disks]
(BZ #530465)
Performing a System z installation, when the install.im g is located on direct access storage
device (DASD) disk, causes the installer to crash, returning a backtrace. anaconda is attempting to
re-write (commit) all disk labels when partitioning is complete, but is failing because the partition is
busy. T o work around this issue, a non-DASD source should be used for install.im g.
(BZ #455929)
When installing to an ext3 or ext4 file system, anaconda disables periodic file system checking.
Unlike ext2, these file systems are journaled, removing the need for a periodic file system check. In
25