IBM BladeCenter JS22 Problem Determination And Service Manual page 48

Table 11. B200xxxx Logical partition SRCs (continued)
v Follow the suggested actions in the order in which they are listed in the Action column until the problem is
solved. If an action solves the problem, then you can stop performing the remaining actions.
v See Chapter 3, "Parts listing, Type 7998," on page 235 to determine which components are CRUs and which
components are FRUs.
B200 xxxx Error
Code Description
3200 Informational system log entry only.
4158 Informational system log entry only.
4400 A problem occurred during the
startup of a partition.
5106 A problem occurred during the
startup of a partition. There is not
enough space to contain the partition
main storage dump. The startup will
not continue.
5109 A problem occurred during the
startup of a partition. There was a
partition main storage dump
problem. The startup will not
continue.
5114 A problem occurred during the
startup of a partition. There is not
enough space to contain the partition
main storage dump. The startup will
not continue.
5115 A problem occurred during the
startup of a partition. There was an
error reading the partition main
storage dump from the partition
load source into main storage. The
startup will attempt to continue.
5117 A problem occurred during the
startup of a partition. A partition
main storage dump has occurred but
cannot be written to the load source
device because a valid dump already
exists.
5121 A problem occurred during the
startup of a partition. There was an
error writing the partition main
storage dump to the partition load
source. The startup will not
continue.
5122 Informational system log entry only.
5123 Informational system log entry only.
5135 A problem occurred during the
startup of a partition. There was an
error writing the partition main
storage dump to the partition load
source. The main store dump startup
will continue.
34
JS22 Type 7998: Problem Determination and Service Guide
Action
No corrective action is required.
No corrective action is required.
Check for server firmware updates; then, install the
updates if available.
Verify that there is sufficient memory available to start the
partition as it is configured. If there is already enough
memory, then go to "Isolating firmware problems" on
page 222.
Go to "Isolating firmware problems" on page 222.
Go to "Isolating firmware problems" on page 222.
If the startup does not continue, look for and resolve
other errors.
Use the Main Storage Dump Manager to rename or copy
the current main storage dump.
Look for related errors in the "Product Activity Log" and
fix any problems found. Use virtual control panel
function 34 to retry the current Main Store Dump startup
while the partition is still in the failed state.
No corrective action is required.
No corrective action is required.
Look for other errors and resolve them.