A B200xxxx SRC is a logical partition reference code that is related to logical partitioning.
Table 1 describes system reference codes that might be displayed if system firmware detects a problem. Suggested actions to correct the problem are also listed.
|
||
|---|---|---|
| Reference Code | Description | Action |
| B2001130 | A problem occurred during the migration of a partition
You attempted to migrate a partition to a system that has a power or thermal problem. The migration will not continue. |
Look for and fix power or thermal problems and then retry the migration. |
| B2001131 | A problem occurred during the migration
of a partition. The migration of a partition did not complete. |
Check for server firmware updates; then, install the updates if available. |
| B2001132 | A problem occurred during the startup of a partition.
A platform firmware error occurred while it was trying to allocate memory. The startup will not continue. |
Collect a platform dump and then go to Isolating firmware problems. |
| B2001133 | A problem occurred during the migration
of a partition. The migration of a partition did not complete. |
Check for server firmware updates; then, install the updates if available. |
| B2001134 | A problem occurred during the migration
of a partition. The migration of a partition did not complete. |
Check for server firmware updates; then, install the updates if available. |
| B2001140 | A problem occurred during the migration
of a partition. The migration of a partition did not complete. |
Check for server firmware updates; then, install the updates if available. |
| B2001141 | A problem occurred during the migration
of a partition. The migration of a partition did not complete. |
Check for server firmware updates; then, install the updates if available. |
| B2001142 | A problem occurred during the migration
of a partition. The migration of a partition did not complete. |
Check for server firmware updates; then, install the updates if available. |
| B2001143 | A problem occurred during the migration
of a partition. The migration of a partition did not complete. |
Check for server firmware updates; then, install the updates if available. |
| B2001144 | A problem occurred during the migration
of a partition. The migration of a partition did not complete. |
Check for server firmware updates; then, install the updates if available. |
| B2001148 | A problem occurred during the migration
of a partition. The migration of a partition did not complete. |
Check for server firmware updates; then, install the updates if available. |
| B2001150 | During the startup of a partition, a partitioning configuration problem occurred. | Go to Verifying the partition configuration. |
| B2001151 | A problem occurred during the migration
of a partition. The migration of a partition did not complete. |
Check for server firmware updates; then, install the updates if available. |
| B2001170 | During the startup of a partition, a failure occurred due to a validation error. | Go to Verifying the partition configuration. |
| B2001225 | A problem occurred during the startup of a partition. The partition attempted to start up prior to the platform fully initializing. Restart the partition after the platform has fully completed and the platform is not in standby mode. |
Restart the partition. |
| B2001230 | During the startup of a partition, a partitioning configuration problem occurred; the partition is lacking the necessary resources to start up. | Go to Verifying the partition configuration. |
| B2001260 | A problem occurred during the startup of a partition. The partition could not start at the Timed Power On setting because the partition was not set to Normal. |
Set the partition to Normal. |
| B2001265 | The partition could not start up. An operating system Main Storage Dump startup was attempted with the startup side on D-mode, which is not a valid operating system startup scenario. The startup will be halted. This SRC can occur when a D-mode SLIC installation fails and attempts a Main Storage Dump. | Correct the startup settings. |
| B2001266 | The partition could not start up. You are attempting to start up an operating system that is not supported. | Install a supported operating system and restart the partition. |
| B2001280 | A problem occurred during a partition Main Storage Dump. A mainstore dump startup did not complete due to a configuration mismatch. | Go to Isolating firmware problems. |
| B2001281 | A partition memory error occurred. The failed memory will no longer be used. | Restart the partition. |
| B2001282 | A problem occurred during the startup of a partition. | Go to Isolating firmware problems. |
| B2001320 | A problem occurred during the startup of a partition.
No default load source was selected. The startup will attempt to continue, but there may not be enough information to find the correct load source. |
Configure a load source for the partition. Then restart the partition. |
| B2001321 | A problem occurred during the startup of a partition. | Verify that the correct slot is specified for the load source. Then restart the partition. |
| B2001322 | In the partition startup, code failed during a check of the load source path. | Verify that the path for the load source is specified correctly. Then restart the partition. |
| B2002048 | A problem occurred during a partition Main Storage Dump. A mainstore dump startup did not complete due to a copy error. | Go to Isolating firmware problems. |
| B2002054 | A problem occurred during a partition Main Storage Dump. A mainstore dump IPL did not complete due to a configuration mismatch. | Go to Isolating firmware problems. |
| B2002058 | A problem occurred during a partition Main Storage Dump. A mainstore dump startup did not complete due to a copy error. | Go to Isolating firmware problems. |
| B2002210 | Informational system log entry only. | No corrective action is required. |
| B2002220 | Informational system log entry only. | No corrective action is required. |
| B2002250 | During the startup of a partition, an attempt to toggle the power state of a slot has failed. | Check for server firmware updates; then, install the updates if available. |
| B2002260 | During the startup of a partition, the partition firmware attempted an operation that failed. | Go to Isolating firmware problems. |
| B2002300 | During the startup of a partition, an attempt to toggle the power state of a slot has failed. | Check for server firmware updates; then, install the updates if available. |
| B2002310 | During the startup of a partition, the partition firmware attempted an operation that failed. | Go to Isolating firmware problems. |
| B2002320 | During the startup of a partition, the partition firmware attempted an operation that failed. | Go to Isolating firmware problems. |
| B2002425 | During the startup of a partition, the partition firmware attempted an operation that failed. | Go to Isolating firmware problems. |
| B2002426 | During the startup of a partition, the partition firmware attempted an operation that failed. | Go to Isolating firmware problems. |
| B2002475 | During the startup of a partition, a slot that was needed for the partition was either empty or the device in the slot has failed. | Check for server firmware updates; then, install the updates if available. |
| B2002485 | During the startup of a partition, the partition firmware attempted an operation that failed. | Go to Isolating firmware problems. |
| B2003000 | Informational system log entry only. | No corrective action is required. |
| B2003081 | During the startup of a partition, the startup did not complete due to a copy error. | Check for server firmware updates; then, install the updates if available. |
| B2003084 | A problem occurred during the startup of a partition.
The adapter type might not be supported. |
Verify that the adapter type is supported. |
| B2003088 | Informational system log entry only. | No corrective action is required. |
| B200308C | A problem occurred during the startup of a partition.
The adapter type cannot be determined. |
Verify that a valid I/O Load Source is tagged. |
| B2003090 | A problem occurred during the startup of a partition. | Go to Isolating firmware problems. |
| B2003110 | A problem occurred during the startup of a partition. | Go to Isolating firmware problems. |
| B2003113 | A problem occurred during the startup of a partition. | Look for B7xx xxxx errors and resolve them. |
| B2003114 | A problem occurred during the startup of a partition. | Look for other errors and resolve them. |
| B2003120 | Informational system log entry only. | No corrective action is required. |
| B2003123 | Informational system log entry only. | No corrective action is required. |
| B2003125 | During the startup of a partition, the blade server firmware could not obtain a segment of main storage within the blade server to use for managing the creation of a partition. | Check for server firmware updates; then, install the updates if available. |
| B2003128 | A problem occurred during the startup of a partition. A return code for an unexpected failure was returned when attempting to query the load source path. | Look for and resolve B700 69xx errors. |
| B2003130 | A problem occurred during the startup of a partition. | Check for server firmware updates; then, install the updates if available. |
| B2003135 | A problem occurred during the startup of a partition. | Check for server firmware updates; then, install the updates if available. |
| B2003140 | A problem occurred during the startup of a partition. This is a configuration problem in the partition. | Reconfigure the partition to include the intended load source path. |
| B2003141 | Informational system log entry only. | No corrective action is required. |
| B2003142 | Informational system log entry only. | No corrective action is required. |
| B2003143 | Informational system log entry only. | No corrective action is required. |
| B2003144 | Informational system log entry only. | No corrective action is required. |
| B2003145 | Informational system log entry only. | No corrective action is required. |
| B2003200 | Informational system log entry only. | No corrective action is required. |
| B2004158 | Informational system log entry only. | No corrective action is required. |
| B2004400 | A problem occurred during the startup of a partition. | Check for server firmware updates; then, install the updates if available. |
| B2005106 | 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. | 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. |
| B2005109 | A problem occurred during the startup of a partition. There was a partition main storage dump problem. The startup will not continue. | Go to Isolating firmware problems. |
| B2005114 | 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. | Go to Isolating firmware problems. |
| B2005115 | 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. | If the startup does not continue, look for and resolve other errors. |
| B2005117 | 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. | Use the Main Storage Dump Manager to rename or copy the current main storage dump. |
| B2005121 | 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. | 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. |
| B2005122 | Informational system log entry only. | No corrective action is required. |
| B2005123 | Informational system log entry only. | No corrective action is required. |
| B2005135 | 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. | Look for other errors and resolve them. |
| B2005137 | 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. | Look for other errors and resolve them. |
| B2005145 | 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. | Look for other errors and resolve them. |
| B2005148 | A problem occurred during the startup of a partition. An error occurred while doing a main storage dump that would have caused another main storage dump. The startup will not continue. | Go to Isolating firmware problems. |
| B2005149 | A problem occurred during the startup of a partition while doing a Firmware Assisted Dump that would have caused another Firmware Assisted Dump. | Check for server firmware updates; then, install the updates if available. |
| B200514A | A Firmware Assisted Dump did not complete due to a copy error. | Check for server firmware updates; then, install the updates if available. |
| B200542A | A Firmware Assisted Dump did not complete due to a read error. | Check for server firmware updates; then, install the updates if available. |
| B200542B | A Firmware Assisted Dump did not complete due to a copy error. | Check for server firmware updates; then, install the updates if available. |
| B200543A | A Firmware Assisted Dump did not complete due to a copy error. | Check for server firmware updates; then, install the updates if available. |
| B200543B | A Firmware Assisted Dump did not complete due to a copy error. | Check for server firmware updates; then, install the updates if available. |
| B200543C | Informational system log entry only. | No corrective action is required. |
| B200543D | A Firmware Assisted Dump did not complete due to a copy error. | Check for server firmware updates; then, install the updates if available. |
| B2006006 | During the startup of a partition, a system firmware error occurred when the partition memory was being initialized; the startup will not continue. | Go to Isolating firmware problems. |
| B200600A | A problem occurred during the startup of a partition. The partition could not reserve the memory required for IPL. | Contact IBM® support. |
| B2006012 | During the startup of a partition, the partition LID failed to completely load into the partition main storage area. | Go to Isolating firmware problems. |
| B2006015 | A problem occurred during the startup of a partition. The load source media is corrupted or not valid. | Replace the load source media. |
| B2006025 | A problem occurred during the startup of a partition. This is a problem with the load source media being corrupt or not valid. | Replace the load source media. |
| B2006027 | During the startup of a partition, a failure occurred when allocating memory for an internal object used for firmware module load operations. |
|
| B2006110 | A problem occurred during the startup of a partition. There was an error on the load source device. The startup will attempt to continue. | Look for other errors and resolve them. |
| B200690A | During the startup of a partition, an error occurred while copying open firmware into the partition load area. | Go to Isolating firmware problems. |
| B2007200 | Informational system log entry only. | No corrective action is required. |
| B2008080 | Informational system log entry only. | No corrective action is required. |
| B2008081 | During the startup of a partition, an internal firmware time-out occurred; the partition might continue to start up but it can experience problems while running. | Check for server firmware updates; then, install the updates if available. |
| B2008105 | During the startup of a partition, there was a failure loading the VPD areas of the partition; the load source media has been corrupted or is unsupported on this server. | Check for server firmware updates; then, install the updates if available. |
| B2008106 | A problem occurred during the startup of a partition. The startup will not continue. | Replace the load source media. |
| B2008107 | During the startup of a partition, there was a problem getting a segment of main storage in the blade server main storage. | Check for server firmware updates; then, install the updates if available. |
| B2008109 | During the startup of a partition, a failure occurred. The startup will not continue. |
|
| B2008111 | A problem occurred during the startup of a partition. | Check for server firmware updates; then, install the updates if available. |
| B2008112 | During the startup of a partition, a failure occurred; the startup will not continue. | Check for server firmware updates; then, install the updates if available. |
| B2008113 | During the startup of a partition, an error occurred while mapping memory for the partition startup. | Check for server firmware updates; then, install the updates if available. |
| B2008114 | During the startup of a partition, there was a failure verifying the VPD for the partition resources during startup. | Check for server firmware updates; then, install the updates if available. |
| B2008115 | During the startup of a partition, there was a low level partition-to-partition communication failure. | Check for server firmware updates; then, install the updates if available. |
| B2008117 | During the startup of a partition, the partition did not start up due to a system firmware error. | Check for server firmware updates; then, install the updates if available. |
| B2008121 | During the startup of a partition, the partition did not start up due to a system firmware error. | Go to Isolating firmware problems. |
| B2008123 | During the startup of a partition, the partition did not start up due to a system firmware error. | Go to Isolating firmware problems. |
| B2008125 | During the startup of a partition, the partition did not start up due to a system firmware error. | Go to Isolating firmware problems. |
| B2008127 | During the startup of a partition, the partition did not start up due to a system firmware error. | Go to Isolating firmware problems. |
| B2008129 | During the startup of a partition, the partition did not start up due to a system firmware error. | Go to Isolating firmware problems. |
| B200813A | There was a problem establishing a console. | Go to Isolating firmware problems. |
| B2008140 | Informational system log entry only. | No corrective action is required. |
| B2008141 | Informational system log entry only. | No corrective action is required. |
| B2008142 | Informational system log entry only. | No corrective action is required. |
| B2008143 | Informational system log entry only. | No corrective action is required. |
| B2008144 | Informational system log entry only. | No corrective action is required. |
| B2008145 | Informational system log entry only. | No corrective action is required. |
| B2008150 | System firmware detected an error. | Collect a platform dump and then go to Isolating firmware problems. |
| B2008151 | System firmware detected an error. | Use the Integrated Virtualization Manager (IVM) or management console to increase the Logical Memory Block (LMB) size, and to reduce the number of virtual devices for the partition. |
| B2008152 | No active system processors. | Verify that processor resources are assigned to the partition. |
| B2008160 | A problem occurred during the migration of a partition. | Contact IBM support. |
| B2008161 | A problem occurred during the migration of a partition. | Contact IBM support. |
| B200A100 | A partition ended abnormally; the partition could not stay running and shut itself down. |
|
| B200A101 | A partition ended abnormally; the partition could not stay running and shut itself down. |
|
| B200A140 | A lower priority partition lost a usable processor to supply it to a higher priority partition with a bad processor. | Evaluate the entire LPAR configuration. Adjust partition profiles with the new number of processors available in the system. |
| B200B07B | Informational system log entry only. | No corrective action is required. |
| B200B215 | A problem occurred after a partition ended abnormally.
There was a communications problem between this partition's service processor and the platform's service processor. |
Restart the platform. |
| B2005127 | Timeout occurred during a main store dump IPL. | There was not enough memory available for the dump to complete before the timeout occurred. Retry the main store dump IPL, or else power on the partition normally. |
| B2D03001 | Informational system log entry only. | No corrective action is required. |
| B2D03002 | Informational system log entry only. | No corrective action is required. |
| B200C1F0 | An internal system firmware error occurred during a partition shutdown or a restart. | Go to Isolating firmware problems. |
| B200D150 | A partition ended abnormally; there was a communications problem between this partition and the code that handles resource allocation. | Check for server firmware updates; then, install the updates if available. |
| B200E0AA | A problem occurred during the power off of a partition. | Go to Isolating firmware problems. |
| B200F001 | A problem occurred during the startup of a partition. An operation has timed out. | Look for other errors and resolve them. |
| B200F003 | During the startup of a partition, the partition processor(s) did not start the firmware within the time-out window. | Collect the partition dump information; then, go to Isolating firmware problems. |
| B200F004 | Informational system log entry only. | No corrective action is required. |
| B200F005 | Informational system log entry only. | No corrective action is required. |
| B200F006 | During the startup of a partition, the code load operation for the partition startup timed out. |
|
| B200F007 | During a shutdown of the partition, a time-out occurred while trying to stop a partition. | Check for server firmware updates; then, install the updates if available. |
| B200F008 | Informational system log entry only. | No corrective action is required. |
| B200F009 | Informational system log entry only. | No corrective action is required. |
| B200F00A | Informational system log entry only. | No corrective action is required. |
| B200F00B | Informational system log entry only. | No corrective action is required. |
| B200F00C | Informational system log entry only. | No corrective action is required. |
| B200F00D | Informational system log entry only. | No corrective action is required. |