Integrity Servers
cancel
Showing results for 
Search instead for 
Did you mean: 

rx1620 not booting EFI or giving CO output

 
npjames
Occasional Visitor

rx1620 not booting EFI or giving CO output

Hello,

I've bought a second hand rx1620 which seems to have some hardware faults. When powered up, the System LED flashes red and the LED 2 is a solid red. This seems to indicate a firmware fault.

I can console in and get to the MP:CM>. So far the SYSREV gives this;
Current firmware revisions

MP FW : E.03.30
BMC FW : 04.01
EFI FW : 05.48
System FW : 04.27

A look at the system event logs gives some Type 2 errors with alert levels of 2, 3 and 7 as below;

# Location|Alert| Encoded Field | Data Field | Keyword / Timestamp
-------------------------------------------------------------------------------
0 BMC 2 0x204BFCAA75020010 FFFF006F04140300 Type-02 146f00 1339136
26 May 2010 04:58:29
1 BMC 2 0x204BFCAA76020020 0401A37004120300 Type-02 127003 1208323
26 May 2010 04:58:30
2 BMC 2 0x204BFCAA79020030 FFFF018302050300 Type-02 058301 361217
26 May 2010 04:58:33
3 BMC *3 0x204BFCAA96020040 FFFF010302050300 Type-02 050301 328449
26 May 2010 04:59:02
4 BMC 2 0x204BFCAACB020050 FFFF018302050300 Type-02 058301 361217
26 May 2010 04:59:55
5 BMC *3 0x204BFCAACC020060 FFFF010302050300 Type-02 050301 328449
26 May 2010 04:59:56
6 BMC *7 0x204BFCAAF0020070 FFFF036F00070300 Type-02 076f03 487171
26 May 2010 05:00:32
7 BMC *7 0x204BFCABF9020080 020EA87002120300 Type-02 127008 1208328
26 May 2010 05:04:57
8 BMC 2 0x204BFCABF9020090 020EA37002120300 Type-02 127003 1208323
26 May 2010 05:04:57
9 BMC 2 0x204BFCB0A30200A0 FFFF006F04140300 Type-02 146f00 1339136
26 May 2010 05:24:51
10 BMC 2 0x204BFCB0A40200B0 0401A37004120300 Type-02 127003 1208323
26 May 2010 05:24:52
11 BMC 2 0x204BFCB0A80200C0 FFFF006F04140300 Type-02 146f00 1339136
26 May 2010 05:24:56
12 BMC 2 0x204BFCB0A80200D0 040EA37004120300 Type-02 127003 1208323
26 May 2010 05:24:56
13 BMC 2 0x204BFCB1AB0200E0 FFFF006F04140300 Type-02 146f00 1339136
26 May 2010 05:29:15
14 BMC 2 0x204BFCB1AB0200F0 0401A37004120300 Type-02 127003 1208323
26 May 2010 05:29:15
15 BMC 2 0x204BFCB1BA020100 FFFF018302050300 Type-02 058301 361217
26 May 2010 05:29:30
16 BMC *7 0x204BFCB226020110 FFFF036F00070300 Type-02 076f03 487171
26 May 2010 05:31:18
17 BMC 2 0x204BFCB5B4020120 FFFF006F04140300 Type-02 146f00 1339136
26 May 2010 05:46:28
18 BMC 2 0x2000000001020130 0150A17000120300 Type-02 127001 1208321
00:00:01
19 MP 0 2 0x5E800A7A00E00140 0000000000000000 MP_SELFTEST_RESULT
00:00:13
20 BMC 2 0x204BFCB6FE020160 FFFF0103FDC00300 Type-02 c00301 12583681
26 May 2010 05:51:58
21 BMC 2 0x204BFCB91F020170 FFFF006F04140300 Type-02 146f00 1339136
26 May 2010 06:01:03
22 BMC 2 0x204BFCB91F020180 0401A37004120300 Type-02 127003 1208323
26 May 2010 06:01:03
23 BMC 2 0x204BFCB923020190 FFFF0108F10D0300 Type-02 0d0801 854017
26 May 2010 06:01:07
24 BMC 2 0x204BFCB9230201A0 FFFF0108F20D0300 Type-02 0d0801 854017
26 May 2010 06:01:07
25 BMC 2 0x204BFCB9230201B0 FFFF006FFA220300 Type-02 226f00 2256640
26 May 2010 06:01:07
26 BMC 2 0x204BFCB92E0201C0 0183A37000120300 Type-02 127003 1208323
26 May 2010 06:01:18
27 BMC *7 0x204BFCB99A0201D0 FFFF036F00070300 Type-02 076f03 487171
26 May 2010 06:03:06

