IBM 8862 Hardware Maintenance Manual - Page 25

Diagnostics

Get IBM 8862 - Eserver xSeries 365 PDF manuals and user guides
UPC - 000435172679
View all IBM 8862 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 25 highlights

Chapter 3. Diagnostics This chapter provides basic troubleshooting information to help solve some common problems that might occur with the server. If you cannot locate and correct the problem using the information in this chapter, see Appendix A, "Getting help and technical assistance," on page 145 for more information. General checkout Follow the checkout procedure for diagnosing hardware problems. Review the following information before performing the checkout procedure: v Read the safety information beginning on page 147. v The diagnostics programs provide the primary methods of testing the major components of the server, including the I/O board, Ethernet controller, RAM, keyboard, mouse (pointing device), serial ports, hard disk drives, and parallel port. You can also use them to test some external devices. If you are not sure whether a problem is caused by the hardware or by the software, you can use the diagnostics programs to confirm that the hardware is working correctly. The diagnostic programs (see "Starting the diagnostic programs" on page 23) are in the system flash erasable programmable read-only memory (EPROM) on the I/O board. v When you run the diagnostics programs, a single problem might cause several error messages. If you receive several error messages, correct the cause of the first error message. The other error messages might not occur the next time you run the diagnostics programs. v Before running the diagnostics programs, you must determine whether the failing server is part of a shared hard disk drive cluster (two or more servers sharing external storage devices). If you suspect that it is part of a cluster, you can run all diagnostics programs except the ones that test the storage unit (that is, a hard disk drive in the storage unit) or the storage adapter that is attached to the storage unit. The failing server might be part of a cluster if any of the following conditions is true: - The customer identifies the failing server as part of a cluster. - One or more external storage units are attached to the failing server and at least one of the attached storage units is also attached to another server or unidentifiable device. - One or more servers are located near the failing server. v Important: 1. When testing a server that is part of a shared hard disk drive cluster, run only one test at a time, in looped mode. Do not run all tests in looped mode, because the hard disk drive tests might run. 2. If more than one error code is displayed, correct the first error. The other error codes might not occur the next time you run the diagnostics programs. 3. If the server is suspended and a POST error code is displayed, see "POST error logs" on page 17. 4. If the server is suspended and no error message is displayed, see "Error symptoms" on page 121 and "Undetermined problems" on page 136. 5. For information about power-supply problems, see "Power checkout" on page 27. © Copyright IBM Corp. 2003 15

  • 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
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
Chapter
3.
Diagnostics
This
chapter
provides
basic
troubleshooting
information
to
help
solve
some
common
problems
that
might
occur
with
the
server.
If
you
cannot
locate
and
correct
the
problem
using
the
information
in
this
chapter,
see
Appendix
A,
“Getting
help
and
technical
assistance,”
on
page
145
for
more
information.
General
checkout
Follow
the
checkout
procedure
for
diagnosing
hardware
problems.
Review
the
following
information
before
performing
the
checkout
procedure:
v
Read
the
safety
information
beginning
on
page
147.
v
The
diagnostics
programs
provide
the
primary
methods
of
testing
the
major
components
of
the
server,
including
the
I/O
board,
Ethernet
controller,
RAM,
keyboard,
mouse
(pointing
device),
serial
ports,
hard
disk
drives,
and
parallel
port.
You
can
also
use
them
to
test
some
external
devices.
If
you
are
not
sure
whether
a
problem
is
caused
by
the
hardware
or
by
the
software,
you
can
use
the
diagnostics
programs
to
confirm
that
the
hardware
is
working
correctly.
The
diagnostic
programs
(see
“Starting
the
diagnostic
programs”
on
page
23)
are
in
the
system
flash
erasable
programmable
read-only
memory
(EPROM)
on
the
I/O
board.
v
When
you
run
the
diagnostics
programs,
a
single
problem
might
cause
several
error
messages.
If
you
receive
several
error
messages,
correct
the
cause
of
the
first
error
message.
The
other
error
messages
might
not
occur
the
next
time
you
run
the
diagnostics
programs.
v
Before
running
the
diagnostics
programs,
you
must
determine
whether
the
failing
server
is
part
of
a
shared
hard
disk
drive
cluster
(two
or
more
servers
sharing
external
storage
devices).
If
you
suspect
that
it
is
part
of
a
cluster,
you
can
run
all
diagnostics
programs
except
the
ones
that
test
the
storage
unit
(that
is,
a
hard
disk
drive
in
the
storage
unit)
or
the
storage
adapter
that
is
attached
to
the
storage
unit.
The
failing
server
might
be
part
of
a
cluster
if
any
of
the
following
conditions
is
true:
–
The
customer
identifies
the
failing
server
as
part
of
a
cluster.
–
One
or
more
external
storage
units
are
attached
to
the
failing
server
and
at
least
one
of
the
attached
storage
units
is
also
attached
to
another
server
or
unidentifiable
device.
–
One
or
more
servers
are
located
near
the
failing
server.
v
Important:
1.
When
testing
a
server
that
is
part
of
a
shared
hard
disk
drive
cluster,
run
only
one
test
at
a
time,
in
looped
mode.
Do
not
run
all
tests
in
looped
mode,
because
the
hard
disk
drive
tests
might
run.
2.
If
more
than
one
error
code
is
displayed,
correct
the
first
error.
The
other
error
codes
might
not
occur
the
next
time
you
run
the
diagnostics
programs.
3.
If
the
server
is
suspended
and
a
POST
error
code
is
displayed,
see
“POST
error
logs”
on
page
17.
4.
If
the
server
is
suspended
and
no
error
message
is
displayed,
see
“Error
symptoms”
on
page
121
and
“Undetermined
problems”
on
page
136.
5.
For
information
about
power-supply
problems,
see
“Power
checkout”
on
page
27.
©
Copyright
IBM
Corp.
2003
15