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

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

Chapter 21.
227
Troubleshooting Installation on an IBM
System z System
This appendix discusses some common installation problems and their solutions.
21.1. You are Unable to Boot Red Hat Enterprise Linux
21.1.1. Is Your System Displaying Signal 11 Errors?
A signal 11 error, commonly know as a
segmentation fault
, means that the program accessed a
memory location that was not assigned to it. A signal 11 error may be due to a bug in one of the
software programs that is installed, or faulty hardware.
Ensure that you have the latest installation updates and images from Red Hat. Review the online
errata to see if newer versions are available.
21.2. Trouble During the Installation
21.2.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
, then there may be an issue with your DASD devices. If you encounter this error, add
the
DASD=< disks >
parameter to your
parm
file (where
disks
is the DASD range reserved for
installation) and start the install again.
Additionally, make sure you format the DASDs using the
dasdfmt
command within a Linux root shell,
instead of formatting the DASDs using CMS.
21.2.2. Trouble with Partition Tables
If you receive an error after the
Disk Partitioning Setup
(
Section 17.11, “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.
21.2.3. Other Partitioning Problems
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.