LVM and VxVM

lvlnboot...Boot volume should be the first logical volume

 
SOLVED
Go to solution
derek b smith_1
Regular Advisor

lvlnboot...Boot volume should be the first logical volume

Hi All,

On one of my servers I noticed

# lvlnboot -v vg00
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c4t6d0 (1/0/0/2/0.6.0) -- Boot Disk
/dev/dsk/c6t6d0 (1/0/0/3/0.6.0) -- Boot Disk
/dev/dsk/c2t6d0 (0/0/0/3/0.6.0) -- Boot Disk
No Boot Logical Volume configured
Root: lvol3 on: /dev/dsk/c4t6d0
/dev/dsk/c2t6d0
Swap: lvol2 on: /dev/dsk/c4t6d0
/dev/dsk/c2t6d0
Dump: lvol2 on: /dev/dsk/c4t6d0, 0


# setboot
Primary bootpath : 1/0/0/2/0.6.0
HA Alternate bootpath : 0/0/0/3/1.6.0
Alternate bootpath : 0/0/0/3/0.6.0

Autoboot is ON (enabled)
Autosearch is ON (enabled)

Note: The interpretation of Autoboot and Autosearch has changed for
systems that support hardware partitions. Please refer to the manpage.

root@john [/var/adm/scripts]
# model
9000/800/rp8420
root@john [/var/adm/scripts]
# uname -a
HP-UX john B.11.23 U 9000/800 john unlimited-user license


so I ran a pvdisplay and it DOES show lvol1 as the 1st PEs/LEs

# pvdisplay -v /dev/dsk/c4t6d0 |more
--- Physical volumes ---
PV Name /dev/dsk/c4t6d0
VG Name /dev/vg00
PV Status available
Allocatable yes
VGDA 2
Cur LV 8
PE Size (Mbytes) 16
Total PE 4374
Free PE 1480
Allocated PE 2894
Stale PE 0
IO Timeout (Seconds) default
Autoswitch On
Proactive Polling On

--- Distribution of physical volume ---
LV Name LE of LV PE for LV
/dev/vg00/lvol1 31 31
/dev/vg00/lvol2 1024 1024
/dev/vg00/lvol3 73 73
/dev/vg00/lvol4 312 312
/dev/vg00/lvol5 64 64
/dev/vg00/lvol6 265 265
/dev/vg00/lvol7 625 625
/dev/vg00/lvoltemp 500 500

--- Physical extents ---
PE Status LV LE
00000 current /dev/vg00/lvol1 00000
00001 current /dev/vg00/lvol1 00001
.
.
.

so to fix it, I tried a mkboot -l /dev/dsk/"primary disk", mkboot -a "hpux -lq" ... /dev/rdsk/"primary c#t#d#"
then a lvlnboot -b, -r -s -d then a lvreduce then an lvextend with no success, lvlnboot -v vg00 still shows the above message.

Any ideas?
Thx!!!
5 REPLIES 5
Bijeesh
Respected Contributor

Re: lvlnboot...Boot volume should be the first logical volume

Hi
If you have pv links,reduce it from the VG.
#vgreduce /dev/vg00 /dev/dsk/c?t?d
#lvlnboot -b /dev/vg00/lvol1
#lvlnboot -v
Check for the boot information.
If it showing extend the VG to previous path.

derek b smith_1
Regular Advisor

Re: lvlnboot...Boot volume should be the first logical volume

pvlinks on vg00....no I am using RAID 1.

thx anyway!
chris huys_4
Honored Contributor
Solution

Re: lvlnboot...Boot volume should be the first logical volume

Hi derek,

> so to fix it, I tried a mkboot -
> l /dev/dsk/"primary disk", mkboot -
> a "hpux -lq" ... /dev/rdsk/"primary c#t#d#"
> then a lvlnboot -b, -r -s -d then a
> lvreduce then an lvextend with no success, > lvlnboot -v vg00 still shows the above
> message.

Try.

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

# lvlnboot -Rv

Greetz,
Chris
derek b smith_1
Regular Advisor

Re: lvlnboot...Boot volume should be the first logical volume

That did not work either, the solution from Chris. I got the same message.

Im thinking removing the mirrored disk, running through all the steps, then re-mirroring. If this does not work, reboot with hpux -lm then rerun the lvlnboot steps. Thoughts?
chris huys_4
Honored Contributor

Re: lvlnboot...Boot volume should be the first logical volume

Hi Derek,

Any output while running the above commands ?

bdf ?
parstatus ?
parstatus -w ?
console log output that shows the bootup to multiusermode ?

For the rest log a call with hp support. ;)

Greetz,
Chris