Sun SPARC(R) Enterprise M3000/M4000/M5000/M8000/M9000 (OPL) Servers: XSCF Reports Bad Data CRC Error at Console After Power Cycle and Loops uboot

Asset ID:	1-72-1993872.1
Update Date:	2017-04-27
Keywords:

Solution Type Problem Resolution Sure

Solution 1993872.1 : Sun SPARC(R) Enterprise M3000/M4000/M5000/M8000/M9000 (OPL) Servers: XSCF Reports Bad Data CRC Error at Console After Power Cycle and Loops uboot

Applies to:

Sun SPARC Enterprise M9000-64 Server - Version All Versions and later
Sun SPARC Enterprise M5000 Server - Version All Versions and later
Sun SPARC Enterprise M4000 Server - Version All Versions and later
Sun SPARC Enterprise M3000 Server - Version All Versions and later
Sun SPARC Enterprise M8000 Server - Version All Versions and later
Information in this document applies to any platform.

Symptoms

SPARC MX000 XSCF cannot boot up

During the boot up of the eXtended System Control Facility, the following or similar can be seen:

XSCF uboot 01080000 (Sep 26 2008 - 09:31:29)

SCF board boot factor = a080
memory test ..
Memory compare test
................finish
DDR Real size: 256 MB
DDR: 224 MB

## Booting image at ff800000 ...
Image Name: XSCF kernel 01080001 2.6.11.12-s
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 1456856 Bytes = 1.4 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
## Loading RAMDisk Image at ff980000 ...
Image Name: XSCF rootfs 01080004 ,2009/01/08
Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
Data Size: 5454338 Bytes = 5.2 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... Bad Data CRC <------ Notice that the xscf uboot loops after this.
XSCF uboot 01080000 (Sep 26 2008 - 09:31:29)

Changes

These errors are generally reported after a power cycle, during XSCF booting.

Cause

The XSCF is experiencing checksum errors this will prevent the XSCF to come up properly

Solution

Please contact your Oracle Support Center and log a service request in order to get assistance to replace the faulty XSCF.

For the M3000, the MBU needs replacement. No system operation is possible until the MBU containing the XSCF is replaced.

For the M4000/M5000, the XSCF needs replacement. No system operation is possible until the XSCF is replaced.

For the M8000/M9000, the indicted XSCF needs replacement. Continue operation on the other XSCF. XSCF redundancy is compromized until the XSCF is replaced.

To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in an appropriate
My Oracle Support Community - Oracle Sun Technologies Community.

Attachments

This solution has no attachment