Table of Contents
Advertisement
Error symptoms
You can use the error symptom table to find solutions to problems that have definite symptoms.
If you have just added new software or a new option and the server is not working, do the following
before using the error symptom charts:
•
Remove the software or device that you just added.
•
Run the diagnostic tests to determine if the server is running correctly.
•
Reinstall the new software or new device.
In the following table, if the entry in the FRU/action column is a suggested action, perform that
action; if it is the name of a component, reseat the component and replace it if necessary. The most
likely cause of the symptom is listed first.
NOTE
See "System" on page 130 to determine which components should be replaced by a field
service technician.
CD-ROM drive problems
Symptom
CD-ROM drive is not
recognized.
CD is not working properly.
CD-ROM drive tray is not
working.
CD-ROM drive is seen as
/dev/sr0 by SuSE. (If the
SuSE Linux operating
system is installed remotely
onto a blade server that is
not the current owner of the
media tray (CD-ROM drive,
diskette drive, and USB
port), SuSE sees the CD-
ROM drive as /dev/sr0
instead of /dev/cdrom.)
110
FRU/action
1. Verify that:
•
All cables and jumpers are installed correctly.
•
The correct device driver is installed for the CD-ROM drive.
2.
CD-ROM drive.
1. Clean the CD.
2.
CD-ROM drive.
NOTE
Blade server must have ownership of CD-ROM drive.
1. Insert the end of a straightened paper clip into the manual tray-
release opening.
2.
CD-ROM drive.
•
Establish a link between /dev/sr0 and /dev/cdrom as follows:
1.
Enter the following command:
rm /dev/cdrom; ln -s /dev/sr0 /dev/cdrom
2.
Insert the following line in the /etc/fstab file:
/dev/cdrom
ro,noauto,user,exec
Intel® Server Compute Blade SBX82: Hardware Maintenance Manual and Troubleshooting Guide
/media/cdrom
auto
0 0
Advertisement
Table of Contents
