make_recovery LIF Error

[MikeL_4]

While running a make_recovery this month I am receiving message:

Option -A specified. Entire Core Volume Group/disk will be backed up.
lifls: Can't list /dev/dsk/c2t5d0; not a LIF volume
WARNING: /dev/dsk/c2t5d0 is not a lif volume.
No LIF files on the boot disk will be archived.
Check /stand/bootconf, man bootconf(4), and /dev/dsk to
make sure that the bootconf file is set up correctly.



***************************************
HP-UX System Recovery
Going to create the tape.
System Recovery Tape successfully created.


What is this telling me and how can I correct it ???

I know last month when the make_recovery was run we didn't get this message..

This is on a 10.20 server...

[S.K. Chan]

Since /stand/bootconf can be hand edited, the obvious thing to check is the content of that file. Mine look like this ..
l /dev/dsk/c2t6d0
The device should be your boot disk path. The first field is lower case L, not number 1. If your bootconf has the wrong boot disk path you can edit and change it, then run make_recovery again and see if it complains.

[Steven E. Protter · Accepted solution]

lvlnboot -v output would be useful here.

Looks like a disk is set up for boot but is missing information.

Is this disk possibily one that's been removed from the system but the driver or other configuration files live on?

Bottom, line is its not an error, its a warning, the tape is good, though if you are anal like me, you might want to see if you can at least boot off it, or recovery it onto a sandbox system.

SEP

[Robert-Jan Goossens]

Hi,

make_net_recovery is receiving warning messages regarding the lif

docid:UIUXKBRC00011961

http://www4.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000067130534

Kind regards,

Robert-Jan.

[S.K. Chan]

A similar thread here ..
http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xf4b2ba808b46d611abda0090277a778c,00.html

[MikeL_4]

Additional Info:

[it05hp] # more /stand/bootconf
# Boot Device configuration file
# This File contains information regarding the location
# of the boot LIF. It is used by the KERN-RUN fileset to
# update the boot kernel.
l /dev/dsk/c2t5d0
[it05hp] #


[it05hp] # lvlnboot -v /dev/vg00
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c2t6d0 (0/28/52.6.0) -- Boot Disk
/dev/dsk/c2t5d0 (0/28/52.5.0)
/dev/dsk/c0t6d0 (0/28/12.6.0) -- Boot Disk
/dev/dsk/c0t5d0 (0/28/12.5.0)
Boot: lvol1 on: /dev/dsk/c2t6d0
/dev/dsk/c0t6d0
Root: lvol3 on: /dev/dsk/c2t6d0
/dev/dsk/c0t6d0
Swap: lvol2 on: /dev/dsk/c2t6d0
/dev/dsk/c0t6d0
Dump: lvol2 on: /dev/dsk/c2t6d0, 0

[MikeL_4]

Additional Info:

[it05hp] # more /stand/bootconf
# Boot Device configuration file
# This File contains information regarding the location
# of the boot LIF. It is used by the KERN-RUN fileset to
# update the boot kernel.
l /dev/dsk/c2t5d0
[it05hp] #


[it05hp] # lvlnboot -v /dev/vg00
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c2t6d0 (0/28/52.6.0) -- Boot Disk
/dev/dsk/c2t5d0 (0/28/52.5.0)
/dev/dsk/c0t6d0 (0/28/12.6.0) -- Boot Disk
/dev/dsk/c0t5d0 (0/28/12.5.0)
Boot: lvol1 on: /dev/dsk/c2t6d0
/dev/dsk/c0t6d0
Root: lvol3 on: /dev/dsk/c2t6d0
/dev/dsk/c0t6d0
Swap: lvol2 on: /dev/dsk/c2t6d0
/dev/dsk/c0t6d0
Dump: lvol2 on: /dev/dsk/c2t6d0, 0

[S.K. Chan]

So what you need is edit /stand/bootconf to contain your pri boot disk ..
l /dev/dsk/c2t6d0
You mirrored disk is c0t6d0. the other 2 PVs that appear in lvlnboot -v are probably because pvcreate -B was run on them. If those 2 PVs are not used and not suppose to be a boot PV, all you need to do is force another pvcreate (without -B) and run ..
# lvlnboot -R
to update the info.

[Michael Steele_2]

Verify your lif with 'lifls' and 'lifcp' commands.

lifls -c /dev/rdsk/c2t5d0
lifls -c /dev/rdsk/c0t6d0

Should see either 6-7 files or 15-16 file if diagnostics are loaded.

lifcp /dev/rdsk/c2t5d0:AUTO -
lifcp /dev/rdsk/c0t6d0:AUTO -
Should see the 'mkboot' string, for example:

"hpux -lq (;0)/stand/vmunix" /dev/rdsk/c2t5d0

For a make_recovery or make_tape_recovery tape, the procedure modifys slightly with 'dd' and 'mt'.

mt -t /dev/rmt/0m rew
mt -t /dev/rmt/0m rew
(* twice for 2 records on tape *)
dd if=/dev/rmt/0mn of=/tmp/lif_file bs=2048
(* Note 0mn for no rewind *)

lifls -C /tmp/lif_file
lifcp /tmp/file_file:AUTO -

[Michael Steele_2]

Verify your lif with 'lifls' and 'lifcp' commands.

lifls -c /dev/rdsk/c2t5d0
lifls -c /dev/rdsk/c0t6d0

Should see either 6-7 files or 15-16 file if diagnostics are loaded.

lifcp /dev/rdsk/c2t5d0:AUTO -
lifcp /dev/rdsk/c0t6d0:AUTO -
Should see the 'mkboot' string, for example:

"hpux -lq (;0)/stand/vmunix" /dev/rdsk/c2t5d0

For a make_recovery or make_tape_recovery tape, the procedure modifys slightly with 'dd' and 'mt'.

mt -t /dev/rmt/0m rew
mt -t /dev/rmt/0m rew
(* twice for 2 records on tape *)
dd if=/dev/rmt/0mn of=/tmp/lif_file bs=2048
(* Note 0mn for no rewind *)

lifls -C /tmp/lif_file
lifcp /tmp/file_file:AUTO -

Read the next record on the tape with tar and you'll have verified your tape successfully for restore.

tar -tvf /dev/rmt/0m