topic Re: boot issue: INIT respawning in Operating System - HP-UX

boot issue: INIT respawning

masood bt — Wed, 24 Feb 2010 15:49:59 GMT

A server's disk has been mirrored.
Tryin to use this newly mirrored disk as a boot disk for a new server. Not booting.

C) Copyright 1999-2006 Hewlett-Packard Development Company, L.P.
All rights reserved

HP-UX Boot Loader for IPF -- Revision 2.029

Press Any Key to interrupt Autoboot
\efi\hpux\AUTO ==> hpux -lq

INIT: Command is respawning too rapidly.
Will try again in 5 minutes.
Check for possible errors.
id:icap "/usr/lbin/icapd # Instant Capacity daemon"

INIT: Command is respawning too rapidly.
Will try again in 5 minutes.
Check for possible errors.
id:util "/usr/lbin/utild # Utilization Provider daemon"

INIT: Command is respawning too rapidly.
Will try again in 5 minutes.
Check for possible errors.
id:ambo "/opt/sectra/bin/ambo_server > /dev/null 2>&1"

INIT: Command is respawning too rapidly.
Will try again in 5 minutes.
Check for possible errors.
id:cim1 "/opt/wbem/lbin/cimserverd"

INIT: Command is respawning too rapidly.
Will try again in 5 minutes.
Check for possible errors.
id:ems4 "/etc/opt/resmon/lbin/p_client"

INIT: Command is respawning too rapidly.
Will try again in 5 minutes.
Check for possible errors.
id:cons "/usr/sbin/getty console console # system console"

"The Sytem is ready", but no prompt.
I am able to boot in single user mode.
I saw in other threads suggesting to edit inittab file, which I dont this solves my problem here...however, vi is not working, I am not sure of using "ed" editor.

Attached vgdisplay info here.
Any help please?

Re: boot issue: INIT respawning

masood bt — Wed, 24 Feb 2010 17:56:19 GMT

Just discovered, in PV with key 0 all are stale
in another PE with Key 1, only one LE is stale.

How to convert this particular LE as current?

# lvdisplay -v -k /dev/vg00/lvol1
lvdisplay: Warning: couldn't query physical volume "/dev/dsk/c4t6d0s2":
The specified path does not correspond to physical volume attached to
this volume group
lvdisplay: Warning: couldn't query all of the physical volumes.
--- Logical volumes ---
LV Name /dev/vg00/lvol1
VG Name /dev/vg00
LV Permission read/write
LV Status available/stale
Mirror copies 1
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 512
Current LE 32
Allocated PE 64
Stripes 0
Stripe Size (Kbytes) 0
Bad block off
Allocation strict/contiguous
IO Timeout (Seconds) default

--- Distribution of logical volume ---
PV Name LE on PV PE on PV
/dev/dsk/c0t6d0s2 32 32

--- Logical extents ---
LE PV1 E1 Status 1 PV2 PE2 Status 2
00000 0 00000 current 1 00000 stale
00001 0 00001 stale 1 00001 current
00002 0 00002 stale 1 00002 current
00003 0 00003 stale 1 00003 current
00004 0 00004 stale 1 00004 current
00005 0 00005 stale 1 00005 current
00006 0 00006 stale 1 00006 current
00007 0 00007 stale 1 00007 current
00008 0 00008 stale 1 00008 current
00009 0 00009 stale 1 00009 current
00010 0 00010 stale 1 00010 current
00011 0 00011 stale 1 00011 current
00012 0 00012 stale 1 00012 current
00013 0 00013 stale 1 00013 current
00014 0 00014 stale 1 00014 current
00015 0 00015 stale 1 00015 current
00016 0 00016 stale 1 00016 current
00017 0 00017 stale 1 00017 current
00018 0 00018 stale 1 00018 current
00019 0 00019 stale 1 00019 current
00020 0 00020 stale 1 00020 current
00021 0 00021 stale 1 00021 current
00022 0 00022 stale 1 00022 current
00023 0 00023 stale 1 00023 current
00024 0 00024 stale 1 00024 current
00025 0 00025 stale 1 00025 current
00026 0 00026 stale 1 00026 current
00027 0 00027 stale 1 00027 current
00028 0 00028 stale 1 00028 current
00029 0 00029 stale 1 00029 current
00030 0 00030 stale 1 00030 current
00031 0 00031 stale 1 00031 current

Re: boot issue: INIT respawning

Torsten. — Wed, 24 Feb 2010 18:45:20 GMT

As said in your other thread, consider to restore the system from backup.

Re: boot issue: INIT respawning

shanmuhanandam — Thu, 25 Feb 2010 07:06:31 GMT

Hi,
if you are not able to edit the inittab file, then you have only option to restore the OS.

Thanks,
Shanmugam.

Re: boot issue: INIT respawning

Matti_Kurkela — Thu, 25 Feb 2010 08:42:51 GMT

The message

INIT: Command is respawning too rapidly.
Will try again in 5 minutes.
Check for possible errors.
id:cons "/usr/sbin/getty console console # system console"

indicates the system has made multiple attempts to produce a login prompt on the console, but the getty process (which is responsible for producing the login prompt) keeps failing.

This and the other error messages all together suggest there is something very wrong with your system. Perhaps some of the system libraries in /lib have been damaged: that would make the system unable to run most commands.

I don't think editing the /etc/inittab file is applicable here. All the failing commands except the ambo_server are standard HP-UX components, and the init process seems to be trying to start them in a standard way. So I don't think your /etc/inittab is broken: the problem must be elsewhere.

MK

Re: boot issue: INIT respawning

Torsten. — Thu, 25 Feb 2010 08:47:21 GMT

If a LE (both PE) are stale on both disks, you are out of luck and need to restore the data from backup.

Re: boot issue: INIT respawning

Yallappa — Thu, 25 Feb 2010 09:15:47 GMT

Hi,

If this is the new server reinstall it and re mirror it

How to mirror plz find the attachment.

Re: boot issue: INIT respawning

masood bt — Thu, 25 Feb 2010 11:00:14 GMT

I will continue this is LVM section's thread.

http://forums13.itrc.hp.com/service/forums/questionanswer.do?threadId=1410438

could you please join me there? thank you.

Re: boot issue: INIT respawning

masood bt — Thu, 25 Feb 2010 11:00:44 GMT

continued in abother thread

http://forums13.itrc.hp.com/service/forums/questionanswer.do?threadId=1410438