Questo contenuto non è disponibile nella lingua selezionata.
14.2. Trouble During the Installation
14.2.1. No Disks Detected
In the Installation Destination screen, the following error message can appear at the bottom: No disks detected. Please shut down the computer, connect at least one disk, and restart to complete installation.
The message indicates that Anaconda did not find any writable storage devices to install to. In that case, first make sure that your system does have at least one storage device attached.
If your system uses a hardware RAID controller, verify that the controller is properly configured and working. See your controller's documentation for instructions.
If you are installing into one or more iSCSI devices and there is no local storage present on the system, make sure that all required LUNs (Logical Unit Numbers) are being presented to the appropriate HBA (Host Bus Adapter). For additional information about iSCSI, see Appendix B, iSCSI Disks.
If you made sure you have a connected and properly configured storage device and the message still appears after you reboot the system and start the installation again, it means that the installation program failed to detect the storage. In most cases this message appears when you attempt to install on an SCSI device which has not been recognized by the installation program.
In that case, you will have to perform a driver update before starting the installation. Check your hardware vendor's website to determine if a driver update is available that fixes your problem. For more general information on driver updates, see Chapter 11, Updating Drivers During Installation on IBM Power Systems.
You can also consult the Red Hat Hardware Compatibility List, available online at https://hardware.redhat.com.
14.2.2. Reporting Traceback Messages
If the graphical installation program encounters an error, it presents you with a crash reporting dialog box. You can then choose to send information about the problem you encountered to Red Hat. To send a crash report, you will need to enter your Customer Portal credentials. If you do not have a Customer Portal account, you can register at https://www.redhat.com/wapps/ugc/register.html. Automated crash reporting also requires a working network connection.
Figure 14.1. The Crash Reporting Dialog Box
When the dialog appears, select to report the problem, or to exit the installation.
Optionally, click More Info to display detailed output that can help determine the cause of the error. If you are familiar with debugging, click . This will take you to virtual terminal
tty1, where you can request more precise information that will enhance the bug report. To return to the graphical interface from tty1, use the continue command.
Figure 14.2. The Expanded Crash Reporting Dialog Box
If you want to report the bug to the customer portal, follow the procedure below.
Procedure 14.2. Reporting Errors to Red Hat Customer Support
- In the menu that appears, select Report a bug to Red Hat Customer Portal.
- To report the bug to Red Hat, you first need to provide your Customer Portal credentials. Click .
Figure 14.3. Customer Portal Credentials
- A new window is now open, prompting you to enter your Customer Portal user name and password. Enter your Red Hat Customer Portal credentials.
Figure 14.4. Configure Red Hat Customer Support
If your network settings require you to use aHTTPorHTTPSproxy, you can configure it by expanding the Advanced menu and entering the address of the proxy server.When you put in all required credentials, click OK to proceed. - A new window appears, containing a text field. Write down any useful information and comments here. Describe how the error can be reproduced by explaining each step you took before the crash reporting dialog appeared. Provide as much relevant detail as possible, including any information you acquired when debugging. Be aware that the information you provide here can become publicly visible on the Customer Portal.If you do not know what caused the error, check the box labeled I don't know what caused this problem at the bottom of the dialog.Then, click .
Figure 14.5. Describe the Problem
- Next, review the information that will be sent to the Customer Portal. The explanation you provided is in the comment tab. Other tabs include such information as your system's host name and other details about the installation environment. You can remove any items you do not want sent to Red Hat, but be aware that providing less detail can affect the investigation of the issue.Click when you finish reviewing the information to be sent.
Figure 14.6. Review the Data to Be Sent
- Review the list of files that will be sent and included in the bug report as individual attachments. These files provide system information that will assist the investigation. If you do not want to send certain files, uncheck the box next to each one. To provide additional files that can help find the problem, click .Once you have reviewed the files to be sent, check the box labeled I have reviewed the data and agree with submitting it. Then, click to send the report and attachments to the Customer Portal.
Figure 14.7. Review the Files to Be Sent
- When the dialog reports that processing has finished, you can click Show log to view details of the reporting process or Close to return to the initial crash reporting dialog box. There, click Quit to exit the installation.
14.2.3. Creating Pre-installation Log Files
To debug installation problems you can set the
inst.debug option to create log files from the environment before the installation starts. These log files contain, for example, the current storage configuration.
To set the option in the Red Hat Enterprise Linux installation boot menu:
- Select the entry.
- Press the Tab key to edit the boot options.
- Append
inst.debugto the options. For example:> vmlinuz ...
inst.debugFor further details, see Chapter 23, Boot Options. - Press Enter to start the setup.
The system stores the pre-installation log files in the
/tmp/pre-anaconda-logs/ directory before Anaconda starts. To access the log files:
- Switch to the console. See Section 8.2.1, “Accessing Consoles”.
- Change into the
/tmp/pre-anaconda-logs/directory:# cd /tmp/pre-anaconda-logs/
14.2.4. Other Partitioning Problems for IBM Power Systems Users
If you create partitions manually, but cannot move to the next screen, you probably have not created all the partitions necessary for installation to proceed.
You must have the following partitions as a bare minimum:
- A
/(root) partition - A
PReP Bootpartition - A
/bootpartition (only if the root partition is a LVM logical volume or Btrfs subvolume)
See Section 13.15.4.4, “Recommended Partitioning Scheme” for more information.
