Booting problem - A class HP 3000 (382 Views)
Reply
Frequent Advisor
j kubler
Posts: 130
Registered: ‎11-03-2003
Message 1 of 2 (382 Views)
Accepted Solution

Booting problem - A class HP 3000

I had the following upon ctrl-A and ctrl-B restart:

Trying Primary Boot Path
------------------------
Booting...
Failed to initialize.

ENTRY_INIT
Status = -4

00000000 FFFFFFFC 00000000 00000001 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 0000001D 00000000 00000000 00000000 00000000
00000000 454E4841 00000000 00000000 00000000 00000000 00000000 454E4841
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000002 00000000 00000004 00000000 00000040 00000000 00000084

Failed to initialize.


Trying Alternate Boot Path
--------------------------
************* SYSTEM ALERT **************
SYSTEM NAME: U
DATE: 09/08/2006 TIME: 14:11:06
ALERT LEVEL: 6 = Boot possible, pending failure - action required

REASON FOR ALERT
SOURCE: 8 = I/O
SOURCE DETAIL: 6 = disk SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail

LEDs: RUN ATTENTION FAULT REMOTE POWER
FLASH OFF ON OFF ON
LED State: Boot Failed. Running non-OS code.
Check Chassis and Console Logs for error messages.

0x0000006086002370 00000000 00000000 - type 0 = Data Field Unused
0x5800086086002370 00006A08 080E0B06 - type 11 = Timestamp 09/08/2006 14:11:06
A: ack read of this entry - X: Disable all future alert messages
Anything else skip redisplay the log entry
->Choice:Timeout!
*****************************************

************* SYSTEM ALERT **************
SYSTEM NAME: U
DATE: 09/08/2006 TIME: 14:12:05
ALERT LEVEL: 6 = Boot possible, pending failure - action required

REASON FOR ALERT
SOURCE: 8 = I/O
SOURCE DETAIL: 6 = disk SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail

LEDs: RUN ATTENTION FAULT REMOTE POWER
FLASH FLASH ON OFF ON
LED State: Boot Failed. Running non-OS code. Non-critical error detected.
Check Chassis and Console Logs for error messages.

0x0000006086002350 00000000 00000000 - type 0 = Data Field Unused
0x5800086086002350 00006A08 080E0C05 - type 11 = Timestamp 09/08/2006 14:12:05
A: ack read of this entry - X: Disable all future alert messages
Anything else skip redisplay the log entry
->Choice:A
*****************************************

************* SYSTEM ALERT **************
SYSTEM NAME: U
DATE: 09/08/2006 TIME: 14:12:05
ALERT LEVEL: 15 = Fatal hardware or configuration problem prevents operation

REASON FOR ALERT
SOURCE: 8 = I/O
SOURCE DETAIL: 6 = disk SOURCE ID: 0
PROBLEM DETAIL: 3 = functional failure

LEDs: RUN ATTENTION FAULT REMOTE POWER
FLASH FLASH ON OFF ON
LED State: Boot Failed. Running non-OS code. Non-critical error detected.
Check Chassis and Console Logs for error messages.

0x000000F386001480 00000000 00000000 - type 0 = Data Field Unused
0x580008F386001480 00006A08 080E0C05 - type 11 = Timestamp 09/08/2006 14:12:05
A: ack read of this entry - X: Disable all future alert messages
Anything else skip redisplay the log entry
->Choice:A
*****************************************

Powered off and the system came up.
Any suggestions for steps to check it out?
Thanks,
Jeff Kubler
Please use plain text.
Honored Contributor
Kwan Fong, Emile
Posts: 1,162
Registered: ‎07-10-2000
Message 2 of 2 (382 Views)

Re: Booting problem - A class HP 3000

Hello Jeff,

You are getting error "fail to initialize entry_init status -4" when booting from the primary boot path? It could be 2 cuases:

1) The PDC cannot locate system disc on ldev#1 (possible bad SCSI cable connection, bad disc) or,

2) The primary boot path is incorrect

You then attempted to boot from the alternate boot path, you got "Alert Level 15, source detail = 6 disc)"; it looks like the system disc was unknown to the PDC.

It looked like resetting the power on the server cleared it.

I would have an HPCE onsite to check the SCSI cable, terminator for ldev#1 and possibly check/repalce ldev#1. You may want to run some diagnostic on ldev#1, check if tehre is any errors on the disc using cstm info and infolog on the disc.
King is the customer!
Please use plain text.
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation