Home » IBM Manuals » Desktops » IBM HS20 » Manual Viewer

IBM HS20 Hardware Maintenance Manual - Page 88

CD-ROM drive problems, Symptom, FRU/action, Verify that, Clean the CD.

UPC - 087944983033

Add to My Manuals
Save this manual to your list of manuals

Page 88 highlights

Note: See "System" on page 94 to determine which components should be replaced by a field service technician. CD-ROM drive problems Symptom FRU/action CD-ROM drive is not recognized. 1. Verify that: v All cables and jumpers are installed correctly. v The correct device driver is installed for the CD-ROM drive. 2. Run CD-ROM drive diagnostics. 3. CD-ROM drive. CD is not working properly. 1. Clean the CD. 2. Run CD-ROM drive diagnostics. 3. CD-ROM drive. CD-ROM drive tray is not 1. Insert the end of a straightened paper clip into the manual tray-release working. (The computer must be opening. turned on.) 2. Run CD-ROM drive diagnostics. 3. CD-ROM drive. 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.) v 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 /media/cdrom auto ro,noauto,user,exec 0 0 CD-ROM drive is not Note: Because the BladeCenter unit uses a USB bus to communicate with the recognized after being switched media tray devices, switching ownership of the media tray to another blade server back to blade server running is the same as unplugging a USB device. Windows 2000 Advanced v Before switching ownership of the CD-ROM drive (media tray) to another blade Server with SP3 applied. (When server, safely stop the media tray devices on the blade server that currently the CD-ROM drive is owned by owns the media tray, as follows: blade server x, is switched to another blade server, then is switched back to blade server x, 1. Double-click the Unplug or Eject Hardware icon in the Windows taskbar at the bottom right of the screen. the operating system in blade 2. Select USB Floppy and click Stop. server x no longer recognizes 3. Select USB Mass Storage Device and click Stop. the CD-ROM drive. This happens when you have not safely stopped the drives before 4. Click Close. You can now safely switch ownership of the media tray to another blade server. switching ownership of the CD-ROM drive, diskette drive, and USB port (media tray).) 78 BladeCenter HS20 Type 8832: Hardware Maintenance Manual and Troubleshooting Guide

