Follow Techotopia on Twitter

On-line Guides
All Guides
eBook Store
iOS / Android
Linux for Beginners
Office Productivity
Linux Installation
Linux Security
Linux Utilities
Linux Virtualization
Linux Kernel
System/Network Admin
Programming
Scripting Languages
Development Tools
Web Development
GUI Toolkits/Desktop
Databases
Mail Systems
openSolaris
Eclipse Documentation
Techotopia.com
Virtuatopia.com

How To Guides
Virtualization
General System Admin
Linux Security
Linux Filesystems
Web Servers
Graphics & Desktop
PC Hardware
Windows
Problem Solutions
Privacy Policy

  




 

 

NOTE: CentOS Enterprise Linux 5 is built from the Red Hat Enterprise Linux source code. Other than logo and name changes CentOS Enterprise Linux 5 is compatible with the equivalent Red Hat version. This document applies equally to both Red Hat and CentOS Enterprise Linux 5.

14.3. Trouble During the Installation

14.3.1. No devices found to install Red Hat Enterprise Linux Error Message

If you receive an error message stating No devices found to install Red Hat Enterprise Linux, there is probably a SCSI controller that is not being recognized by the installation program.

Check your hardware vendor's website to determine if a driver diskette image is available that fixes your problem. For more general information on driver diskettes, refer to Chapter 13, Driver Media for IBM POWER Systems.

You can also refer to the Red Hat Hardware Compatibility List, available online at:

https://hardware.redhat.com/hcl/    

14.3.2. Saving Traceback Messages Without a Diskette Drive

If you receive a traceback error message during installation, you can usually save it to a diskette.

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 headless IBM System p 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.

14.3.3. Trouble with Partition Tables

If you receive an error after the Disk Partitioning Setup (Section 12.16, “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 recognizable 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.

14.3.4.  Other Partitioning Problems for IBM™ POWER 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.

  • A /boot/ partition.

Tip

When defining a partition's type as swap, do not assign it a mount point. Disk Druid automatically assigns the mount point for you.

14.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 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:

          https://www.redhat.com/support/errata/
        

The anaconda website may also be a useful reference and can be found online at:

          https://rhlinux.redhat.com/anaconda/
        

You can also search for bug reports related to this problem. To search Red Hat's bug tracking system, go to:

          https://bugzilla.redhat.com/bugzilla/
        

Finally, if you are still facing problems related to this error, register your product and contact our support team. To register your product, go to:

          https://www.redhat.com/apps/activate/
        

 
 
  Published under the terms of the GNU General Public License Design by Interspire