Is anyone able to identify what may be missing or at fault here?

Thanks in advance,

Nick
7 REPLIES 7
Michal Kapalka (mikap)
Honored Contributor

Re: rx1620 not booting EFI or giving CO output

hi,

if you go to event log use "t" to switch the messages in to text mode instead of hexa codes.


===> example :


MP MAIN MENU:

CO: Console
VFP: Virtual Front Panel
CM: Command Menu
CL: Console Log
SL: Show Event Logs
HE: Main Help Menu
X: Exit Connection

[sms-mp] MP> sl


Event Log Viewer Menu:

Log Name Entries % Full Latest Timestamped Entry
---------------------------------------------------------------------------
E - System Event 271 31 % 30 Mar 2010 08:30:28
F - Forward Progress 4000 100 %
B - Current Boot 77 25 %
P - Previous Boot 77 25 %
C - Clear All Logs
L - Live Events

Enter menu item or [Ctrl-B] to Quit: e


Log Name Entries % Full Latest Timestamped Entry
---------------------------------------------------------------------------
E - System Event 271 31 % 30 Mar 2010 08:30:28


Event Log Navigation Help:

+ View next block (forward in time, e.g. from 3 to 4)
- View previous block (backward in time, e.g. from 3 to 2)
Continue to the next or previous block
D Dump the entire log
F First entry
L Last entry
J Jump to entry number
H View mode configuration - Hex
K View mode configuration - Keyword
T View mode configuration - Text
A Alert Level Filter options
U Alert Level Unfiltered
? Display this Help menu
Q Quit and return to the Event Log Viewer Menu
Ctrl-B Exit command, and return to the MP Main Menu


MP:SL (+,-,,D, F, L, J, H, K, T, A, U, ? for Help, Q or Ctrl-B to Quit) >


# Location|Alert| Encoded Field | Data Field | Keyword / Timestamp
-------------------------------------------------------------------------------
270 OSA 2 0x214BB1B6A4021400 FF0F066F001F0300 Type-02 1f6f06 2060038
30 Mar 2010 08:30:28
269 SFW 0 1 0x5480006300E013E0 0000000000000000 BOOT_START
30 Mar 2010 08:28:27
268 SFW 2 0xC14BB1B62A0213D0 FFFF000A001D0300 Type-02 1d0a00 1903104
30 Mar 2010 08:28:26
267 BMC 2 0x204BB1B6280213C0 FFFF027000120300 Type-02 127002 1208322
30 Mar 2010 08:28:24
266 OSA 2 0x214B2896FE0213B0 FF0F066F001F0300 Type-02 1f6f06 2060038
16 Dec 2009 08:14:54
265 SFW 0 1 0x5480006300E01390 0000000000000000 BOOT_START
16 Dec 2009 08:12:53
264 SFW 2 0xC14B289685021380 FFFF000A001D0300 Type-02 1d0a00 1903104
16 Dec 2009 08:12:53
263 BMC 2 0x204B289683021370 FFFF027000120300 Type-02 127002 1208322
16 Dec 2009 08:12:51
262 OSA 2 0x214B2895CD021360 FF0F066F001F0300 Type-02 1f6f06 2060038
16 Dec 2009 08:09:49


MP:SL (+,-,,D, F, L, J, H, K, T, A, U, ? for Help, Q or Ctrl-B to Quit) >t
MP:SL (+,-,,D, F, L, J, H, K, T, A, U, ? for Help, Q or Ctrl-B to Quit) >l



Log Entry 270: 30 Mar 2010 08:30:28
Alert Level 2: Informational
Keyword: Type-02 1f6f06 2060038
OS Boot complete.
Logged by: OS Software Agent;
Sensor: OS Boot
Data1: boot completed-boot device not specified
0x214BB1B6A4021400 FF0F066F001F0300


Log Entry 269: 30 Mar 2010 08:28:27
Alert Level 1: Major Forward Progress
Keyword: BOOT_START
CPU starting boot
Logged by: System Firmware 0
Data: Major change in system state
0x5480006300E013E0 0000000000000000

mikap
npjames
Occasional Visitor

Re: rx1620 not booting EFI or giving CO output

Already a great help thank you, as the LED's say, it does indeed seem to be a firmware issue;

Log Entry 38: 26 May 2010 06:13:18
Alert Level 7: Fatal
Keyword: Type-02 076f03 487171
No events were received from system firmware
Logged by: Baseboard Management Controller;
Sensor: Processor
Data1: FRB2/Hang in POST failure
0x204BFCBBFE020290 FFFF036F00070300

I've attempted the firmware upgrade a couple of times but am not sure if I've done it right. The results have been either not logging in to the FTP server correctly or then not finding the correct code.

