Red Hat ENTERPRISE LINUX 5 - VIRTUAL SERVER ADMINISTRATION, Руководство по установке

Страница: 246 / 388

Chapter 21. Troubleshooting Installation on an IBM System z System
228
You must have the following partitions as a bare minimum:
• A
/
(root) partition
• A <swap> partition of type swap
Note
When defining a partition's type as swap, do not assign it a mount point.
Disk Druid
automatically assigns the mount point for you.
21.2.4. 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 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
anaconda
. Errata can be
found at:
http://www.redhat.com/support/errata/
The
anaconda
website may also be a useful reference and can be found online at:
http://fedoraproject.org/wiki/Anaconda
You can also search for bug reports related to this problem. To search Red Hat's bug tracking system,
go to:
http://bugzilla.redhat.com/bugzilla/