System Crashes after Kernel Tuning

Jeff Craig_1 — Mon, 03 Dec 2001 17:52:29 GMT

Hi,

I used SAM to re-tune the kernel on our HP 9000/800/R380 UNIX system running HPUX B.11.00 32-bit. I used a Tunable Parameter Set (Monolithic), then updated a few parameters from SAM. I rebooted through SAM, and the system came up fine. Then I got a call in the middle of the night that the system was down. When I looked at the console, it was at the firmware menu, and when I tried to RESET, it said:

Cannot find ENTRY_TEST
Failed to initialize
ENTRY_INIT
Status = -7

Well, throught this forum and others, I figured out how to reboot with /stand/vmunix.prev, but it died again sometime in the night. I have checked SYSLOG and looked for other evidence or clues as to what it's problem is, but I can't find any. Can anyone help me out here? FYI, I hate to say it, but I'm a DBA, not a SYSADM, so if my note sounds ignorant, that's probably the right tone.

Regards,
Jeff

Re: System Crashes after Kernel Tuning

Uday_S_Ankolekar — Mon, 03 Dec 2001 18:03:09 GMT

Hi,
The below answer I got it from this forum itself Thanks to Alex GLENNIE. Hope this helps.

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)

Goodluck,

-USA..

topic Re: System Crashes after Kernel Tuning in Operating System - HP-UX

System Crashes after Kernel Tuning

Re: System Crashes after Kernel Tuning

Re: System Crashes after Kernel Tuning