HPE 9000 and HPE e3000 Servers
cancel
Showing results for 
Search instead for 
Did you mean: 

trouble booting rp7400

 
Paul Dea
Occasional Visitor

trouble booting rp7400

Hi,

I been trying to get an rp7400 to boot again. For some reason, it just stopped.

I pulled out all the PCI cards and only have CPUs 1,3 and memory installed.

I cant get it to boot even to BCH.

Can someone tell me what the below errors during bootup mean??



***** EARLY BOOT VFP : SYSTEM ALERT *****
SYSTEM NAME: uninitialized
DATE: 01/22/1970 TIME: 03:53:20
ALERT LEVEL: 7 = reserved

REASON FOR ALERT
SOURCE: 0 = unknown, no source stated
SOURCE DETAIL: 0 = unknown, no source stated SOURCE ID: FF
PROBLEM DETAIL: 0 = no problem detail

LEDs: RUN ATTENTION FAULT REMOTE POWER
FLASH FLASH OFF OFF ON

0x0000187000FF6292 000000FF FF800000 - type 0 = Data Field Unused
0x5800187000FF6292 00004600 16033514 - type 11 = Timestamp 01/22/1970 03:53:20
A/a: ack read of this entry - Q/q: quit Virtual Front Panel Display
Anything else redisplay the log entry
->Choice:a
I/O machine check 8631
I/O machine check 8633
I/O machine check 8633
I/O machine check 8631
unknown, no source stated machine check 641
unknown, no source stated machine check 640
I/O machine check 8630
I/O machine check 8633
I/O machine check 8634
I/O machine check 8634
I/O machine check 8634
I/O machine check 8634

***** EARLY BOOT VFP : SYSTEM ALERT *****
SYSTEM NAME: uninitialized
DATE: 01/22/1970 TIME: 03:54:13
ALERT LEVEL: 6 = Boot possible, pending failure - action required

REASON FOR ALERT
SOURCE: 8 = I/O
SOURCE DETAIL: 5 = I/O device adapter SOURCE ID: FF
PROBLEM DETAIL: 6 = configuration error

LEDs: RUN ATTENTION FAULT REMOTE POWER
OFF FLASH FLASH OFF ON

0x2000106685FF2384 000000FF FF0DFF85 - type 4 = Physical Location
0x5800106685FF2384 00004600 1603360D - type 11 = Timestamp 01/22/1970 03:54:13
A/a: ack read of this entry - Q/q: quit Virtual Front Panel Display
Anything else redisplay the log entry
->Choice:Timeout!
*****************************************

***** EARLY BOOT VFP : SYSTEM ALERT *****
SYSTEM NAME: uninitialized
DATE: 01/22/1970 TIME: 03:54:14
ALERT LEVEL: 6 = Boot possible, pending failure - action required

REASON FOR ALERT
SOURCE: 8 = I/O
SOURCE DETAIL: 5 = I/O device adapter SOURCE ID: FF
PROBLEM DETAIL: 6 = configuration error

LEDs: RUN ATTENTION FAULT REMOTE POWER
OFF FLASH FLASH OFF ON

0x2000106685FF2384 000000FF FF0DFF85 - type 4 = Physical Location
0x5800106685FF2384 00004600 1603360E - type 11 = Timestamp 01/22/1970 03:54:14
A/a: ack read of this entry - Q/q: quit Virtual Front Panel Display
Anything else redisplay the log entry
->Choice:a
*****************************************

***** EARLY BOOT VFP : SYSTEM ALERT *****
SYSTEM NAME: uninitialized
DATE: 01/22/1970 TIME: 03:54:14
ALERT LEVEL: 6 = Boot possible, pending failure - action required

REASON FOR ALERT
SOURCE: 8 = I/O
SOURCE DETAIL: 5 = I/O device adapter SOURCE ID: FF
PROBLEM DETAIL: 6 = configuration error

LEDs: RUN ATTENTION FAULT REMOTE POWER
OFF FLASH FLASH OFF ON

0x2000106685FF2384 FFFFFFFF FFFFFFFF - type 4 = Physical Location
0x5800106685FF2384 00004600 1603360E - type 11 = Timestamp 01/22/1970 03:54:14
A/a: ack read of this entry - Q/q: quit Virtual Front Panel Display
Anything else redisplay the log entry
->Choice:a
*****************************************

***** EARLY BOOT VFP : SYSTEM ALERT *****
SYSTEM NAME: uninitialized
DATE: 01/22/1970 TIME: 03:54:14
ALERT LEVEL: 6 = Boot possible, pending failure - action required

REASON FOR ALERT
SOURCE: 8 = I/O
SOURCE DETAIL: 5 = I/O device adapter SOURCE ID: FF
PROBLEM DETAIL: 6 = configuration error

LEDs: RUN ATTENTION FAULT REMOTE POWER
OFF FLASH FLASH OFF ON

