Operating System - HP-UX
1833873 Members
4419 Online
110063 Solutions
New Discussion

LIF information corrupt or not present after installing Mirrordisk/UX

 
SOLVED
Go to solution
Clay Combs
Occasional Advisor

LIF information corrupt or not present after installing Mirrordisk/UX

How can I resolve an error message after installing Mirrordisk/UX when mirroring logical volumes in SAM:

lvlnboot: LIF information corrupt or not present on â /dev/dsk/c2t4d0â . Use the â mkbootâ command to initialize the LIF area.


I have a K570 running HP-UX 10.20 with 4 internal drives.

# ioscan -fnC disk
Class I H/W Path Driver S/W State H/W Type Description
======================================================================
disk 0 8/0.0.0 sdisk CLAIMED DEVICE HP C5447A
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
disk 1 8/0.0.1 sdisk CLAIMED DEVICE HP C5447A
/dev/dsk/c0t0d1 /dev/rdsk/c0t0d1
disk 2 8/4.1.0 sdisk CLAIMED DEVICE HP C5447A
/dev/dsk/c1t1d0 /dev/rdsk/c1t1d0
disk 3 8/4.1.1 sdisk CLAIMED DEVICE HP C5447A
/dev/dsk/c1t1d1 /dev/rdsk/c1t1d1
disk 4 10/0.3.0 sdisk CLAIMED DEVICE SEAGATE ST39175LC
/dev/dsk/c2t3d0 /dev/rdsk/c2t3d0
disk 5 10/0.4.0 sdisk CLAIMED DEVICE SEAGATE ST39175LC
/dev/dsk/c2t4d0 /dev/rdsk/c2t4d0
disk 6 10/0.5.0 sdisk CLAIMED DEVICE SEAGATE ST39173WC
/dev/dsk/c2t5d0 /dev/rdsk/c2t5d0
disk 7 10/0.6.0 sdisk CLAIMED DEVICE SEAGATE ST19171W
/dev/dsk/c2t6d0 /dev/rdsk/disk_query
/dev/rdsk/c2t6d0
disk 8 10/12/5.2.0 sdisk CLAIMED DEVICE PIONEER DVD-ROM DVD-30
3
/dev/dsk/c3t2d0 /dev/rdsk/c3t2d0

Vg00 contained all 4 physical disks in the beginning. 2 disks did not have any data on them: c2t5d0 and c2t6d0. I removed c2t5d0 from vg00 then:

pvcreate â B /dev/rdsk/c2t5d0
vgextend /dev/vg00 /dev/dsk/c2t5d0
mkboot /dev/rdsk/c2t5d0
mkboot â a â hpux (;0)/stand/vmunixâ /dev/rdsk/c2t5d0
mkboot â a â hpux â lq /stand/vmunixâ /dev/rdsk/c2t5d0
lvextend â m 1 /dev/vg00/lvol1 /dev/dsk/c2t5d0
lvextend â m 1 /dev/vg00/lvol2 /dev/dsk/c2t5d0
# lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c2t3d0 (10/0.3.0) -- Boot Disk
/dev/dsk/c2t4d0 (10/0.4.0)
/dev/dsk/c2t5d0 (10/0.5.0) -- Boot Disk
/dev/dsk/c2t6d0 (10/0.6.0)
Boot: lvol1 on: /dev/dsk/c2t3d0
Root: lvol3 on: /dev/dsk/c2t3d0
Swap: lvol2 on: /dev/dsk/c2t3d0
/dev/dsk/c2t5d0
Dump: lvol2 on: /dev/dsk/c2t3d0, 0

Current path "/dev/dsk/c1t1d0" is an alternate link, skip.
Current path "/dev/dsk/c1t1d1" is an alternate link, skip.

Then from SAM I increased the number of mirror copies on the remaining logical volumes. After the mirror is created I get the error message:

lvlnboot: LIF information corrupt or not present on â /dev/dsk/c2t4d0â . Use the â
7 REPLIES 7
A. Clay Stephenson
Acclaimed Contributor

