Error - The command "lvlnboot -v vg00" returned 126.

[Prasanth Thomas]

Hi All,
Could you please assist on the below issue. when i executing the make_net_recovery iam getting the below error. i have verified the vg00 and file permissions everything looking fine. Please find the below error.
-------
# gap.fr.infores.com:root /# make_net_recovery -s bayonneo -a bayonneo:/var/opt/ignite/recovery/archives/gap -AvI ->
# gap.fr.infores.com:root /# var/opt/ignite/recovery/archives/gap -AvI -x inc_entire=/dev/vgxg1 <
* Creating NFS mount directories for configuration files.
* Recovery Archive Name = 2009-12-14,15:47

* Lanic Id = 0x00306E0636C6

* Ignite-UX Server = bayonneo


======= 12/14/09 15:47:09 MET Started make_net_recovery. (Mon Dec 14 15:47:09 MET 2009)
@(#)Ignite-UX Revision C.7.8.201
@(#)ignite/net_recovery (opt) Revision: /branches/IUX_RA0903/ignite/src@76987 Last Modified: 2009-02-05 15:45:55
-0700 (Thu, 05 Feb 2009)

* Recovery Archive Description = Recovery Archive

* Recovery Archive Location = bayonneo:/var/opt/ignite/recovery/archives/gap

* Number of Archives to Save = 2

* Pax type = tar


In? dsk/vg name minor# Associated disks/mountpoints
0 v /dev/vg00 0x00 /dev/dsk/c1t0d0 /dev/dsk/c1t2d0
0 v /dev/vgxg1 0x02 /dev/dsk/c4t0d0 /dev/dsk/c4t0d1

** 0 - The Volume Group or Filesystem is Not included in the
System Recovery Archive
** 1 - The Volume Group or Filesystem is Partially included in the
System Recovery Archive
** 2 - The Volume Group or Filesystem is Fully included in the
System Recovery Archive

* Checking Versions of Recovery Tools
* Scanning system for IO devices...
* Boot device is: 0/0/1/1.2.0
* Creating System Configuration.
* /opt/ignite/bin/save_config -f
/var/opt/ignite/recovery/client_mnt/0x00306E0636C6/recovery/2009-12-14,15:47/system_cfg
save_config: Error - The command "lvlnboot -v vg00" returned 126. If needed, the command "vgscan -v " can be used to recreate the "/etc/lvmtab" file. The lvlnboot error output is: /opt/ignite/bin/save_config: lvlnboot: Execute permission denied.
ERROR: /opt/ignite/bin/save_config failed

======= 12/14/09 15:47:18 MET make_net_recovery completed unsuccessfully
-----------------------------------------

# gap.fr.infores.com:root /#
# gap.fr.infores.com:root /# lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c1t0d0 (0/0/1/1.0.0) -- Boot Disk
/dev/dsk/c1t2d0 (0/0/1/1.2.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c1t0d0
/dev/dsk/c1t2d0
Root: lvol3 on: /dev/dsk/c1t0d0
/dev/dsk/c1t2d0
Swap: lvol2 on: /dev/dsk/c1t0d0
/dev/dsk/c1t2d0
Dump: lvol2 on: /dev/dsk/c1t0d0, 0

# gap.fr.infores.com:root /# lanscan
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
0/0/0/0 0x00306E0636C6 0 UP lan0 snap0 1 ETHER Yes 119
0/3/0/0 0x00306E042182 2 UP lan2 snap2 2 ETHER Yes 119
0/4/0/0 0x001083F65F8F 1 UP lan1 snap1 3 ETHER Yes 119
# gap.fr.infores.com:root /#
---------------------------------------------
Regards,
Prasanth Thomas.

[Scot Bean]

make_net_recovery cannot see your vg00

Just a guess, but perhaps the target machine is setup with an LVM2 filesystem? If so, Ignite does not support that format at this time.

[Prasanth Thomas]

Hi Scot
Many Thanks for your reply.But one week back it was running successfully and we did not changed anything on ignite clinet and ignite server. I have verified with same version of server but its giving the same error.

Regards,
Prasanth Thomas.

[VK2COT]

Hello,

Error 126 is related to:

#define EPOWERF 126

It happens when an I/O times out. Generic
"power failed" message means that the disk
stopped responding to SCSI commands.

In case of HP-UX it can also happen when an
LVM operation is not completed within the
specified PV timeout (30 secs by default).

a) Check your hardware for intermittent
problems;

b) Maybe a longer PV timeout is worth
setting;

Cheers,

VK2COT

[Prasanth Thomas]

Hi,

The pv timeout set as default and i didnot see any stale value too.

Regards,
Prasanth Thomas.

[VK2COT]

Then increase the PV timeout value and
also check your hardware.

Do you have any issue with UNCLAIMED, NO_HW
and other types of bad devices?

Regards,

VK2COT

[Prasanth Thomas]

Hi ,

I have resolved this issue by copying the binary for lvlnboot, vgdisplay and lvdisplay from another server.

Thanks,
Prasanth Thomas.