IBM 8676 Hardware Maintenance Manual - Page 99

Error, symptoms

Get IBM 8676 - Eserver xSeries 335 PDF manuals and user guides
UPC - 087944770107
View all IBM 8676 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 99 highlights

Error symptoms You can use the error symptom table to find solutions to problems that have definite symptoms. If you cannot find the problem in the error symptom charts, go to "Starting the diagnostic programs" on page 22 to test the server. If you have just added new software or a new option and your server is not working, do the following before using the error symptom charts: v Remove the software or device that you just added. v Run the diagnostic tests to determine if your server is running correctly. v 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 112 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 The IDE channel to which the CD-ROM drive is attached (primary or secondary) is enabled in the Configuration/Setup Utility program. 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. Note: See "System" on page 112 to determine which components should be replaced by a field service technician. Diskette drive problems Symptom FRU/action Diskette drive activity LED stays 1. If there is a diskette in the drive, verify that: on, or the system bypasses the v The diskette drive is enabled in the Configuration/Setup utility program. diskette drive. v The diskette is good and not damaged. (Try another diskette if you have one.) v The diskette is inserted correctly in the drive. v The diskette contains the necessary files to start the server. v The software program is working properly. v The cable is installed correctly (in the proper orientation). 2. Run diskette drive diagnostics. 3. Cable. 4. Diskette drive. 5. System board. Chapter 6. Symptom-to-FRU index 89

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
Error
symptoms
You
can
use
the
error
symptom
table
to
find
solutions
to
problems
that
have
definite
symptoms.
If
you
cannot
find
the
problem
in
the
error
symptom
charts,
go
to
“Starting
the
diagnostic
programs”
on
page
22
to
test
the
server.
If
you
have
just
added
new
software
or
a
new
option
and
your
server
is
not
working,
do
the
following
before
using
the
error
symptom
charts:
v
Remove
the
software
or
device
that
you
just
added.
v
Run
the
diagnostic
tests
to
determine
if
your
server
is
running
correctly.
v
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
112
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
The
IDE
channel
to
which
the
CD-ROM
drive
is
attached
(primary
or
secondary)
is
enabled
in
the
Configuration/Setup
Utility
program.
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.
Note:
See
“System”
on
page
112
to
determine
which
components
should
be
replaced
by
a
field
service
technician.
Diskette
drive
problems
Symptom
FRU/action
Diskette
drive
activity
LED
stays
on,
or
the
system
bypasses
the
diskette
drive.
1.
If
there
is
a
diskette
in
the
drive,
verify
that:
v
The
diskette
drive
is
enabled
in
the
Configuration/Setup
utility
program.
v
The
diskette
is
good
and
not
damaged.
(Try
another
diskette
if
you
have
one.)
v
The
diskette
is
inserted
correctly
in
the
drive.
v
The
diskette
contains
the
necessary
files
to
start
the
server.
v
The
software
program
is
working
properly.
v
The
cable
is
installed
correctly
(in
the
proper
orientation).
2.
Run
diskette
drive
diagnostics.
3.
Cable.
4.
Diskette
drive.
5.
System
board.
Chapter
6.
Symptom-to-FRU
index
89