Boot error during startup

[martin van den brink]

Our HP9000 has been powered off for some time. Now I have tried to boot the server again. I have tried it from the primary boot path and also from the CD_ROM.
Always the following messages appear.

Cannot find ENTRY_TEST
Failed I/O operation with ENTRY_10
STATUS -4

Error Reading IPL

Do I have a hardware problem or what ?

[Alex Glennie]

The majority of ENTRY_INIT errors encountered are: Status = -4 and
Status = -7.

ENTRY_INIT -4 Causes:
- the disk is experiencing hardware faults and needs replacing.
- the path to the disk is experiencing problems. e.g.. Termination,
cabling, SCSI adapter, SCSI adapter seating.
ENTRY_INIT -7 Causes:
- Booting from the wrong path or non-existent device.
- Trying to boot from a device that is not responding.

Troubleshooting Steps:
. Power off the server, then power off the disks - leave all powered
off for at least 30 seconds. Power on disks, then server.

. When server is booting, check access LED's on boot disk, is it being
accessed? Yes - possible bad disk. No - possible bad path to
disk, e.g.. Cabling/termination/adapter. Time to log hardware call.

. If boot disk is in an external disk enclosure, check the cabling is
secure, and access/status lights are normal.

. Attempt to boot from an alternate boot path if you have one,
e.g.. Mirror boot disk, alternate boot disk.

. Double check you have the correct boot path.

. Use the SEArch option at the Boot Menu, does the primary boot path
appear? If not, we cannot see the disk and time to log a hardware call.
If we can see the boot disk, but still get ENTRY_INIT error when booting
we need to log a hardware call.

. We can boot to Recovery Shell and use the chroot option to fsck the
boot disk, but this will always fail if we cannot get to the ISL
prompt of a disk; in most occurrences of this error using the Recovery
Shell (Support Media) is not helpful.

. Perform preliminary steps to reinstall the system; As in most cases this
error means the boot disk is bad and will need to be replaced. If the
system is not mirrored then the recommended recovery method is to
reinstall the system. Is the backup offsite? Do you know what sizes
the vg00 logical volumes are?


Errors Returned by IODC ENTRY_INIT
Overview of ENTRY_INIT: To initialize and test a boot device so that ENTRY_I/O can transfer data to/from the boot device. ENTRY_INIT is also used to establish module or device communication.
Status Description
2 Recoverable Error.
The call completed normally and the returned results are valid
0 OK.
The call completed normally without error
-2 Nonexistent option.
The call did not correspond to implemented options in entry_init
-3 Can not complete call without error.
An error of unknown type prevented the call from completing correctly
-4 Unrecoverable Hardware Error.
An unrecoverable hardware error has occurred between the processor PDC and IODC on the target controller or device
-5 Unrecoverable data error.
ENTRY_INIT encountered an error while transferring data to/from the target controller or device
-6 Illegal device address.
The device address supplied to ENTRY_INIT is invalid
-7 Nonexistent device.
The device address supplied to ENTRY_INIT is valid, but, the target controller or device is not installed or is not responding
-8 Module/device not ready.
The module or device is not ready to be initialized. The target is not ready because it has not completed its power on reset/selftest
-9 Cannot locate a console or boot device.
ENTRY_INIT could not locate a console or boot device
-10 Invalid argument.
ENTRY_INIT was passed an invalid command
-11 Data buffer too small
-12 Unsupported record size
-13 Protocol Error.
A protocol error was encountered on bus during data transfer to/from the target controller or device (which also means 3rd part hardware or a boot disk)

[CHRIS_ANORUO]

Hi Martin,

You have a hardware problem as explained by Alex.

[Paula J Frazer-Campbell]

Hi Martin
Before you get to deep into this problem check the obvious (As the server has been powered down for some time.)

Connections on cables and boards without power oxidise and oxidants tend not to let electrickery run through them.

So power down - unplug and refit all data cables - and recheck.
If this fails then I would get the system boards removed and refitted.