LIF information corrupt or not present on /dev/dsk/c2t1d0

[Randy Martin_2]

Trying to setup Mirror (2 identical disks, mirroring all lvm's/vg00 for DR purposes).
Problem is each time I increase mirror count on a lvm, I get message lvlnboot: LIF information corrupt or not present on /dev/dsk/c2t1d0 Use the mkboot command to initialize the LIF area. If tried this several ways, but nothing seems to prevent this message each time I mirror another lvm. Tried:
1) Remove all mirrors, run mkboot -l /dev/dsk/c2t1d0
2) Run mkboot -l /dev/dsk/c2t1d0 between each mirror
3) Remove all mirrors, remove 2nd drive from vg00, run mkboot, add 2nd drive back to vg00 and increase mirror count.

As you've probably noticed there are no commands other than mkboot documented, that's because everything else was done using SAM.

Thank you in advance for any help you can offer, Randy.

[Steven E. Protter · Accepted solution]

Shalom,

Compare the procedure you used to this:

pvcreate -B /dev/rdsk/c1t0d0 #use real disk

mkboot -l /dev/rdsk/c1t0d0
mkboot -a "hpux -lq (;0)/stand/vmunix" /dev/rdsk/c1t0d0 # use real disk


# mkboot -b /usr/sbin/diag/lif/updatediaglif -p ISL -p AUTO -p HPUX -p PAD -p LABEL /dev/rdsk/c?t?d?

If you are running 64-bit OS:

# mkboot -b /usr/sbin/diag/lif/updatediaglif2 -p ISL -p AUTO -p HPUX -p PAD -p LABEL /dev/rdsk/c?t?d?


vgextend /dev/vg00 /dev/dsk/c1t0d0 # same thing
lvextend -m 1 /dev/vg00/lvol1 /dev/dsk/c1t0d0

# real disk. repeat for other lvols

lvlnboot -r /dev/vg00/lvol3 # root fs /
lvlnboot -s /dev/vg00/lvol2 #swap
lvlnboot -d /dev/vg00/lvol2 #swap/dump
lvlnboot -b /dev/vg00/lvol1
lvlnboot -R
lvlnboot -v
setboot
setboot -a 52.1.0 # second disk

You may have missed something.

SEP

[A. Clay Stephenson]

This is generally a result of not using the -B option of pvcreate which reserves a section of the disk for boot/LIF data.

Man pvcreate for details.

[Denise2]

What if the -B option was not used but a -f (force) instead.  

How do you proceed to fix the LIF message?

Thanks!!

[Torsten.]

Better open your own thread with a detailed description of your issue.

pvcreate -f does ..

Force the creation of a physical volume (thus deleting any file system or volume manager information present) without first requesting confirmation.

Warning: The -f option should only be used as a last resort to over write file system or volume manager information that cannot properly be removed using the commands designed for that purpose. When invoked with -f, the command does minimal verification, so care should be taken to assure that the disk is not already in use prior to invoking the command.