Red Hat Enterprise Linux 4: Installation Guide for x86, Itanium™, AMD64, and Intel® Extended Memory 64 Technology (Intel® EM64T)
Prev | Appendix C. Troubleshooting Your Installation of Red Hat Enterprise Linux | Next

# C.3. Trouble During the Installation

## C.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 Appendix E Driver Media.

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

    http://hardware.redhat.com/hcl/

## C.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.

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 `<KEYCAP >[Ctrl]</KEYCAP >-<KEYCAP >[Alt]</KEYCAP >-<KEYCAP >[F2]</KEYCAP >` and `scp` the message written to `/tmp/anacdump.txt` to a known working remote system.

## C.3.3. Trouble with Partition Tables

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

Users who have used programs such as EZ-BIOS have experienced similar problems, causing data to be lost (assuming the data was not backed up before the installation began) that could not be recovered.

No matter what type of installation you are performing, backups of the existing data on your systems should always be made.

## C.3.4. Using Remaining Space

You have a `swap` and a `/` (root) partition created, and you have selected the root partition to use the remaining space, but it does not fill the hard drive.

If your hard drive is more than 1024 cylinders, you must create a `/boot` partition if you want the `/` (root) partition to use all of the remaining space on your hard drive.

## C.3.5. Other Partitioning Problems for x86 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

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

## C.3.6. Other Partitioning Problems for Itanium 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 `/boot/efi/` partition of type VFAT

- A `/` (root) partition

- A <swap> partition of type swap

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

## C.3.7. 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://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:

    http://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:

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

Prev | Home | Next
Trouble Beginning the Installation | Up | Problems After Installation