0x2000106685FF2384 000000FF FF0DFF85 - type 4 = Physical Location
0x5800106685FF2384 00004600 1603360E - type 11 = Timestamp 01/22/1970 03:54:14
A/a: ack read of this entry - Q/q: quit Virtual Front Panel Display
Anything else redisplay the log entry
->Choice:a
*****************************************
I/O machine check 8620
I/O machine check 8620
6 REPLIES 6
Sameer_Nirmal
Honored Contributor

Re: trouble booting rp7400

Hi,

Alert 7 and I/O machine check indicates hardware problem. It looks like the "SOURCE DETAIL: 5 = I/O device adapter " is nothing but a SCSI I/O adapter. Saying that either the onboard SCSI I/O adapter ( a part of the integrated multi-funcation core I/O ) or the device connected to it is at fault.

Do you able to access the GSP ?
If yes, check the sl and cl logs for any messages.

I would take out internal SCSI disks and a SCSI connection if any to the 68-pin VHDCI connector and check if system reach to BCH. If no success, the system board may need to be replaced.

I would raise a h/w call to HP and provides them all these details and get the hardware fixed.
Mark Nieuwboer
Esteemed Contributor

Re: trouble booting rp7400

Hi Paul,

The best way is to make a system call with HP. From what i see it is the system backplane.

grtz. Mark
timmy b.
Honored Contributor

Re: trouble booting rp7400

I agree with the previous post, you'll need to get HP involved to properly decode the error. But, going by what you've said, it sounds like you may have a problem with one of your pci-backplanes. In the N class (rp7400) there are two of these.

Good Luck - Tim
There are 10 kinds of people in this world: Those who understand Binary, and those who don't.
Paul Dea
Occasional Visitor

Re: trouble booting rp7400

All,

thanks for the replies. below is the SL log. There was no CL log. Is there anyway to disable the PCI Backplane, or the backplane check so the machine can boot?

Log Entry # 0 :
SYSTEM NAME: uninitialized
DATE: 01/22/1970 TIME: 05:20:03
ALERT LEVEL: 6 = Boot possible, pending failure - action required

SOURCE: 4 = power
SOURCE DETAIL: 4 = high voltage DC power SOURCE ID: 0
PROBLEM DETAIL: A = failed

CALLER ACTIVITY: 4 = monitor STATUS: F
CALLER SUBACTIVITY: 04 = low voltage power supply
REPORTING ENTITY TYPE: 2 = power monitor REPORTING ENTITY ID: 00

0x0020086A4400404F 00000000 00000000 type 0 = Data Field Unused
0x5820086A4400404F 00004600 16051403 type 11 = Timestamp 01/22/1970 05:20:03
Type CR for next entry, Q CR to escape.



Log Entry # 1 :
SYSTEM NAME: uninitialized
DATE: 01/22/1970 TIME: 05:14:29
ALERT LEVEL: 6 = Boot possible, pending failure - action required

SOURCE: 8 = I/O
SOURCE DETAIL: 5 = I/O device adapter SOURCE ID: FF
PROBLEM DETAIL: 6 = configuration error

CALLER ACTIVITY: 2 = config STATUS: 4
CALLER SUBACTIVITY: 38 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 01

0x2000106685FF2384 000000FF FF0DFF85 type 4 = Physical Location
0x5800106685FF2384 00004600 16050E1D type 11 = Timestamp 01/22/1970 05:14:29
Type CR for next entry, - CR for previous entry, Q CR to escape.



Log Entry # 2 :
SYSTEM NAME: uninitialized
DATE: 01/22/1970 TIME: 05:14:29
ALERT LEVEL: 6 = Boot possible, pending failure - action required

SOURCE: 8 = I/O
SOURCE DETAIL: 5 = I/O device adapter SOURCE ID: FF
PROBLEM DETAIL: 6 = configuration error

CALLER ACTIVITY: 2 = config STATUS: 4
CALLER SUBACTIVITY: 38 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 01

0x2000106685FF2384 FFFFFFFF FFFFFFFF type 4 = Physical Location
0x5800106685FF2384 00004600 16050E1D type 11 = Timestamp 01/22/1970 05:14:29
Type CR for next entry, - CR for previous entry, Q CR to escape.



Log Entry # 3 :
SYSTEM NAME: uninitialized
DATE: 01/22/1970 TIME: 05:14:29
ALERT LEVEL: 6 = Boot possible, pending failure - action required

SOURCE: 8 = I/O
SOURCE DETAIL: 5 = I/O device adapter SOURCE ID: FF
PROBLEM DETAIL: 6 = configuration error

CALLER ACTIVITY: 2 = config STATUS: 4
CALLER SUBACTIVITY: 38 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 01

0x2000106685FF2384 000000FF FF0DFF85 type 4 = Physical Location
0x5800106685FF2384 00004600 16050E1D type 11 = Timestamp 01/22/1970 05:14:29
Type CR for next entry, - CR for previous entry, Q CR to escape.



Log Entry # 4 :
SYSTEM NAME: uninitialized
DATE: 01/22/1970 TIME: 05:14:29
ALERT LEVEL: 6 = Boot possible, pending failure - action required

SOURCE: 8 = I/O
SOURCE DETAIL: 5 = I/O device adapter SOURCE ID: FF
PROBLEM DETAIL: 6 = configuration error

