Internal Data Failed error. What does it mean?

[chuckk281]

Roberto needed some help understanding an error message:

***********************

Any idea, what internal Data failed means?

Thanks.

See below.

Blade #7 Status:

                Power: On

                Current Wattage used: 294

                Health: Degraded

                Unit Identification LED: Off

                Virtual Fan: 37%

                Diagnostic Status:

                               Internal Data        Failed

                               Management Processor OK

                               I/O Configuration    OK

                               Power                OK

                               Cooling              OK

                               Device Failure       OK

                               Device Degraded      OK

                               iLO Network          OK

                               Please refer to the System Log for important information on this device

******************

Monty replied:

**********************

Internal Data failed – indicates the Field Replacement Unit (FRU) eeprom contents have been corrupted and have a checksum error.

The FRU eeproms contain factory information used by the OA to control  that component.  In the case of the server FRU eeprom – the contents include the wiring of the server blade embedded and mezz ports, critical to proper functionality.  In addition, the FRU eeprom contains information such as Part Number, Service Spare P/N, MAC or WWN addresses and other management info.

The only way to clear this error is replace that board containing the error.

**************

Comments or questions??

[Johan Guldmyr]

You don't even advise to try to reset NVRAM? I think Chuck == Monty.

[chuckk281]

Johan:

Do mean to re-write the FRU EEPROM data? As this is fartory set, you would need to get that data somehow. The somehow, I don't have a clue.

Chuck

[Johan Guldmyr]

Thanks for replying.

Maybe this differs between blade types. Don't the integrity blades have EFI "BIOS" that might help in this case.

Is this EEPROM FRU not in the same chipset as the NVRAM?

Basically what I'd wonder is why wouldn't a clear NVRAM via BIOS/System Maintenance Switch be an option?