IBM RS6000 Service Guide - Page 116

E1xx Code Boot Problems - boot from cd

Get IBM RS6000 - 7026 - H70 PDF manuals and user guides View all IBM RS6000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 116 highlights

6. Replace the Memory Card. 7. Replace the System Board. 8. Replace the CPU Card(s). E1xx Code Boot Problems: Depending on the boot device, a checkpoint may be displayed on the operator panel for an extended period of time while the boot image is retrieved from the device. This is particularly true for Tape and Network boot attempts. If the checkpoint/code is displayed for an extended time there may be a problem loading the boot image from the device. If booting from CD-ROM or Tape, watch for "activity" on the drive's LED indicator. A blinking LED means that the loading of either the boot image or additional information required by the operating system being booted is still in progress. For network boot attempts, if the system is not connected to an active network or if the target server is inaccessible (this can also result from incorrect IP parameters being supplied), the system still attempts to boot and because time-out durations are necessarily long to accommodate retries, the system may appear to be hung. 1. Restart the system and get to the Firmware SMS utilities. In the utilities check: Is the intended boot device correctly specified in the boot sequence? - If the intended boot device is not correctly identified in the boot sequence, add it to the boot sequence using the SMS menus. For network boot attempts: - Are the IP parameters correct? - Attempt to "Ping" the target server using the SMS "Ping" utility. 2. If the checkpoint E105 or E15B is displayed for an extended time, there may be a problem with the integrity of the boot image. Try to boot and run standalone diagnostics against the system, particularly against the intended boot device. If the diagnostics are successful, it may be necessary to perform an operating system specific recovery process, or reinstall the operating system. 3. If attempting to boot from a Hard disk, CD-ROM, or Tape drive: a. Try a different CD/Tape (unless booting from Hard disk). b. Verify proper SCSI bus termination. c. Replace SCSI cable. d. It is possible that another attached SCSI device is causing the problem. Disconnect any other SCSI devices attached to the same controller as the one the boot device is attached to and retry the boot operation. If this is successful, one of the devices removed is causing the problem, re-attach devices one by one and retry the boot operation until the problem recurs and replace the device that caused the problem. e. Replace SCSI adapter (if drive is attached to a card rather than the I/O Board). f. Replace SCSI drive. 3-44 Service Guide

  • 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
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
6. Replace the Memory Card.
7. Replace the System Board.
8. Replace the CPU Card(s).
E1xx Code Boot Problems:
Depending on the boot device, a checkpoint may
be displayed on the operator panel for an extended period of time while the boot
image is retrieved from the device.
This is particularly true for Tape and Network
boot attempts.
If the checkpoint/code is displayed for an extended time there may
be a problem loading the boot image from the device.
If booting from CD-ROM or
Tape, watch for “activity” on the drive's LED indicator.
A blinking LED means that
the loading of either the boot image or additional information required by the
operating system being booted is still in progress.
For network boot attempts, if the system is not connected to an active network or if
the target server is inaccessible (this can also result from incorrect IP parameters
being supplied), the system still attempts to boot and because time-out durations are
necessarily long to accommodate retries, the system may appear to be hung.
1. Restart the system and get to the Firmware SMS utilities.
In the utilities check:
±
Is the intended boot device correctly specified in the boot sequence?
–
If the intended boot device is not correctly identified in the boot
sequence, add it to the boot sequence using the SMS menus.
±
For network boot attempts:
–
Are the IP parameters correct?
–
Attempt to “Ping” the target server using the SMS “Ping” utility.
2. If the checkpoint E105 or E15B is displayed for an extended time, there may be
a problem with the integrity of the boot image.
±
Try to boot and run standalone diagnostics against the system, particularly
against the intended boot device.
If the diagnostics are successful, it may be
necessary to perform an operating system specific recovery process, or
reinstall the operating system.
3. If attempting to boot from a Hard disk, CD-ROM, or Tape drive:
a. Try a different CD/Tape (unless booting from Hard disk).
b. Verify proper SCSI bus termination.
c. Replace SCSI cable.
d. It is possible that another attached SCSI device is causing the problem.
Disconnect any other SCSI devices attached to the same controller as the
one the boot device is attached to and retry the boot operation.
If this is
successful, one of the devices removed is causing the problem, re-attach
devices one by one and retry the boot operation until the problem recurs and
replace the device that caused the problem.
e. Replace SCSI adapter (if drive is attached to a card rather than the I/O
Board).
f. Replace SCSI drive.
3-44
Service Guide