Section	Page
About this manual	5
Important safety information	5
Online support	5
Contents	7
Chapter 1. Introduction	11
Related documentation	14
Features and specifications	15
BladeCenter HS20 specifications for non-NEBS/ETSI environments	15
BladeCenter HS20 specifications for NEBS/ETSI environments	16
Notices and statements used in this book	17
Chapter 2. Blade server power, controls, and indicators	19
Turning on the blade server	19
Turning off the blade server	19
Blade server controls and LEDs	20
Chapter 3. Configuration	23
Using the Configuration/Setup Utility program	24
Starting the Configuration/Setup Utility program	24
Configuration/Setup Utility menu choices	24
ServerGuide Setup and Installation CD	24
Installing the operating system without ServerGuide	25
Using passwords	25
Starting the PXE boot agent utility program	25
Firmware updates	26
Configuring the Gigabit Ethernet controllers	27
Blade server Ethernet controller enumeration	28
Configuring an IDE RAID	28
Chapter 4. Diagnostics	29
General checkout	29
Diagnostic tools overview	30
POST	31
POST error logs	31
Viewing error logs from the Configuration/Setup Utility program	31
Diagnostic programs and error messages	31
Starting the diagnostic programs	32
Viewing the test log	33
Diagnostic error message tables	33
Error symptoms	33
Error symptom charts	33
Small computer system interface messages	34
Light path diagnostics	34
Memory errors	35
Recovering the BIOS code	35
Chapter 5. Customer replacement units	37
Installation guidelines	37
System reliability considerations	37
Handling static-sensitive devices	37
Major components of the blade server	38
Replacing the blade server in the BladeCenter unit	39
Removing the blade server from the BladeCenter unit	39
Installing the blade server in the BladeCenter unit	41
Operating the blade server cover	44
Opening the blade server cover	44
Closing the blade server cover	45
Replacing the blade server bezel assembly	46
Removing the blade server bezel assembly	46
Installing the blade server bezel assembly	47
Installing IDE disk drives	47
Memory modules	49
Memory technology and Chipkill	49
Memory considerations	49
Installing memory modules	50
Installing an additional microprocessor	51
Installing an I/O expansion card	54
Installing an expansion unit	56
Installing a SCSI hot-swap hard disk drive	58
Replacing a SCSI hot-swap hard disk drive	60
Replacing the battery	60
Completing the installation	62
Updating the blade server configuration	63
Input/output connectors and devices	63
Chapter 6. Installing the operating system	65
Using RDM Version 4.11 Update 3 or later	65
Downloading installation instructions	65
Chapter 7. Field replaceable units	67
Microprocessor removal	67
Thermal grease	69
System board	70
System board component locations	70
Switches and jumpers	71
Switches	71
Jumpers	71
System board LED locations	72
System board removal	73
Chapter 8. Symptom-to-FRU index	75
Beep symptoms	75
No-beep symptoms	78
Diagnostic error codes	78
POST error codes	81
Light path diagnostics	85
IDE RAID	87
Error symptoms	87
Service processor error codes	96
SCSI error codes	97
Temperature error messages	97
Power error messages	97
System shutdown	99
System errors	99
Temperature-related system shutdown	99
DASD checkout	100
Undetermined problems	100
Problem determination tips	101
Chapter 9. Parts listing, Type 8832	103
System	104
Appendix A. Getting help and technical assistance	105
Before you call	105
Using the documentation	105
Getting help and information from the World Wide Web	105
Software service and support	106
Hardware service and support	106
Appendix B. Safety information	107
General safety	107
Electrical safety	108
Safety inspection guide	109
Grounding requirements	110
Safety notices (multi-lingual translations)	110
Appendix C. Notices	147
Edition notice	147
Trademarks	148
Important notes	148
Product recycling and disposal	149
Battery return program	149
Electronic emission notices	150
Federal Communications Commission (FCC) statement	150
Industry Canada Class A emission compliance statement	150
Australia and New Zealand Class A statement	150
United Kingdom telecommunications safety requirement	150
European Union EMC Directive conformance statement	151
Taiwanese Class A warning statement	151
Chinese Class A warning statement	151
Japanese Voluntary Control Council for Interference (VCCI) statement	151
Index	153
B	153
C	153
D	153
E	153
F	153
G	154
H	154
I	154
J	154
K	154
L	154
M	154
N	154
O	154
P	154
R	155
S	155
T	155
U	155
V	155

Match case Limit results 1 per page

Note:

See “System” on page 94 to determine which components should be replaced by a field service technician.

CD-ROM drive problems

Symptom

FRU/action

CD-ROM drive is not

recognized.

Verify that:

All cables and jumpers are installed correctly.

The correct device driver is installed for the CD-ROM drive.

Run CD-ROM drive diagnostics.

CD-ROM drive.

CD is not working properly.

Clean the CD.

Run CD-ROM drive diagnostics.

CD-ROM drive.

CD-ROM drive tray is not

working. (The computer must be

turned on.)

Insert the end of a straightened paper clip into the manual tray-release

opening.

Run CD-ROM drive diagnostics.

CD-ROM drive.

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

Establish a link between /dev/sr0 and /dev/cdrom as follows:

Enter the following command:

rm /dev/cdrom; ln -s /dev/sr0 /dev/cdrom

Insert the following line in the /etc/fstab file:

/dev/cdrom

/media/cdrom

auto

ro,noauto,user,exec

CD-ROM drive is not

recognized after being switched

back to blade server running

Windows 2000 Advanced

Server with SP3 applied. (When

the CD-ROM drive is owned by

blade server x, is switched to

another blade server, then is

switched back to blade server x,

the operating system in blade

server x no longer recognizes

the CD-ROM drive. This

happens when you have not

safely stopped the drives before

switching ownership of the

CD-ROM drive, diskette drive,

and USB port (media tray).)

Note:

Because the BladeCenter unit uses a USB bus to communicate with the

media tray devices, switching ownership of the media tray to another blade server

is the same as unplugging a USB device.

Before switching ownership of the CD-ROM drive (media tray) to another blade

server, safely stop the media tray devices on the blade server that currently

owns the media tray, as follows:

Double-click the Unplug or Eject Hardware icon in the Windows taskbar at

the bottom right of the screen.

Select USB Floppy and click Stop.

Select USB Mass Storage Device and click Stop.

Click Close.

You can now safely switch ownership of the media tray to another blade server.

BladeCenter HS20 Type 8832: Hardware Maintenance Manual and Troubleshooting Guide