IBM @Server pSeries 630 6E4, Руководство по обслуживанию

Страница: 261 / 651

Table 4. Firmware Error Codes. (continued)
Error Code Description Action/
Possible Failing FRU
25A8 0xxx Description: NVRAM problems
Action: Errors reported against NVRAM can be caused by low battery voltage and (more rarely)
power outages that occur during normal system usage. With the exception of the 25A80000 error,
these errors are warnings that the NVRAM data content had to be re-established and do not
require any FRU replacement unless the error is persistent. When one of these errors occurs,
any system customization (for example, boot device list) information has been lost, the system
may need to be reconfigured.
If the error is persistent, replace CEC backplane
Location: U0.1-P1
25A8 0000 Initialization failed, device test failed Refer to Action under error code 25A80xxx.
25A8 0100 NVRAM data validation check failed. Turn off, then turn on system unit and retry the
operation before replacing any system
component.
Refer to Action under error code 25A80xxx.
25A8 0201 Unable to expand target partition - saving
configuration variable.
Refer to Action under error code 25A80xxx.
25A8 0202 Unable to expand target partition - writing error
log entry.
Refer to Action under error code 25A80xxx.
25A8 0203 Unable to expand target partition - writing VPD
data.
Refer to Action under error code 25A80xxx.
25A8 0210 Setenv/$Setenv parameter error - name
contains a null character.
Refer to Action under error code 25A80xxx.
25A8 0211 Setenv/$Setenv parameter error - value
contains a null character.
Refer to Action under error code 25A80xxx.
25A8 0215 NVRAM RIO-USR-select variable not found.
1. Check for platform firmware updates. Apply
if available.
2. Call service support.
25A8 0998 Description: NVRAMRC script evaluation error - command line execution error
Action: Execution of a command line within the nvram configuration variable “nvramrc” (script)
resulted in a “throw” being executed. This script can be modified by the system firmware SMS
utilities, the operating system, PCI adapter ROM code or utility, or an operator (via the open
firmware script editing command
nvedit ). It may not be possible to resolve the problem without a
detailed analysis of the nvram script, the current system configuration, and device tree contents.
1. The problem can be caused by a SCSI adapter, whose SCSI bus ID has been changed from
the default setting, no longer appearing in the system. This can be caused either by removing
a SCSI adapter, or a problem with a SCSI adapter.
a. Select option 5, Change SCSI Settings , on the SMS main menu. Then on the SCSI
utilities menu, select option 2, Change SCSI Id .
1) Verify the list of SCSI controllers/adapters. If the list is not correct, suspect a problem
with the adapter(s) installed but not listed.
2) Select one of the adapters listed and enter the SCSI id that is currently displayed for
that adapter, then exit from this menu. This causes the information in NVRAM to be
updated.
3) Restart the system.
b. If the problem persists, boot the operating system and verify the SCSI bus IDs of any
installed/available SCSI controllers (change as necessary), and restart the system.
2. Contact support support for further assistance.
Chapter 5. Error Code to FRU Index
241