What wrong with this configuration

[Ihab Zaki]

lvlnboot -v


Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c0t5d0 (8/0.5.0)
/dev/dsk/c0t6d0 (8/0.6.0) -- Boot Disk
/dev/dsk/c1t5d0 (8/4.5.0)
/dev/dsk/c1t6d0 (8/4.6.0)
Boot: lvol1 on: /dev/dsk/c0t6d0
Root: lvol3 on: /dev/dsk/c0t6d0
Swap: lvol2 on: /dev/dsk/c0t6d0
Dump: lvol2 on: /dev/dsk/c0t6d0, 0

Current path "/dev/dsk/c3t0d1" is an alternate link, skip.
Current path "/dev/dsk/c3t0d2" is an alternate link, skip.
Current path "/dev/dsk/c3t0d3" is an alternate link, skip.
Current path "/dev/dsk/c3t0d0" is an alternate link, skip.

[Tom Danzig]

Nothing really unless you expect to have more that one bootable disk.

If dev/dsk/c0t5d0 (8/0.5.0) is a root mirror (or any of the others are), they are not boot disks. You need to use pvcreate -B and the makeboot command to make it bootable.

You cannot do this after the fact. The root disk mirror process will have to be repeated after removing the disk from the root VG.

[Tom Danzig · Accepted solution]

Should have been clearer - the makeboot command is actually mkboot.

[Steven E. Protter]

Nothing.

You seem to be booting off your second disk on controller 0. Thats a little unusual, but not outlandish.

If you are expecting a mirror setup, here is a procedure that will help with that.

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

It seems that you have alternate links disk failover configured, but thats a good thing too.

SEP