topic Re: Ignite error in Operating System - HP-UX

Ignite error

Karthik Balu — Mon, 09 Feb 2009 02:53:03 GMT

I'm getting this error...when i'm running the iginite.
______________

/opt/ignite/bin/make_net_recovery -A -x inc_entire=rootdg -s (Server_name) > /tmp/make_net_recovery_log 2>&1

ERROR: The list_expander command failed. This could be due to a problem with
the -x options specified - Check the existence of the included
device(s).
* Creating NFS mount directories for configuration files.

======= 02/08/09 18:46:02 PST Started /opt/ignite/bin/make_net_recovery. (Sun
Feb 08 18:46:02 PST 2009)
@(#)Ignite-UX Revision C.7.6.100
@(#)ignite/net_recovery (opt) Revision:
/branches/IUX_RA0806/ignite/src@73644 Last Modified: 2008-04-15
17:21:10 -0600 (Tue, 15 Apr 2008)

* Testing for necessary pax patch.
* Checking Versions of Recovery Tools

======= 02/08/09 18:46:03 PST make_net_recovery completed unsuccessfully

______________
OS Info -> B.11.23 U ia64
For Reference -> # what `whence ignite`
/opt/ignite/bin/ignite:
ignite/headers $Revision: 72278 $ $Date: 2007-11-20 16:01:38 -0700 (Tue, 20 Nov 2007) $
Ignite-UX Revision C.7.6.100
ignite/ignite user interface (opt) Revision: /branches/IUX_RA0806/ignite/src@73644 Last Modified: 2008-04-15 17:21:10 -0600 (Tue, 15 Apr 2008)

Re: Ignite error

Patrice Le Guyader — Mon, 09 Feb 2009 12:28:11 GMT

Hello,

Are you sure to have your system disk with this name "rootdg " and not as usually vg00 ?

try a bdf to control your mount point and if so change you volume group name for vg00.

If you're really not using logical volume manager try by replacing rootdg by the block device file of your disk.

Hope this help.
Kenavo
Pat.

Re: Ignite error

Ganesan R — Mon, 09 Feb 2009 12:47:16 GMT

Hi Karthik,

Just for confirmation, Are you sure you have any vg called "rootdg"?. Normally this naming convention used to be vxvm.

Re: Ignite error

likid0 — Thu, 12 Feb 2009 07:33:11 GMT

Normaly list_expander errors are beacuse of you have a bad entry in your /etc/fstab file, check out your fstab is consistent(all lvols exist, all mount points exist, etc ..)

You can manually launch list_expander and check the error:

/opt/ignite/lbin/list_expander

also check with vgdisplay if your root vg is actually rootdg and you are using veritas

vgdisplay -v /dev/rootdg