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

Failed Boot on HP9000/D350 Server

 
Karl Haynes
Occasional Advisor

Failed Boot on HP9000/D350 Server

 
Measure twice, cut once
9 REPLIES 9
Michael Steele_2
Honored Contributor

Re: Failed Boot on HP9000/D350 Server

"....Searching for potential boot device(s)..." revealed:

P0 8/4.5 Random access media
P1 8/4.8 Random access media
P2 8/16/5.2 Random access media
P3 8/16/6.0 LAN Module

Your next step is the following:

bo pri (* this should be 8/4.5 *)
interact with IPL? YES
ISL> hpux -is
# init 1
# init 2
# init 3

Observe the LCD panel and note all the LED messages as they scroll by. Copy down and FLT messages.

90% of the Dclass server had no PDC processor. If you're of the 10%:

turn the key to service
control b
sl
observe the last 50 LCD messages and note any FLT's.

D Class servers 'RS' from the power switch.
D Class servers have a 'TOC' switch in the back on the system board. This will create a dump.

There are HW single points of failure at the combination system/io card board, and the SCSI controller. In this case, 8/4.

Your CDROM device is P2 - 8/16/5.2.
Your tape device is not listed. This should be listed as a 'sequential access media' bootable device.
Support Fatherhood - Stop Family Law
Michael Steele_2
Honored Contributor

Re: Failed Boot on HP9000/D350 Server

"....Searching for potential boot device(s)..." revealed:

P0 8/4.5 Random access media
P1 8/4.8 Random access media
P2 8/16/5.2 Random access media
P3 8/16/6.0 LAN Module

Your next step is the following:

bo pri (* this should be 8/4.5 *)
interact with IPL? YES
ISL> hpux -is
# init 1
# init 2
# init 3

Observe the LCD panel and note all the LED messages as they scroll by. Copy down any
FLT messages.

90% of the Dclass server had no PDC processor. If you're of the 10%:

turn the key to service
control b
sl
observe the last 50 LCD messages and note any FLT's.

D Class servers 'RS' from the power switch.
D Class servers have a 'TOC' switch in the back on the system board. This will create a dump.

There are HW single points of failure at the combination system/io card board, and the SCSI controller. In this case, 8/4.

Your CDROM device is P2 - 8/16/5.2.
Your tape device is not listed. This should be listed as a 'sequential access media' bootable device.
Support Fatherhood - Stop Family Law
Karl Haynes
Occasional Advisor

Re: Failed Boot on HP9000/D350 Server

When I boot pri and try select Y to interact with IPL, I do not get the ISL prompt. There is a lot of hard drive clicking but I do not get the ISL prompt, just the following:
Menu -------------------------------------------------------------

Command Description
------- -----------
BOot [PRI|ALT|] Boot from specified path
PAth [PRI|ALT|CON|KEY] [] Display or modify a path
SEArch [DIsplay|IPL] [] Search for boot devices

COnfiguration [] Access Configuration menu/commands
INformation [] Access Information menu/commands
SERvice [] Access Service menu/commands

DIsplay Redisplay the current menu
HElp [|] Display help for menu or command
RESET Restart the system
-------
Main Menu: Enter command > bo pri
Interact with IPL (Y or N)?> Y

WARN 80F9.
Cannot find ENTRY_TEST.

Failed to initialize.

ENTRY_INIT
Status = -4

00800000 00000001 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00003508 0000001B C1000040 01840000 070500D8 00000000 0005F004 00000000
98080000 0000EAD4 0000EAD4 00000000 00000002 00000004 00000002 00000000
WARN 80F5
Failed to initialize.


CPU 0
WARNING: Memory has been initialized, but not tested as a result of
FASTBOOT being enabled. To test memory, use the FASTBOOT
command in the CONFIGURATION menu and reboot the system.

Main Menu: Enter command >
Measure twice, cut once
Michael Steele_2
Honored Contributor

Re: Failed Boot on HP9000/D350 Server

WARN 80F5 Error executing Entry Init

You've got a HW problem. I believe either an unterminated SCSI port or bad SCSI controler.
Support Fatherhood - Stop Family Law
Michael Steele_2
Honored Contributor

Re: Failed Boot on HP9000/D350 Server

Sorry, that would be:

WARN 80F9 PDC IODC failed to return Entry Test
Support Fatherhood - Stop Family Law
Enrico P.
Honored Contributor

Re: Failed Boot on HP9000/D350 Server

Hi,
you can try to do that it say you:


FASTBOOT being enabled. To test memory, use the FASTBOOT
command in the CONFIGURATION menu and reboot the system

From


------- Main Menu -------------------------------------------------------------

Command Description
------- -----------
BOot [PRI|ALT|] Boot from specified path
PAth [PRI|ALT|CON|KEY] [] Display or modify a path
SEArch [DIsplay|IPL] [] Search for boot devices

COnfiguration [] Access Configuration menu/commands
INformation [] Access Information menu/commands
SERvice [] Access Service menu/commands

DIsplay Redisplay the current menu
HElp [|] Display help for menu or command
RESET Restart the system
-------
Main Menu: Enter command >

Enter co
and try the FASTBOOT command and reboot.

Enrico
Robert_Jewell
Honored Contributor

Re: Failed Boot on HP9000/D350 Server

It sounds like you may have lost your boot disk. The entry-init -4 indicates an un-bootable device.

You could try booting an Install CDROM and try the recovery scripts to see if your drive is still good, but from the "clicking" sounds you described, the drive may be toast.

-Bob
----------------
Was this helpful? Like this post by giving me a thumbs up below!
Vincent Farrugia
Honored Contributor

Re: Failed Boot on HP9000/D350 Server

Hello,

Most probably you have a faulty boot harddisk. It failed to boot also from the alternative path, but since it is your CD-ROM, that is understandable.

D350 disks are hot-pluggable. Most probably, you have to replace disk and reinstall. If you have ignite backup, restore through it.

HTH,
Vince
Tape Drives RULE!!!
Mike_Ca Li
Regular Advisor

Re: Failed Boot on HP9000/D350 Server

I'm experiencing similar issue after I replaced a SCSI disk.
Originaly I had 4 X 9 GB with IDs 3, 4, 5, 6

I disconnected disks with IDs 5 and 6 and replaced with new SCSI HD ID 6.
Getting the WARN 80F5 error and can't find the boot device (cannot find ENTRY_TEST).
I did a SEA to search for a boot path:
P0 10/0.8 fwscsi.8 Random access media
P1 10/0.4 fwscsi.4
P2 10/0.3 fwscsi.3
P3 10/12/5.0 sescsi.0

Pri is set to 10/0.6 , my question is that did I replace/disconnected the boot devices?
Anyone has idea how SCSI Id is related to fwscsi.## ? Thank you