reboot OS but it hangs at "Reconfiguring setboot event subscription" section

[kentarozpe9]

Hi all,

    I have problem after reboot OS (HP-UX 11.31i)...

Console is on Serial Device - via PCDP
Booting kernel...

Loaded ACPI revision 2.0 tables.
Using /stand/ext_ioconfig

Memory Class Setup
-------------------------------------------------------------------------
Class Physmem Lockmem Swapmem
-------------------------------------------------------------------------
System : 7760 MB 7760 MB 7760 MB
Kernel : 7760 MB 7760 MB 7760 MB
User : 7019 MB 6222 MB 6247 MB
-------------------------------------------------------------------------

ktracer is off until requested.
Enabling spinlock ALAT switching
Installing Socket Protocol families AF_INET and AF_INET6
Kernel EVM initialized
sec_init(): kernel RPC authentication/security initialization.
secgss_init(): kernel RPCSEC_GSS security initialization.
rpc_init(): kernel RPC initialization.
rpcmod_install(): kernel RPC STREAMS module "rpcmod" installation. ...(driver_install)
NOTICE: nfs_client_pv3_install(): nfs3 File system was registered at index 10.
NOTICE: nfs_client_pv4_install(): nfs4 File system was registered at index 11.
NOTICE: cachefsc_install: cachefs File system was registered at index 13.
DIAGNOSTIC SYSTEM WARNING:
The diagnostic logging facility has started receiving excessive
errors. The error entries will be lost until the cause of
the excessive error logging is corrected.
Use oserrlogd(1M) man page for further details.
I/O hardware probe timed out at path 0/6/1/1 or relative to it
Boot device's HP-UX HW path is: 0/4/1/0.0x5000cca00b476755.0x0

System Console is on the Built-In Serial Interface
iether0: INITIALIZING HP AD193-60001 PCI/PCI-X 1000Base-T 4Gb FC/1000B-T Combo Adapter at hardware path 0/3/1/0/6/0
iether1: INITIALIZING HP AB352-60003 PCI/PCI-X 1000Base-T Dual-port Core at hardware path 0/4/2/0
iether3: INITIALIZING HP AD193-60001 PCI/PCI-X 1000Base-T 4Gb FC/1000B-T Combo Adapter at hardware path 0/7/1/0/6/0
iether2: INITIALIZING HP AB352-60003 PCI/PCI-X 1000Base-T Dual-port Core at hardware path 0/4/2/1
AF_INET socket/streams output daemon running, pid 56
afinet_prelink: module installed
Starting the STREAMS daemons-phase 1
LVM: Root VG activated
Swap device table: (start & size given in 512-byte blocks)
entry 0 - major is 64, minor is 0x2; start = 0, size = 33554432
Checking root file system.
file system is clean - log replay is not required
Root check done.
Create STCP device files
Starting the STREAMS daemons-phase 2
$Revision: vmunix: B.11.31_LR FLAVOR=perf
Memory Information:
physical page size = 4096 bytes, logical page size = 4096 bytes
Physical: 8356572 Kbytes, lockable: 5908556 Kbytes, available: 6725556 Kbytes

/sbin/ioinitrc:
/dev/vg00/lvol1:file system is clean - log replay is not required
/sbin/krs_sysinit:
ERROR: The module 'gvid_info' could not be loaded.
More information about the failure may be available in the
system log file (typically /var/adm/syslog/syslog.log).
ERROR: The module 'rng' could not be loaded.
More information about the failure may be available in the
system log file (typically /var/adm/syslog/syslog.log).
NOTICE: mod_load_helper: io_mod_opstart load failed, mcp->mc_typep = 0x4baf7640
NOTICE: mod_load_helper: io_mod_opstart load failed, mcp->mc_typep = 0x4baf7700
pciinfo.prep:
ERROR: Invalid number of arguments
Usage: pciinfo.prep pciinfo <operation> [status]
ERROR: The module 'pciinfo' could not be loaded.
More information about the failure may be available in the
system log file (typically /var/adm/syslog/syslog.log).
NOTICE: mod_load_helper: io_mod_opstart load failed, mcp->mc_typep = 0x48879500

insf: Installing special files for ipmi instance 0 address 250/0
insf: Installing special files for pseudo driver framebuf

NOTICE: VxVM vxdmp V-5-0-34 added disk array DISKS, datype = Disk

NOTICE: VxVM vxdmp V-5-0-34 added disk array 21000022a10e45d0, datype = HUAWEI-S3900M2

