Unexpected shutdown

[Philemon_2]

Hello All,

Need your urgent help...

This morning i noticed that one of my Unix box was Unexpected shutdown, i connected to the console as i am remote to the box. I see the following message and not able to go further. not sure how to go further.

Need your Urgent help.

Thanks,
Phil

*****************************************

************* SYSTEM ALERT **************
SYSTEM NAME: csccansxdrc
DATE: 07/07/2010 TIME: 13:20:06
ALERT LEVEL: 12 = Software failure

REASON FOR ALERT
SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail

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

0xF8E000C01100B800 00000000 0000B800 - type 31 = legacy PA HEX chassis-code
0x58E008C01100B800 00006E06 070D1406 - type 11 = Timestamp 07/07/2010 13:20:06
A: ack read of this entry - X: Disable all future alert messages
Anything else skip redisplay the log entry
->Choice:

[Torsten.]

It would be nice to know the model of one of your Unix box and if there is something in OLDsyslog.log.

[Philemon_2]

How can i access OLDsyslog now? not sure how to go there when i was at the following prompt

A: ack read of this entry - X: Disable all future alert messages
Anything else skip redisplay the log entry
->Choice:

Please advice.

[Torsten.]

->> A: ack read of this entry - X: Disable all future alert messages

press "a" or "x"


Does it boot up?
What model?

[Philemon_2]

I tried both options A/X/Q, but the server reboots over and over. Please look into the following. Pleasehelp

*****************************************

Duplex Console IO Dependent Code (IODC) revision 1

------------------------------------------------------------------------------
(c) Copyright 1995-2002, Hewlett-Packard Company, All rights reserved
------------------------------------------------------------------------------

Processor Speed State CoProcessor State Cache Size
Number State Inst Data
--------- -------- --------------------- ----------------- ------------
0 650 MHz Active Functional 750 KB 1.5 MB
1 650 MHz Idle Functional 750 KB 1.5 MB
2 650 MHz Idle Functional 750 KB 1.5 MB
3 650 MHz Idle Functional 750 KB 1.5 MB

Central Bus Speed (in MHz) : 133
Available Memory : 6291452 KB
Good Memory Required : 166564 KB

Primary boot path: 0/0/2/0.0
Alternate boot path: 0/0/1/1.0
Console path: 0/0/4/1.0
Keyboard path: 0/0/4/0.0


Processor is starting autoboot process.

To discontinue, press any key within 10 seconds.

10 seconds expired.
Proceeding...

Trying Primary Boot Path
------------------------

Booting...
Boot IO Dependent Code (IODC) revision 1


HARD Booted.

ISL Revision A.00.43 Apr 12, 2000

ISL booting hpux

Boot
: disk(0/0/2/0.0.0.0.0.0.0;0)/stand/vmunix
11317248 + 2322432 + 156757640 start 0x1fbce8




alloc_pdc_pages: Relocating PDC from 0xffff800000 to 0x7fa00000.

[Philemon_2]

Also please look at the following...

System Console is on the Built-In Serial Interface
btlan: Initializing 10/100BASE-TX card at 0/12/0/0/4/0....
btlan: Initializing 10/100BASE-TX card at 0/12/0/0/5/0....
btlan: Initializing 10/100BASE-TX card at 0/12/0/0/6/0....
btlan: Initializing 10/100BASE-TX card at 0/12/0/0/7/0....
iether5: INITIALIZING HP AD331-60001 PCI/PCI-X 1000Base-T Adapter at hardware path 0/9/0/0
Entering cifs_init...
Initialization finished successfully... slot is 9
Logical volume 64, 0x3 configured as ROOT
LVM: VG 64 0x000000: Quorum check failed!
LVM : Activation of root volume group failed
Quorum not present, or some physical volume(s) are missing


-----------------------------------------------------
| |
| SYSTEM HALTING during LVM Configuration |
| |
Could not configure root VG
If new kernel, ISL> hpux -lm /stand/vmunix; pvck -y /dev/rdsk/....
| |
-----------------------------------------------------


linkstamp: Wed Mar 18 15:35:10 EDT 2009
_release_version: @(#) $Revision: vmunix: vw: -proj selectors: CUPI80_BL2000_1108 -c 'Vw for CUPI80_BL2000_1108 build' -- cupi80_bl2000_1108 'CUPI80_BL2000_1108' Wed Nov 8 19:24:56 PST 2000 $
panic: LVM: Configuration failure

PC-Offset Stack Trace (read across, top of stack is 1st):
0x0020e5d8 0x005261cc 0x00529740
0x00526084 0x00357188 0x004703d4
0x00358e70 0x0017666c 0x001fc2e4
End Of Stack

Trap Type 15 (Data page fault):
Instruction Address (pcsq.pcoq) = 0x0.0x474790
Instruction (iir) = 0x531a0020 (load/store)
Target Address (isr.ior) = 0x0.0x0000000000000010
Base Register (gr24) = 0x0000000000000000
Savestate Ptr (ssp) = 0x4c58000.0x400003ffffff0fa8
Savestate Return Pointer (ss_rp) = 0x0000000000000000

System Panic:

linkstamp: Wed Mar 18 15:35:10 EDT 2009
_release_version: @(#) $Revision: vmunix: vw: -proj selectors: CUPI80_BL2000_1108 -c 'Vw for CUPI80_BL2000_1108 build' -- cupi80_bl2000_1108 'CUPI80_BL2000_1108' Wed Nov 8 19:24:56 PST 2000 $
panic: Data page fault



*** 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.

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.

********** VIRTUAL FRONT PANEL **********
System Boot detected
*****************************************
LEDs: RUN ATTENTION FAULT REMOTE POWER
FLASH FLASH FLASH ON ON
LED State: Unexpected Reboot. Running non-OS code. Non-critical error detected.
Check Chassis and Console Logs for error messages.

[Andrew Rutter · Accepted solution]

hi,

looks like the server cannot boot due to a failed hard drive. probably a root disk.

you will need to boot into maintenance mode as the error states and try and find out which disk has a problem.

or possibly try and boot the system from the isl prompt with hpux -lq or something similar? depending upon if its a pa box or itanium.

stop the system from booting at pdc.do a search for bootable devices first, and issue boot command, selecting yes to interact with isl

as yoy have 4x 650mhz cpus i would hazard a guess it been an rp5470(l3000). looks like it from the disk paths too.

Andy

[Philemon_2]

Hello Andrew Rutter,

Thank you so much... You were absolutely right, I appreciate it.

As per your advice I did the following and it worked for me

(Your advice: stop the System from booting at pdc. do a search for bootable devices first, and boot the system from the isl prompt with hpux -lq, selecting yes to interact with isl.)

I booted the server from isl prompt with hpux -lq (Ignore quorum), it worked, system is back online now. I identified that there was a failed disk.

Thanks Again

Regards,
Philemon

[Philemon_2]

Issue is been resolved, Thank you!