Red Hat ENTERPRISE LINUX 3 - FOR IBM ESERVER ISERIES AND IBM ESERVER PSERIES, Руководство по установке

Страница: 57 / 80

Appendix B. Troubleshooting Your Installation of Red Hat Enterprise Linux 49
If you do not have a diskette drive available in your system, you can
scp
the error message to a remote
system.
This information does not apply to users of iSeries systems or headless pSeries systems.
When the traceback dialog appears, the traceback error message is automatically written to a file
named
/tmp/anacdump.txt
. Once the dialog appears, switch over to a new tty (virtual console) by
pressing the keys
[Ctrl]-[Alt]-[F2]
and
scp
the message written to
/tmp/anacdump.txt
to a
known working remote system.
B.3.3. Trouble with Partition Tables
If you receive an error after the
Disk Partitioning Setup
(Section 2.13 Disk Partitioning Setup ) phase
of the installation saying something similar to
The partition table on device hda was unreadable. To create new partitions it must be initialized,
causing the loss of ALL DATA on this drive.
you may not have a partition table on that drive or the partition table on the drive may not be recog-
nizable by the partitioning software used in the installation program.
No matter what type of installation you are performing, backups of the existing data on your systems
should always be made.
B.3.4. Other Partitioning Problems for iSeries and pSeries System Users
If you are using Disk Druid to create partitions, but cannot move to the next screen, you probably
have not created all the partitions necessary for
Disk Druid
’s dependencies to be satisfied.
You must have the following partitions as a bare minimum:
•
A
/
(root) partition
•
A swap partition of type swap
•
A PPC PReP Boot partition.
•
For pSeries users only, a
/boot/
partition.
Tip
When defining a partition’s type as swap, you do not have to assign it a mount point. Disk Druid
automatically assigns the mount point for you.
B.3.5. Are You Seeing Python Errors?
During some upgrades or installations of Red Hat Enterprise Linux, the installation program (also
known as anaconda ) may fail with a Python or traceback error. This error may occur after the selection
of individual packages or while trying to save the upgrade log in
/tmp/
. The error may look similar
to:
Traceback (innermost last):
File "/var/tmp/anaconda-7.1//usr/lib/anaconda/iw/progress_gui.py",
line 20, in run
rc = self.todo.doInstall ()
File "/var/tmp/anaconda-7.1//usr/lib/anaconda/todo.py", line 1468, in