Red Hat ENTERPRISE LINUX 5.5 - S 2010, Руководство пользователя

Страница: 311 / 470

Chapter 5.
301
Known Issues
5.1. anaconda
The anaconda package contains the program which was used to install your system.
The following are the Known Issues that apply to the anaconda package in Red Hat Enterprise Linux 5
• anaconda sometimes crashes while attempting to install on a disk containing partitions or
filesystems used by other operating systems. To workaround this issue, clear the existing partition
table using the command:
clearpart ---initlabel [disks]
BZ#530465
1
• Performing a System z installation when the install.img is located on direct access storage device
(DASD) disk, will cause 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. To work around this issue, a non-DASD source should be used for install.img.
BZ#455929
2
• When installing to an ext3 or ext4 file system, anaconda disables periodic filesystem checking.
Unlike ext2, these filesystems are journaled, removing the need for a periodic filesystem check. In
the rare cases where there is an error detected at runtime or an error while recovering the filesystem
journal, the file system check will be run at boot time.
(BZ#513480)
3
• If unmodified kickstart files from Red Hat Enterprise Linux 5.4 are used to install Red Hat Enterprise
Linux 5.5, anaconda may crash and complain that the directory required to save the log files does
not exist.(
BZ#568861
4
)
• Red Hat Enterprise Linux 5 does not support having a separate /var on a network filesystem (nfs,
iscsi disk, nbd, etc.) This is because /var contains the utilities required to bring up the network,
for example /var/lib/dhcp. However, you may have /var/spool, /var/www or the like on a separate
network disk, just not the complete /var filesystem.
BZ#485478
5
• When using rescue mode on an installation which uses iscsi drives which were manually configured
during installation, the automatic mounting of the root filesystem will not work and you need to
configure iscsi and mount the filesystems manually. This only applies to manual configured iscsi
drives, iscsi drives which are automatically detected through ibft are fully supported in rescue mode.
To rescue a system which has / on a non ibft configured iscsi drive, choose to skip the mounting of
the root fs when asked and then follow the steps below.
$TARGET_IP: IP address of the iscsi target (drive)
$TARGET_IQN: name of the iscsi target as printed by the discovery command
$ROOT_DEV: devicenode (/dev/.....) where your root fs lives
1. Define an initiator name.
$ mkdir -/etc/iscsi