Server crashes during scheduled reboot

[Robert T. Lott]

My HP T500 SERVER for the last several weeks has been crashing during scheduled reboots and I am not sure whats wrong. Pls see below:

The script showed the following:

-- I/O hardware probe timed out at path 0/52.6.4
nh System Panic:
-- linkstamp: Mon Nov 22 22:03:04 CST 2004
-- _release_version: @(#)B2352B/9245XB HP-UX (B.11.00) #1: Thu Nov 6 01:58:21 PST 1997
-- __kern_ci_revision: $Header: kern_sequence.c,v 1.6.106.512 97/11/05 18:01:46 msosa Exp $
nh panic: I/O system hang
-- PC-Offset Stack Trace (read across, top of stack is 1st):
-- 0x0027a048 0x002e1760 0x0008ac90 0x0003cbb4 0x0034b44c 0x0028e45c
-- 0x0011c6dc 0x002b1088 0x0037b4cc 0x0037b1b4 0x002e10c0 0x002e10f4
-- 0x002e10f4 0x002e0eb0 0x002e183c 0x00230c9c 0x000d1c04 0x001c94c8
-- End Of Stack
-- *** A system crash has occurred. (See the above messages for details.)
-- *** The system is now preparing to dump physical memory to disk, for use
-- *** in debugging the crash.
PM ERROR: Your system crashed before I/O and dump configuration was complete.
-- A crash dump cannot be taken under these circumstances without
-- special configuration. Contact your HP support representative.
-- Connecting to Service Processor. (APMSG 10)(@&j2D&j154LWARN E000 REMOTE: disabled inactive multiple ACCESS FAULT: 00 SP logs contain a critical entry which has not yet been read (SPMsg 000)
-- 3 1 1 1 1 1 1 1 1 1Service Processor: Finished waiting for Lan/Console card after system reboot.
-- ********************************************************
-- A log contains a critical entry which has not been read.
-- Execute the Display Logs (dl) command to read the log.
-- ********************************************************


Also when I looked at the error messages I only saw the following:

@ PDC TOC initial chassis code 6cbb0

6 6300 02/23/2005 03:18:44 UT
BCRITICAL LOG
@ PDC TOC initial chassis code 6cbd0

7 6300 02/23/2005 03:18:45 UT
BCRITICAL LOG
@ PDC TOC initial chassis code 6cbf0

Thx

[melvyn burnard]

you have a hardware problem, log a call with your local HP Response Centre

[Robert T. Lott]

Not sure but I don't think this server is ocvered (under contract) any longer I am trying to trouble shoot on my own before bring someone out to fix...
Thx

[Patrick Wallek]

Your problem is at hardware path 0/52.6.4. The SCSI probe during bootup is timing out trying to talk to that device.

If your system comes up do an ioscan and try to find what is supposed to be at that hardware path.

If your system is not up, go and have a look at all the devices. You almost certainly have one that is having a problem. If you can find it, and it is not critical, you should just be able to disconnect it and have your system boot normally.