NOTICE: VxVM vxdmp V-5-0-34 added disk array 21000022a10e45cb, datype = HUAWEI-S3900M2

NOTICE: VxVM vxdmp V-5-0-0 removed disk array FAKE_ENCLR_SNO, datype = FAKE_ARRAY

May 10 11:57:40 vxvm:vxconfigd: WARNING V-365-1-1 This host is not entitled to run Veritas Storage Foundation/Veritas Cluster Server. As set forth in the End User License Agreement (EULA) you must complete one of the two options set forth below. To comply with this condition of the EULA and stop logging of this message, you have 0 days to either: - make this host managed by a Management Server (see http://go.symantec.com/sfhakeyless for details and free download), or - add a valid license key matching the functionality in use on this host using the command 'vxlicinst' and validate using the command 'vxkeyless set NONE'.
VxVM INFO V-5-2-3156 EXIT CODE: 127
/sbin/bcheckrc:
Checking for LVM volume groups and Activating (if any exist)
Volume group "/dev/vg00" is already active on this system.
Activated volume group.
Volume group "/dev/vglock" has been successfully changed.
Activated volume group.
Volume group "/dev/vgroot" has been successfully changed.
Resynchronized volume group /dev/vg00
Resynchronized volume group /dev/vglock
Resynchronized volume group /dev/vgroot
Checking vxfs file systems
UX:vxfs fsck: INFO: V-3-20913: /dev/vg00/lvol3:sanity check: root file system OK (mounted read/write)
UX:vxfs fsck: WARNING: V-3-20916: /dev/vg00/lvol4:sanity check: /dev/vg00/lvol4 needs checking
UX:vxfs fsck: WARNING: V-3-20916: /dev/vg00/lvol5:sanity check: /dev/vg00/lvol5 needs checking
UX:vxfs fsck: WARNING: V-3-20916: /dev/vg00/lvol6:sanity check: /dev/vg00/lvol6 needs checking
UX:vxfs fsck: WARNING: V-3-20916: /dev/vg00/lvol7:sanity check: /dev/vg00/lvol7 needs checking
UX:vxfs fsck: WARNING: V-3-20916: /dev/vg00/lvol8:sanity check: /dev/vg00/lvol8 needs checking
UX:vxfs fsck: WARNING: V-3-20916: /dev/vg00/lvinformix:sanity check: /dev/vg00/lvinformix needs checking
UX:vxfs fsck: WARNING: V-3-20916: /dev/vg00/lvdbtemp:sanity check: /dev/vg00/lvdbtemp needs checking
/dev/vg00/lvol4:log replay in progress
/dev/vg00/lvol4:replay complete - marking super-block as CLEAN
/dev/vg00/lvol5:log replay in progress
/dev/vg00/lvol5:replay complete - marking super-block as CLEAN
/dev/vg00/lvol6:log replay in progress
/dev/vg00/lvol6:replay complete - marking super-block as CLEAN
/dev/vg00/lvol7:log replay in progress
/dev/vg00/lvol7:replay complete - marking super-block as CLEAN
/dev/vg00/lvol8:log replay in progress
/dev/vg00/lvol8:replay complete - marking super-block as CLEAN
/dev/vg00/lvinformix:log replay in progress
/dev/vg00/lvinformix:replay complete - marking super-block as CLEAN
/dev/vg00/lvdbtemp:log replay in progress
/dev/vg00/lvdbtemp:replay complete - marking super-block as CLEAN

Cleaning /etc/ptmp...
(c)Copyright 1983-2006 Hewlett-Packard Development Company, L.P.
(c)Copyright 1979, 1980, 1983, 1985-1993 The Regents of the Univ. of California
(c)Copyright 1980, 1984, 1986 Novell, Inc.
(c)Copyright 1986-2000 Sun Microsystems, Inc.
(c)Copyright 1985, 1986, 1988 Massachusetts Institute of Technology
(c)Copyright 1989-1993 The Open Software Foundation, Inc.
(c)Copyright 1990 Motorola, Inc.
(c)Copyright 1990, 1991, 1992 Cornell University
(c)Copyright 1989-1991 The University of Maryland
(c)Copyright 1988 Carnegie Mellon University
(c)Copyright 1991-2006 Mentat Inc.
(c)Copyright 1996 Morning Star Technologies, Inc.
(c)Copyright 1996 Progressive Systems, Inc.

Confidential computer software. Valid license from HP required for
possession, use or copying. Consistent with FAR 12.211 and 12.212,
Commercial Computer Software, Computer Software Documentation, and
Technical Data for Commercial Items are licensed to the U.S. Government
under vendor's standard commercial license.

/sbin/auto_parms: DHCP access is disabled (see /etc/auto_parms.log)

HP-UX Start-up in progress
__________________________

Configure system crash dumps ................................. OK
Start Integrity VM Guest Tools ............................... OK
Removing old vxvm files ...................................... OK
VxVM INFO V-5-2-3360 VxVM device node check .................. OK
VxVM INFO V-5-2-3362 VxVM general startup .................... May 10 11:58:05 vxvm:vxconfigd: WARNING V-365-1-1 This host is not entitled to run Veritas Storage Foundation/Veritas Cluster Server. As set forth in the End User License Agreement (EULA) you must complete one of the two options set forth below. To comply with this condition of the EULA and stop logging of this message, you have 0 days to either: - make this host managed by a Management Server (see http://go.symantec.com/sfhakeyless for details and free download), or - add a valid license key matching the functionality in use on this host using the command 'vxlicinst' and validate using the command 'vxkeyless set NONE'.
OK
VxVM INFO V-5-2-3366 VxVM reconfiguration recovery ........... OK
Mount file systems ........................................... OK
Remounting Root File System .................................. OK
Setting hostname ............................................. OK
Start containment subsystem configuration .................... OK
Set privilege group .......................................... N/A
Display date ................................................. N/A
Save system crash dump if needed ............................. N/A
Start evp .................................................... OK
Enable auxiliary swap space .................................. OK
Start syncer daemon .......................................... OK
Initializing livedump ........................................ N/A
Start Utmp Daemon : manages User Accounting Database ......... OK
Configure Loopback interfaces (lo0) .......................... OK
Reconfiguring setboot event subscription .....................

and it hangs here. Do you have any solution for solve this?

Thank you.

[Robert_Jewell]

The startup script being referenced is:

lrwxr-xr-x   1 root       sys             20 Oct 19  2012 /sbin/rc2.d/S019setboot@ -> /sbin/init.d/setboot

What I see that /sbin/init.d/setboot is trying to do is:

/usr/sbin/setboot -R

Given that, the man page for 'setboot' does not reference a "-R" option.  However, there is a "-r" that states:

           -r   Reinitialize the EVM subscription for boot paths currently
                set in stable storage.  This option is useful when the boot
                path health event subscriptions are not updated after a
                change in boot paths.  For example, when the boot paths are
                updated between an evmd stop and restart.  See evmd(1M).
                Refer to the Failover section for more information.

That description suggests that perhaps -r and -R are one in the same?

What you could try is to disable this startup script by simply renaming the S019setboot file to something like orig.S019setboot and allow the system to boot.

Most likely, thereafter, running the 'setboot -R' command will hang up.    Look to see if there is a patch that can be applied to setboot or perhaps look to update the WBEM Management Bundle.

-Bob

[TK_Theerasak]

Hi Bob and All,

I also have same problem with HP-UX 11.31 and I have restarted many times ... 

as your suggestion to disable the startup script /sbin/rc2.d/S019setboot, but now I still cannot login. So I there any solution? Thank you.

HP-UX Start-up in progress
__________________________

Configure system crash dumps ................................. OK
Start Integrity VM Guest Tools ............................... OK
Removing old vxvm files ...................................... OK
VxVM INFO V-5-2-3360 VxVM device node check .................. OK
VxVM INFO V-5-2-3362 VxVM general startup .................... OK
VxVM INFO V-5-2-3366 VxVM reconfiguration recovery ........... OK
Mount file systems ........................................... OK
Remounting Root File System .................................. OK

Setting hostname ............................................. OK
Start containment subsystem configuration .................... OK
Set privilege group .......................................... N/A
Display date ................................................. N/A
Save system crash dump if needed ............................. N/A
Start evp .................................................... OK
Enable auxiliary swap space .................................. OK
Start syncer daemon .......................................... OK
Initializing livedump ........................................ N/A
Start Utmp Daemon : manages User Accounting Database ......... OK
Configure Loopback interfaces (lo0) .......................... OK
Reconfiguring setboot event subscription .....................

Thank you,

TK

[Dennis Handly]

>but now I still cannot login.

There must be something else preventing it from going on to level 3?

Anything in /etc/rc.log?