1839105 Members
4411 Online
110136 Solutions
New Discussion

Re: Bootup Sequence hang

 
Kenneth Woolard
Advisor

Bootup Sequence hang

Has anyone come across the following issue whereby the boot sequence hangs at this point. Tried using previous version of kernel at ISL prompt and also an Ignite backup. Same result.

Prior to this the PDC firmware was upgraded to 46.34 via patch PHSS_37789 and was succesful.
I then installed GOLDBASEAPPS/BASE B.11.11.0706.467 successfully - system came back up.

Issue started I think when I tried to install 6 patches from HWEnable11i and also install POwerPath 4.5.1 at the same time.

*******************************************
Anyway here is the bootup sequence hang

Firmware Version 46.34

Duplex Console IO Dependent Code (IODC) revision 1
------------------------------------------------------------------------------
(c) Copyright 1995-2004, Hewlett-Packard Company, All rights reserved
------------------------------------------------------------------------------

Processor Speed State CoProcessor State Cache Size
Number State Inst Data
--------- -------- --------------------- ----------------- ------------
0 800 MHz Active Functional 33554432 33554432
1 800 MHz Idle Functional 33554432 33554432

Central Bus Speed (in MHz) : 200
Available Memory : 4194304 KB
Good Memory Required : Not initialized. Defaults to 32 MB.

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


Processor is booting from the first available device.

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/1/1/0.0.0.0.0.0.0;0)/stand/vmunix
11350016 + 1986560 + 3281880 start 0x1fa668




alloc_pdc_pages: Relocating PDC from 0xfffffff0f0c00000 to 0x3f900000.
LVM: /stand/rootconf is corrupted
gate64: sysvec_vaddr = 0xc0002000 for 2 pages
NOTICE: autofs_link(): File system was registered at index 3.
NOTICE: cachefs_link(): File system was registered at index 4.
NOTICE: nfs3_link(): File system was registered at index 5.
td: claimed Tachyon XL2 Fibre Channel Mass Storage card at 0/2/1/0
td: claimed Tachyon XL2 Fibre Channel Mass Storage card at 0/6/1/0
igelan0: INITIALIZING HP PCI 1000Base-T Core at hardware path 0/1/2/0
iether1: INITIALIZING HP A7012-60001 PCI/PCI-X 1000Base-T Dual-port Adapter at hardware path 0/3/1/0
iether2: INITIALIZING HP A7012-60001 PCI/PCI-X 1000Base-T Dual-port Adapter at hardware path 0/3/1/1
iether3: INITIALIZING HP A7012-60001 PCI/PCI-X 1000Base-T Dual-port Adapter at hardware path 0/4/1/0
iether4: INITIALIZING HP A7012-60001 PCI/PCI-X 1000Base-T Dual-port Adapter at hardware path 0/4/1/1

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 64, minor is 0x2; start = 0, size = 8388608
Starting the STREAMS daemons-phase 1
Checking root file system.
log replay in progress
replay complete - marking super-block as CLEAN
Root check done.
Create STCP device files
Starting the STREAMS daemons-phase 2
$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 $
Memory Information:
physical page size = 4096 bytes, logical page size = 4096 bytes
Physical: 4192256 Kbytes, lockable: 3762932 Kbytes, available: 3389852 Kbytes

/sbin/ioinitrc:
/dev/vg00/lvol1: 176 files, 0 icont, 7957 used, 29409 free (313 frags, 3637 blocks)
insf: Installing special files for ipmi instance 0 address 16
insf: Installing special files for pseudo driver framebuf
/sbin/krs_sysinit:
ln: Warning! /stand/krs/_stand_vmunix.krs and /stand/krs_lkg//_stand_vmunix.krs are identical
ln: Warning! /stand/krs/system.krs and /stand/krs_lkg//system.krs are identical


Starting EMC PowerPath.
PIOC_START_DAEMON: Invalid argument
Access error on piocDaemon.pUserBuf=1073758208
*******************************************

Tried to recover from Ignite backup but I think that was no good as it was done before the PDU firmware upgrade and complained about not recognising CPU.


Looks like only option I have available is to replace the main board ?
5 REPLIES 5
Mridul Shrivastava
Honored Contributor

Re: Bootup Sequence hang

It has something to do with EMC powerpath software malfunction. Can you try booting in single user mode and try searching for the startup script for this one. May be you could start swagentd daemon and try uninstalling this software.

How did you upgrade the PDC firmware ?? (Via patch from OS or from MP by xd)

If Mp has been used then did u have a backup of Old version?? You can think of downgrading the PDC version using that and restore the old ignite tape.

Replacing Motherboard .. We may get some new errors is System ID etc will be different for that...

All the best.
Time has a wonderful way of weeding out the trivial
Avinash20
Honored Contributor

Re: Bootup Sequence hang

This seems to be an issue with EMC starup scripts.
You could boot into single user mode
http://docs.hp.com/en/A5201-96044/apas02.html#aes-npar-329

FSCK and mount the FS
# fsck -y
# mount -a

>> Check the runlevel at which EMC startup script are configured.
> Mostly it will be in /sbin/rc*.d which is linked to /sbin/init.d/

You could rename the startup script and then go to the next runlevel
# init 3

>> You could also press the following button to CoreDump the process which is trying to start

"Ctrl" + "\" + "d"
"Ctrl" + "\" + "c"
"Light travels faster than sound. That's why some people appear bright until you hear them speak."
John_Hancock
Trusted Contributor

Re: Bootup Sequence hang

I have been working with Ken on this issue. We get the same error when we boot in single user mode as well.

We did the firmware upgrade from the OS using the HP patch and I don't believe there is a backup of the old firmware.

We are getting an OS DVD and will try to disable the power path start so that we can at least boot the host.

Any further suggestions will be most appreciated.
Michael Steele_2
Honored Contributor

Re: Bootup Sequence hang

You can boot off of the previous kernel.

hpux -is /stand/vmunix.prev (* single user *)
Support Fatherhood - Stop Family Law
John_Hancock
Trusted Contributor

Re: Bootup Sequence hang

Michael, Thanks for the reply but we already tried that. We get exactly the same error.