Re: LIF information corrupt or not present after installing Mirrordisk/UX

Your message is badly garbled but it looks as though you have an extra mkboot. Also, make sure that you use -B with pvcreate; I just can't tell from your output.

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


You should also do an lvextend -m 1 for lvol3. It is important that the first three LVOL's be mirrored in order. I would put all of the lvextends inside your script and not use SAM. This is a case where exact order (at least for the first 3) counts.
If it ain't broke, I can fix that.
Lorenzo Facello
Valued Contributor

Re: LIF information corrupt or not present after installing Mirrordisk/UX

sure,
you have to mirror also lvol3...
take a look to this document.
Hope this helps
L.
Clay Combs
Occasional Advisor

Re: LIF information corrupt or not present after installing Mirrordisk/UX

Hopefully this Word document will not be garbled. I will attempt the process again from the beginning with your suggestions.
Lorenzo Facello
Valued Contributor
Solution

Re: LIF information corrupt or not present after installing Mirrordisk/UX

Hi,
I put some correction on the document (look the <--)
and I also add a little part at the end.
Regds
L.
Lorenzo Facello
Valued Contributor

Re: LIF information corrupt or not present after installing Mirrordisk/UX

... preserve this document
May be useful...
L.
Steven E. Protter
Exalted Contributor

Re: LIF information corrupt or not present after installing Mirrordisk/UX

A complete procedure from disk create to final step for mirroring a boot disk.

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

Check your steps, perhaps start over.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Clay Combs
Occasional Advisor

Re: LIF information corrupt or not present after installing Mirrordisk/UX

Thanks a bundle gentlemen. If the following comes out garbled I attached a text copy. I removed the mirrors I created then started over at the mkboot -a command:

mkboot -a "hpux -lq (;0)/stand/vmunix" /dev/rdsk/c2t5d0
lvextend â m 1 /dev/vg00/lvol1 /dev/dsk/c2t5d0
lvextend â m 1 /dev/vg00/lvol2 /dev/dsk/c2t5d0
lvextend â m 1 /dev/vg00/lvol3 /dev/dsk/c2t5d0
lvlnboot -b /dev/vg00/lvol1
lvlnboot -v -r /dev/vg00/lvol3
lvlnboot -s /dev/vg00/lvol2
lvlnboot -R /dev/vg00
lvlnboot -v

# lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c2t3d0 (10/0.3.0) -- Boot Disk
/dev/dsk/c2t4d0 (10/0.4.0)
/dev/dsk/c2t5d0 (10/0.5.0) -- Boot Disk
/dev/dsk/c2t6d0 (10/0.6.0)
No Boot Logical Volume configured
Root: lvol3 on: /dev/dsk/c2t3d0
/dev/dsk/c2t5d0
Swap: lvol2 on: /dev/dsk/c2t3d0
/dev/dsk/c2t5d0
Dump: lvol2 on: /dev/dsk/c2t3d0, 0

Current path "/dev/dsk/c1t1d0" is an alternate link, skip.
Current path "/dev/dsk/c1t1d1" is an alternate link, skip.

I noticed the "No Boot Logical Volume configured" and issued again:
lvlnboot -b /dev/vg00/lvol1

# lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c2t3d0 (10/0.3.0) -- Boot Disk
/dev/dsk/c2t4d0 (10/0.4.0)
/dev/dsk/c2t5d0 (10/0.5.0) -- Boot Disk
/dev/dsk/c2t6d0 (10/0.6.0)
Boot: lvol1 on: /dev/dsk/c2t3d0
/dev/dsk/c2t5d0
Root: lvol3 on: /dev/dsk/c2t3d0
/dev/dsk/c2t5d0
Swap: lvol2 on: /dev/dsk/c2t3d0
/dev/dsk/c2t5d0
Dump: lvol2 on: /dev/dsk/c2t3d0, 0

Current path "/dev/dsk/c1t1d0" is an alternate link, skip.
Current path "/dev/dsk/c1t1d1" is an alternate link, skip.

Created the remaining lvol mirrors with SAM with n