LIF

[Waugh]

Hi ,

Suppose lif is corrupted on disk . how to recover it.

regards
Rkumar

[Analyst]

Hi Rkumar,

Please check the link.

http://forums11.itrc.hp.com/service/forums/questionanswer.do?admit=109447626+1230129069179+28353475&threadId=514082

http://forums13.itrc.hp.com/service/forums/questionanswer.do?threadId=1277959.

[Matti_Kurkela]

I assume you mean the boot LIF in the beginning of the disk. Correct?

First it would be a good idea to find out why the LIF is corrupted.

A common reason would be running the "pvcreate" command without the -B option. If this has happened, just rewriting the boot LIF would overwrite and corrupt the first filesystem on the disk. In this case, you must make the disk free again (= un-mirror the vg00 filesystems and vgreduce the disk out of vg00) and then re-run pvcreate using the -B option and re-mirror.

You can use the "mkboot" command to re-write the boot LIF.

mkboot /dev/rdsk/

Then use "mkboot -a" to set the boot string to the correct value. Usually it is "hpux -lq" for mirrored system disk, "hpux" for non-mirrored one. For vPar systems, use "hpux /stand/vpmon".

If you have a disk with a non-corrupt boot LIF, you can display the current boot string with:

lifcp /dev/dsk/:AUTO -

If your standard setup includes having the Offline Diagnostics package on the boot LIF, you will have to re-install it too.

The command for 64-bit systems:
mkboot -b /usr/sbin/diag/lif/updatediaglif2 -p ISL -p AUTO -p HPUX -p PAD -p LABEL /dev/rdsk/

For 32-bit systems, replace "updatediaglif2" with "updatediaglif".

MK

[Waugh]

Hi,

Suppose i m using only one command
#mkboot -l /dev/rdsk/c1t1d0
it will solve the problem or not

Reagrds
Rkumar

[Analyst]

You can use the "mkboot" command to re-write the boot LIF.

mkboot /dev/rdsk/


Yes It Should solve your problem.

goahead.

[Matti_Kurkela]

There are two problems with your single-command fix:

1.) If you don't make sure the boot string is correct, you may have additional problems.
- The system may remain in the ISL> boot prompt instead of booting automatically, if the default boot string is not correct.
- If vg00 is mirrored and "hpux -lq" is not used, your system may not restart automatically if there is a system disk failure.
- If this a vPar system, it will boot into non-vPar mode after a full system reset, instead of starting vpmon and then running all the configured vPars.

If this is a High-Availability system, all these things can cause you to break the SLA mandated by your customer, because the system will not automatically recover from problems as expected.

2.) If the root cause of LIF corruption was the use of pvcreate without the -B option, running the mkboot -l command will repair the boot LIF but will corrupt the /stand filesystem. The machine will still be unbootable, but for a different reason. In this situation, recovering /stand will corrupt the LIF again. Only fixing the root cause will help.

This is because the boot LIF and the /stand filesystem will both attempt to occupy the same place at the beginning of the disk, unless pvcreate is instructed to leave some space for the boot LIF (=using the "pvcreate -B").

MK