This was attempted using the following two files;

PF_CONYXSYS0427EFI
PF_CEVERMPE0315

As before though, from reading up, it seems like i'm already running current firmware.
Michal Kapalka (mikap)
Honored Contributor

Re: rx1620 not booting EFI or giving CO output

hi,

go to HP site and go to driver download section and select your server them download a offline cd for the HP-UX OS, and try to boot from he cd and flash the firmware, if you are running HP-UX the firmware is different such a Windows.

mikap
Torsten.
Acclaimed Contributor

Re: rx1620 not booting EFI or giving CO output

Looks like a failed CPU.
As long as you cannot reach EFI you cannot do any firmware update.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
KSamuel
Visitor

Re: rx1620 not booting EFI or giving CO output

-Put an older CPU in your server

-Upgrade your server firmware

-Put back your CPU

 

BTW your CPU work fine, your motherboard work fine

 

Just upgrade your firmware

 

 

:)

 

Torsten.
Acclaimed Contributor

Re: rx1620 not booting EFI or giving CO output

If the problem really still exist - 5 years later?


Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Bill_t
Visitor

Re: rx1620 not booting EFI or giving CO output

 

Nick,

 

I work for HP with the integrity Team.  I have reviewed you post and have determined the following:

 

It appears all of the FW is up to date at this time.

 

Please be aware the logs provided is reporting the dates of May 2010.

 

The BMC alert levels of 2 are informational and do not require any action.

 

3 BMC *3 0x204BFCAA96020040 FFFF010302050300 Type-02 050301 328449
26 May 2010 04:59:02

 

This Alert 3 decodes to the following:

IPMI Event Code: 204BFCAA96020040 FFFF010302050300

Timestamp (GMT) = Wed May 26 04:59:02 2010

Generator = Baseboard Management Controller

Alert Level = 3 - Warning or non-critical

Sensor

Number Triplet Data 2 Data 3

------ -------- ------ ------

02 05:03:01 FF FF

Decoding as system type: Nemesis

Sensor Number : 02 - Chassis open

Sensor Type : 05 = Chassis Intrusion

Event type : Assertion event : Discrete – assertion

Keyword = CHASSIS_DOOR_IS_OPEN

The server has detected that the chassis door or other access panel is not securely closed.

 

5 BMC *3 0x204BFCAACC020060 FFFF010302050300 Type-02 050301 328449
26 May 2010 04:59:56

 

IPMI Event Code: 204BFCAACC020060 FFFF010302050300

Timestamp (GMT) = Wed May 26 04:59:56 2010

Generator = Baseboard Management Controller

Alert Level = 3 - Warning or non-critical

Sensor

Number Triplet Data 2 Data 3

------ -------- ------ ------

02 05:03:01 FF FF

Decoding as system type: Nemesis

Sensor Number : 02 - Chassis open

Sensor Type : 05 = Chassis Intrusion

Event type : Assertion event : Discrete – assertion

Keyword = CHASSIS_DOOR_IS_OPEN

The server has detected that the chassis door or other access panel is not securely closed.

 

6 BMC *7 0x204BFCAAF0020070 FFFF036F00070300 Type-02 076f03 487171
26 May 2010 05:00:32

 

IPMI Event Code: 204BFCAAF0020070 FFFF036F00070300 

Timestamp (GMT) = Wed May 26 05:00:32 2010

Generator = Baseboard Management Controller

Alert Level = 7 - Fatal

Sensor

Number Triplet Data 2 Data 3

------ -------- ------ ------

00 07:6F:03 FF FF

Decoding as system type: Nemesis

Sensor Number : 00 - Various, refer to manual

Sensor Type : 07 = Processor

Event type : Assertion event : Sensor-specific assertion event

Keyword = BOOT_NOT_DETECTED

FRB2 - Hang in Power On Self-Test failure (used to detect

the system hanging during power on self-test, usually the hang

is believed to be due or related to a processor failure)

 

The BMC starts a timer when the system is reset. If the

system firmware does not log an event within 120 seconds

the BMC considers it dead and logs an FRB2 event. On

xpeak it also turns on the diag leds if there is no MP

installed.

 

General recommendations -

* Check the processors for bent pins.

* Check the processor socket cam is locked and the processor is seated correctly.

* Reduce the system to one processor configuration (must be installed in cpu 0 socket).

* Try several different processors in this one processor configuration.

* If each processor produces the same "FRB2 hang", replace the FRU with the processor sockets.

 

 

I work for HP
A quick resolution to technical issues for your HP Enterprise products is just a click away HP Support Center Knowledge-base
See Self Help Post for more details