Installation guide

No matter what type of installation you are performing, backups of the existing data on your systems
should always be made.
14 .3.4 . Ot her Part it ioning Problems for IBMPOWER Syst em Users
If you are using Disk Dru id to create partitions, but cannot move to the next screen, you probably
have not created all the partitions necessary for Disk Dru id '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.
A /boot/ partition.
Note
When defining a partition's type as swap, do not assign it a mount point. Disk Dru id
automatically assigns the mount point for you.
14 .3.5. Are You Seeing Pyt hon Errors?
During some upgrades or installations of Red Hat Enterprise Linux, the installation program (also
known as an aco n d a) 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 the /tmp/directory. 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 doInstall
self.fstab.savePartitions ()
File "fstab.py", line 221, in savePartitions
sys.exit(0)
SystemExit: 0
Local variables in innermost frame:
self: <fstab.GuiFstab instance at 8446fe0>
sys: <module 'sys' (built-in)>
ToDo object: (itodo ToDo p1 (dp2 S'method' p3 (iimage CdromInstallMethod
p4 (dp5 S'progressWindow' p6 <failed>
This error occurs in some systems where links to /tmp/ are symbolic to other locations or have been
changed since creation. These symbolic or changed links are invalid during the installation process,
so the installation program cannot write information and fails.
If you experience such an error, first try to download any available errata for an aco n d a. Errata can
be found at:
http://www.redhat.com/support/errata/
The an aco n d a website may also be a useful reference and can be found online at:
Chapt er 1 4 . T roubleshoot ing Inst allat ion on an IBM PO WER Syst em
165