topic Re: Integrity Server does not come up in Operating System - HP-UX

Integrity Server does not come up

dictum9 — Tue, 15 Aug 2006 16:18:58 GMT

rx4640 hpux 11.23

When booting, I get this error message. This happened right after I patched SAM. Panicked twice in a row.

ktp 00000000_00000000 rnat 00000000_00000000 ssd 00000000_00000000
ksp 00000000_00000002 ccv 00000000_00000001
sv 00000000_00000000 pfs 00000000_00000490 ec 00

iip ffffffff_ffffff90/0 ifs 80000000_00000490 [i]psr 00001010_0842a01a
iipa e0000000_012cc360 tpr 00000000_00000000 isr 00000001_00000000

ibe sddiimic rtldsdpsddd p i mmaub
andrisdadtcspl tbpbiipphlt kic hlcpe
psr bits = ------------------01000000010000----10000100001-101-------01101-

e snirsn
deioirsparwx < code >
isr bits = --------------------000000000001--------000000000000000000000000

arg0=ffffffff_ffffff90 (cr.iip)
arg1=00000000_00000000 (unknown)

Dirty Registers:
loc0 : 00000000_00000001 00000000_00000024 00000000_00000000 00000000_0006ddd0
loc4 : e0000000_003a3a00 e0000000_0159aee0 00000000_00000000 00000000_00000796
loc8 : e0000000_0159d6b0
out0 : ffffffff_ffffff9b 00000000_00000024 00000000_00000000 00000000_0006ddd0
out4 : e0000000_003a3a00 e0000000_0159aee0 00000000_00000000

System Panic:

panic: Bad News!

Stack Trace:
IP Function Name
0xe000000000dce9a0 bad_news+0x950
0xe000000000dcd9c0 bubbledown
0xffffffffffffff90 +0xffffffffffffff90
0xffffffffffffff9b +0xffffffffffffff9b
End of Stack Trace

linkstamp: Tue Aug 15 16:24:45 EDT 2006
_release_version: @(#) $Revision: vmunix: B11.23_LR FLAVOR=perf Fri Aug 29 22:35:38 PDT 2003 $

*** 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.
This system does not support a crash dump under these circumstances.
Contact your HP support representative for assistance.
***********************************************************
* ROM Version : 03.17
* ROM Date : 03/15/2005
* BMC Version : 03.52
***********************************************************
0 0 0x0015B2 0x0000000023846555 boot time event
1 0 0x0000A4 0x0000000000000000 start memory configuration

Re: Integrity Server does not come up

Mel Burslan — Tue, 15 Aug 2006 16:23:16 GMT

Your system is obviously at the point of no return. Instead of trying to save whatever is left over, save yourself some time and start rebuilding the server, either via cold install from the cd/dvd media or from an ignite tape taken off of a same a or very similar server.

Re: Integrity Server does not come up

dictum9 — Tue, 15 Aug 2006 16:27:54 GMT

I think so too, but I want to least boot into single user to recover a few config files. Do I choose (r) or (x) option to get a limited shell?

HP-UX CORE MEDIA SYSTEM RECOVERY
MAIN MENU

s. Search for a file
b. Reboot
l. Load a file
r. Recover an unbootable HP-UX system
x. Exit to shell

This menu is for listing and loading the tools contained on the core media.
Once a tool is loaded, it may be run from the shell. Some tools require other
files to be present in order to successfully execute.

Select one of the above:

Re: Integrity Server does not come up

Mel Burslan — Tue, 15 Aug 2006 17:25:18 GMT

I am not familiar with itanium systems but x will drop you into a very restricted shell right on the spot, and with this shell I am not sure what exactly you can or can not do. responding with r will at least try getting you into a somewhat workable state. I think r is a better option here, but this is from RISC architecture experience long time ago, not IA64, nothing new. When you choose r option, you may have to have a support/recovery cd/dvd in the optical disk drive of the machine. Better try to get hold of one before you start.

Re: Integrity Server does not come up

dictum9 — Tue, 15 Aug 2006 17:28:47 GMT

I got that far. In this limited shell, I managed to salvage a few important system files, like netconf for example. (It has lots of NICS and I hate reconfiguring them again) passwd file and thinking of what else I can salvage before I reinstall it.

BTW, I tried to boot off the old kernel with no success.

=================================================================
The root disk has been mounted under /ROOT. If you would like to
chroot to this directory, execute the commands:
loadfile chroot
chroot /ROOT /sbin/sh

# loadfile chroot
# chroot /ROOT /sbin/sh