topic Make_recovery errror in Operating System - HP-UX

Make_recovery errror

Ramesh_1 — Thu, 26 Sep 2002 06:37:52 GMT

Hi ,

I had installed ignite-ux on a D210 server runnig on HP-UX 10.20. I ran the following command:
- make_recovery -A -v -d /dev/rmt/0m.

lifinit: can not create /usr/lib/ignite_bootlif
WARNING: LIF volume for bakup cannot be created.

The rest of the job went fine.
But is the tape bootable ?

Thanx in advance

Cheers,
Ramesh

Re: Make_recovery errror

Donald Kok — Thu, 26 Sep 2002 06:49:56 GMT

There is an issue about one ignite release of this year, concerning the lif-failure. You can check for patches, or download the correct version.

Re: Make_recovery errror

Animesh Chakraborty — Thu, 26 Sep 2002 06:51:16 GMT

Hi,
make_*_recovery is calling
make_sys_image -L to make a copy of the current state of the lif on your boot disk. This call is resulting in a non-zero return code.

The "-L" option from man page:
-L Create a copy of any non-standard LIF files (as
defined for both whole and LVM disks) found on the
boot disk. The boot disk that is used is taken
from the first non-commented line in the
/stand/bootconf file. The LIF volume for storing
these LIF files is /usr/lib/ignite_bootlif and it
is only created if non-standard LIF files are
present. This option only creates the back-up
file. Without this option the back-up, if needed,
is created and the recovery media is created with
this information stored for later recovery. For
more information on the disks, LIF files, and LIF
volume creation, see bootconf(4), lif(4),
mkboot(1M), and lifinit(1). The main purpose of
this option is to allow LIF diagnostics and any
changes to the AUTO LIF file to be saved by the
Ignite-UX recovery commands, see make_recovery(1M)
and make_net_recovery(1M).
====================

You can get a non-zero exit code if the "lifcp" fails, or if the disk listed in /stand/bootconf doesn't exist or doesn't contain a lif header. Other possibilities are running out of space on the filesystem when making the backup copy of the lif.

You can try running the make_sys_image -L command by hand and seeing if any additional messages show up.

Re: Make_recovery errror

Ramesh_1 — Mon, 30 Sep 2002 03:08:38 GMT

Hi,

The OS on the server has been hardened and the /usr is mounted Read Only.
So it could be the RO mount option that has caused the failure to create the file.

Thanx

Cheers
Ramesh

Re: Make_recovery errror

Andi Rigauer — Wed, 02 Oct 2002 11:49:56 GMT

Hi,

Try to make an swlist -l fileset | grep -i ignite. Do you have different versions running? Are you using Sevice Control Manager?

BRGDS
ANDI

Re: Make_recovery errror

john korterman — Wed, 02 Oct 2002 12:08:25 GMT

Hi Ramesh,
this has probably nothing to do with the errors you get, but even if you had got no errors the tape would not be bootable: you have to use the NON-rewinding device
/dev/rmt/0mn

regards,
John K.

Re: Make_recovery errror

Ramesh_1 — Wed, 02 Oct 2002 23:21:57 GMT

Hi,

It's fine now.
The error msg disappeared after changing the mount options.
Now I need to restore the make_recovery tape onto another machine. Wish me luck

Cheers,
Ramesh