Warning message

[Alex_17]

Hi,

when I check my Ignite log (makrec.log1) I found the following warning:

WARNING: Could not restore LIF volume.

Anybody knows what it means?

Thanks.

Alex.

[Shahul]

Hi

Where U are getting this error? In IU server or client?

Anyway, LIF (Logical Interchange format) is the first part of ur boot HDD. Normally it contains ISL, AUTo, HPUX ...etc utilities.
Ur error shows that it can't recover this area.

Shahul

[Alex_17]

Hi Shaul,

I get the message when I run:
make_recovery -A. The question is: the LIF volume can't be restored, but where?. The Ignite tape is good?.

Thanks.

Alex.

[Alex Glennie]

Make sure the correct disk is defined in the /stand/bootconf file as this is one possible cause for this error ?

[Alex_17]

Hi Alex,

the only line in that file is:

l /dev/dsk/c1t6d0

is this possible? . I think it should appear more entries in the file.

Thanks.

Alex.

[Michael Roberts_3 · Accepted solution]

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.