IBM HS12 Service Guide - Page 138

ServerGuide problems, Service processor problems, Software problems, Suggested action

Page 138 highlights

ServerGuide problems Use this information to locate ServerGuide problems and suggested actions. The following table lists problem symptoms and suggested solutions. Symptom Suggested action The ServerGuide Setup and Installation CD will not start. v Make sure that the CD drive is associated with the blade server that you are configuring. v Make sure that the blade server supports the ServerGuide program and has a bootable CD (or DVD) drive. v If the startup (boot) sequence settings have been changed, make sure that the CD drive is first in the startup sequence. The RAID configuration program cannot view all installed drives, or the operating system cannot be installed. v Make sure that there are no duplicate SCSI/SAS IDs or interrupt request (IRQ) assignments. See "Configuring a SAS RAID array" on page 22. v Make sure that the storage drive is connected correctly. See "System-board connectors" on page 11 to locate the storage drive connector. The operating-system installation program continuously loops. Make more space available on the hard disk. The ServerGuide program will not start the operating-system CD. Make sure that the operating-system CD is supported by the ServerGuide program. See the ServerGuide Setup and Installation CD label for a list of supported operating-system versions. The operating system cannot be installed; the option is not available. Make sure that the operating system is supported on the blade server. If the operating system is supported, either no logical drive is defined (SCSI/SAS RAID systems) or the ServerGuide System Partition is not present. Run the ServerGuide program and make sure that setup is complete. Service processor problems Use this information to diagnose and resolve service processor problems for the blade server. Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 4, "Parts listing, Types 8014, 8028 and 1916," on page 25 to determine which components are CRUs and which components are FRUs. v If an action step is preceded by "(Trained service technician only)," that step must be performed only by a trained service technician. Symptom Action The management module reports a general monitor failure. Disconnect the BladeCenter unit from all electrical sources, wait for 30 seconds, reconnect the BladeCenter unit to the electrical sources, and restart the blade server. If the problem remains, see "Solving undetermined problems" on page 171. Software problems Use this information to diagnose and resolve software problems for the blade server. Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. 126 BladeCenter HS12 Type 8014, 8028 or 1916: Problem Determination and 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

ServerGuide problems
Use this information to locate ServerGuide problems and suggested actions.
The following table lists problem symptoms and suggested solutions.
Symptom
Suggested action
The
ServerGuide Setup and
Installation
CD will not start.
v
Make sure that the CD drive is associated with the blade server that you are
configuring.
v
Make sure that the blade server supports the ServerGuide program and has a
bootable CD (or DVD) drive.
v
If the startup (boot) sequence settings have been changed, make sure that the
CD drive is first in the startup sequence.
The RAID configuration
program cannot view all
installed drives, or the
operating system cannot be
installed.
v
Make sure that there are no duplicate SCSI/SAS IDs or interrupt request (IRQ)
assignments. See “Configuring a SAS RAID array” on page 22.
v
Make sure that the storage drive is connected correctly. See “System-board
connectors” on page 11 to locate the storage drive connector.
The operating-system
installation program
continuously loops.
Make more space available on the hard disk.
The ServerGuide program will
not start the operating-system
CD.
Make sure that the operating-system CD is supported by the ServerGuide
program. See the
ServerGuide Setup and Installation
CD label for a list of supported
operating-system versions.
The operating system cannot be
installed; the option is not
available.
Make sure that the operating system is supported on the blade server. If the
operating system is supported, either no logical drive is defined (SCSI/SAS RAID
systems) or the ServerGuide System Partition is not present. Run the ServerGuide
program and make sure that setup is complete.
Service processor problems
Use this information to diagnose and resolve service processor problems for the
blade server.
Follow the suggested actions in the order in which they are listed in the Action
column until the problem is solved.
v
See Chapter 4, “Parts listing, Types 8014, 8028 and 1916,” on page 25 to determine which components are CRUs
and which components are FRUs.
v
If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Symptom
Action
The management module
reports a general monitor
failure.
Disconnect the BladeCenter unit from all electrical sources, wait for 30 seconds,
reconnect the BladeCenter unit to the electrical sources, and restart the blade
server. If the problem remains, see “Solving undetermined problems” on page 171.
Software problems
Use this information to diagnose and resolve software problems for the blade
server.
Follow the suggested actions in the order in which they are listed in the Action
column until the problem is solved.
126
BladeCenter HS12 Type 8014, 8028 or 1916: Problem Determination and Service Guide