CALLER ACTIVITY: 2 = config STATUS: 4
CALLER SUBACTIVITY: 38 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 01

0x2000106685FF2384 000000FF FF0DFF85 type 4 = Physical Location
0x5800106685FF2384 00004600 16050E1D type 11 = Timestamp 01/22/1970 05:14:29
Type CR for next entry, - CR for previous entry, Q CR to escape.



Log Entry # 5 :
SYSTEM NAME: uninitialized
DATE: 01/22/1970 TIME: 05:13:36
ALERT LEVEL: 7 = reserved

SOURCE: 0 = unknown, no source stated
SOURCE DETAIL: 0 = unknown, no source stated SOURCE ID: FF
PROBLEM DETAIL: 0 = no problem detail

CALLER ACTIVITY: 6 = machine check STATUS: 2
CALLER SUBACTIVITY: 29 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 01

0x0000187000FF6292 000000FF FF800000 type 0 = Data Field Unused
0x5800187000FF6292 00004600 16050D24 type 11 = Timestamp 01/22/1970 05:13:36
Type CR for next entry, - CR for previous entry, Q CR to escape.



Log Entry # 6 :
SYSTEM NAME: uninitialized
DATE: 01/22/1970 TIME: 05:10:14
ALERT LEVEL: 6 = Boot possible, pending failure - action required

SOURCE: 4 = power
SOURCE DETAIL: 4 = high voltage DC power SOURCE ID: 0
PROBLEM DETAIL: A = failed

CALLER ACTIVITY: 4 = monitor STATUS: F
CALLER SUBACTIVITY: 04 = low voltage power supply
REPORTING ENTITY TYPE: 2 = power monitor REPORTING ENTITY ID: 00

0x0020086A4400404F 00000000 00000000 type 0 = Data Field Unused
0x5820086A4400404F 00004600 16050A0E type 11 = Timestamp 01/22/1970 05:10:14
Type CR for next entry, - CR for previous entry, Q CR to escape.



Log Entry # 7 :
SYSTEM NAME: uninitialized
DATE: 01/22/1970 TIME: 04:57:42
ALERT LEVEL: 6 = Boot possible, pending failure - action required

SOURCE: 8 = I/O
SOURCE DETAIL: 5 = I/O device adapter SOURCE ID: FF
PROBLEM DETAIL: 6 = configuration error

CALLER ACTIVITY: 2 = config STATUS: 4
CALLER SUBACTIVITY: 38 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 01

0x2000106685FF2384 000000FF FF0DFF85 type 4 = Physical Location
0x5800106685FF2384 00004600 1604392A type 11 = Timestamp 01/22/1970 04:57:42
Type CR for next entry, - CR for previous entry, Q CR to escape.



Log Entry # 8 :
SYSTEM NAME: uninitialized
DATE: 01/22/1970 TIME: 04:57:41
ALERT LEVEL: 6 = Boot possible, pending failure - action required

SOURCE: 8 = I/O
SOURCE DETAIL: 5 = I/O device adapter SOURCE ID: FF
PROBLEM DETAIL: 6 = configuration error

CALLER ACTIVITY: 2 = config STATUS: 4
CALLER SUBACTIVITY: 38 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 01

0x2000106685FF2384 FFFFFFFF FFFFFFFF type 4 = Physical Location
0x5800106685FF2384 00004600 16043929 type 11 = Timestamp 01/22/1970 04:57:41
Type CR for next entry, - CR for previous entry, Q CR to escape.



Log Entry # 9 :
SYSTEM NAME: uninitialized
DATE: 01/22/1970 TIME: 04:57:41
ALERT LEVEL: 6 = Boot possible, pending failure - action required

SOURCE: 8 = I/O
SOURCE DETAIL: 5 = I/O device adapter SOURCE ID: FF
PROBLEM DETAIL: 6 = configuration error

CALLER ACTIVITY: 2 = config STATUS: 4
CALLER SUBACTIVITY: 38 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 01

0x2000106685FF2384 000000FF FF0DFF85 type 4 = Physical Location
0x5800106685FF2384 00004600 16043929 type 11 = Timestamp 01/22/1970 04:57:41
Type CR for next entry, - CR for previous entry, Q CR to escape.

Mark Nieuwboer
Esteemed Contributor

Re: trouble booting rp7400

Hi Paul,

If the backplane is broken you can't boot.
The backplane is the motherboard of the system.
From what i can see from this it is the most probebly the backplane. Make a hardware call with HP to sove this problem.

grtz. Mark
Sameer_Nirmal
Honored Contributor

Re: trouble booting rp7400

As per the SL log, entries are logged for power supply 0 failure besides the I/O device adapter error entries posted earlier.
You need to check physically PS 0 (LEDs , fans)status.

As I said before, there is apprently hardware problem which is hampering the power on self tests of the server and thus not going to BCH. The I/O adpater reported is integrated on the system board and is not removable and can't be bypassed.

Saying that, you need to get the hardware
(apprently system board and power supply 0) fixed by logging a h/w call to HP.