System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

system panic ,anyone can help?

 
yuchengliu_1
Occasional Contributor

system panic ,anyone can help?

HP L2000

gsp chasis log

Log Entry # 1 :
SYSTEM NAME: uninitialized
DATE: 01/01/1970 TIME: 00:02:12
ALERT LEVEL: 3 = System blocked waiting for operator input

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

CALLER ACTIVITY: E = system warning STATUS: 0
CALLER SUBACTIVITY: 00 = implementation dependent
REPORTING ENTITY TYPE: E = HP-UX REPORTING ENTITY ID: 00

0xF8E000301100E000 00000000 0000E000 type 31 = legacy PA HEX chassis-code
0x58E008301100E000 00004600 0100020C type 11 = Timestamp 01/01/1970 00:02:12
Type CR for next entry, - CR for previous entry, Q CR to quit.

when booted the system ,it paused at following messages


Main Menu: Enter command or menu > bo p1
Interact with IPL (Y, N, or Cancel)?> y


Press Q/q to quit, Enter to continue:

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


HARD Booted.

ISL Revision A.00.38 OCT 26, 1994

ISL> hpux -lm (;0)/stand/vmunix

Boot
: disk(0/0/1/1.0.0.0.0.0.0;0)/stand/vmunix
6692864 + 866040 + 1709296 start 0x212be8


alloc_pdc_pages: Relocating PDC from 0xf0f0000000 to 0x7f9ab000.
gate64: sysvec_vaddr = 0xc0002000 for 1 pages

Press Q/q to quit, Enter to continue:

NOTICE: autofs_link(): File system was registered at index 3.
NOTICE: nfs3_link(): File system was registered at index 5.

System Console is on the Built-In Serial Interface
Logical volume 64, 0x3 configured as ROOT
Logical volume 64, 0x2 configured as SWAP
Logical volume 64, 0x2 configured as DUMP
Swap device table: (start & size given in 512-byte blocks)
entry 0 - major is 31, minor is 0x10003; start = 0, size = 2097152


Press Q/q to quit, Enter to continue:

linkstamp: Sun Dec 11 16:14:05 EAT 2005
_release_version: @(#)B2352B/9245XB HP-UX (B.11.00) #1: Wed Nov 5 22:38:19 PST 1997
__kern_ci_revision: $Header: kern_sequence.c,v 1.6.106.512 97/11/05 18:01:46 msosa Exp $

panic: all VFS_MOUNTROOTs failed: NEED DRIVERS ?????

PC-Offset Stack Trace (read across, top of stack is 1st):
0x002db93c 0x003549dc 0x0026c748
0x0010651c 0x0021314c
End Of Stack


Press Q/q to quit, Enter to continue: q



some other messages below

gate64: sysvec_vaddr = 0xc0002000 for 1 pages
NOTICE: autofs_link(): File system was registered at index 3.
NOTICE: nfs3_link(): File system was registered at index 5.

System Console is on the Built-In Serial Interface
Logical volume 64, 0x3 configured as ROOT
Logical volume 64, 0x2 configured as SWAP
Logical volume 64, 0x2 configured as DUMP
Swap device table: (start & size given in 512-byte blocks)
entry 0 - major is 31, minor is 0x10003;

start = 0, size = 2097152

************* SYSTEM ALERT **************
SYSTEM NAME: uninitialized
DATE: 01/01/1970 TIME: 00:02:05
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 OFF OFF ON ON

0xF8E000C01100B800 00000000 0000B800 - type 31 = legacy PA HEX chassis-code
0x58E008C01100B800 00004600 01000205 - type 11 = Timestamp 01/01/1970 00:02:05
A: ack read of this entry - X: Disable all future alert messages
Anything else skip redisplay the log entry
->Choice:Timeout!
*****************************************

************* SYSTEM ALERT **************
SYSTEM NAME: uninitialized
DATE: 01/01/1970 TIME: 00:02:05
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
ON FLASH FLASH ON ON

0xA0E000C01100B000 00000000 000005E9 - type 20 = major change in system state
0x58E008C01100B000 00004600 01000205 - type 11 = Timestamp 01/01/1970 00:02:05
A: ack read of this entry - X: Disable all future alert messages
Anything else skip redisplay the log entry
->Choice:x
*****************************************

CAUTION: System Alerts have been disabled. This will re-enable with
a re-boot or power-on of the system. To re-enable system alerts now, you
may use the AC (Alert Display Configuration) command.

************* SYSTEM ALERT **************
Alert messages are now disabled. Enter Commands Interface AC command to enable them again
*****************************************

********** VIRTUAL FRONT PANEL **********
System Boot detected
*****************************************
LEDs: RUN ATTENTION FAULT REMOTE POWER
FLASH FLASH FLASH ON ON

platform config 626F
processor slave rendezvous 1C17
processor test 1142
PDH INIT 3722
processor test 1100
processor test 1100
processor test 1100
processor test 1100
processor test 1100
processor test 1100
3 REPLIES 3
Highlighted
Chan 007
Honored Contributor

Re: system panic ,anyone can help?

Hi,

Try booting the system in a Sible User mode.

Stop the boot process when it prompts and try your luck.

Even it works better log a call with HP.
Cheers 007...

Highlighted
Steven E. Protter
Exalted Contributor

Re: system panic ,anyone can help?

Shalom,

Your system may have had a SCSI disk go bad. It could also be just a loose cable or something like that.

I had a D320 do this to be continuously twice, once when I connected a scsi card with the same scsi id as the scsi card at the other end of a jbod and once when a disk failed in a HP-6000 disk array.

In both cases solving the scsi problem made the problem go away.

It could however be almost any kind of hardware issue. If you've done anything to the system recently consider backing that change out.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Highlighted
Sameer_Nirmal
Honored Contributor

Re: system panic ,anyone can help?

Hi,

One of the reasons of such system panic buring bootup is unable to mount "root" filesystem.

You can try to boot using old kernel
ISL > hpux -lm /stand/vmunix.prev
Don't use (;0) while booting.

Another probable cause could be bad super block of the root file system. In this case you need to boot with core OS media and run fsck -b

If you have mirrored disk , try above with that disk.

If you have changed anything like generating new kernel or SCSI card changed etc. revert it back.