lvlnboot -v does not display c0t1d0 root mirror as " -- Boot Disk"

[paul cummings]

lvlnboot should show c0t1d0 as "-- Boot Disk" but it doesn't.
# lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c4t6d0 (10/0.6.0) -- Boot Disk
/dev/dsk/c0t1d0 (8/0.1.0)
Boot: lvol1 on: /dev/dsk/c4t6d0
/dev/dsk/c0t1d0
Root: lvol3 on: /dev/dsk/c4t6d0
/dev/dsk/c0t1d0
Swap: lvol2 on: /dev/dsk/c4t6d0
/dev/dsk/c0t1d0
Dump: lvol2 on: /dev/dsk/c4t6d0, 0
Dump: lvol4 on: /dev/dsk/c4t6d0, 1

Yet, lifls tells you it has what it needs?# lifls -l /dev/rdsk/c0t1d0
volume c0t1d0 data size 7984 directory size 8 03/06/16 18:54:11
filename type start size implement created
===============================================================
ISL -12800 584 240 0 96/05/28 04:10:13
AUTO -12289 824 1 0 96/05/28 04:10:13
HPUX -12928 832 848 0 96/05/28 04:10:13
PAD -12290 1680 1652 0 96/05/28 04:10:14
LABEL BIN 3336 8 0 03/06/17 12:26:05

[Michael Steele_2]

What is :

lifcp /dev/rdsk/c0t1d0:AUTO -

-and-

strings /etc/lvmtab

Does the disk respond?

dd if=/dev/dsk/c0t1d0 of=/dev/null count=1000000

diskinfo /dev/rdsk/c0t1d0

[Michael Steele_2]

lvlnboot -R

-R Recover any missing links to all of the logical volumes specified in the Boot Data Reserved Area and update the Boot Data Reserved Area of each bootable physical volume in the volume group (see pvcreate(1M) ).

[paul cummings]

I assume you mean the output of the following command...
# lifcp /dev/rdsk/c0t1d0:AUTO -

hpux -lq

# strings /etc/lvmtab
/dev/vg00
/dev/dsk/c4t6d0
/dev/dsk/c0t1d0
/dev/vg03
/dev/dsk/c0t5d2
/dev/dsk/c1t0d2
/dev/vg01
/dev/dsk/c0t2d0
/dev/vgdata1
/dev/dsk/c2t2d0
/dev/dsk/c3t4d0
/dev/vgdata2
/dev/dsk/c2t2d1
/dev/dsk/c3t4d1
/dev/vgdb1
/dev/dsk/c2t3d0
/dev/dsk/c3t5d0
/dev/vgdb2
/dev/dsk/c2t3d1
/dev/dsk/c3t5d1
/dev/vgdb3
/dev/dsk/c1t0d1
/dev/dsk/c0t5d1
/dev/vgquest1
/dev/dsk/c0t3d0
/dev/dsk/c1t3d0
/dev/vgklarity1
/dev/dsk/c0t4d0
/dev/dsk/c1t4d0#

dd if=/dev/dsk/c0t1d0 of=/dev/null count=1000000

17909+0 records in
17908+0 records out

# diskinfo /dev/rdsk/c0t1d0
SCSI describe of /dev/rdsk/c0t1d0:
vendor: SEAGATE
product id: ST39173WC
type: direct access
size: 8891556 Kbytes
bytes per sector: 512

# lvlnboot -R /dev/vg00
Volume Group configuration for /dev/vg00 has been saved in /etc/lvmconf/vg00.conf

# lvlnboot -v /dev/vg00
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c4t6d0 (10/0.6.0) -- Boot Disk
/dev/dsk/c0t1d0 (8/0.1.0)
Boot: lvol1 on: /dev/dsk/c4t6d0
/dev/dsk/c0t1d0
Root: lvol3 on: /dev/dsk/c4t6d0
/dev/dsk/c0t1d0
Swap: lvol2 on: /dev/dsk/c4t6d0
/dev/dsk/c0t1d0
Dump: lvol2 on: /dev/dsk/c4t6d0, 0
Dump: lvol4 on: /dev/dsk/c4t6d0, 1

[Michael Steele_2]

Issue:

mkboot /dev/dsk/c0t1d0

-and-

mkboot -a "hpux -lq" /dev/rdsk/c0t1d0

-or-

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

[Michael Steele_2]

If fails:

# vgcfgrestore -n vg00 /dev/rdsk/c0t1d0
# vgchange -a y vg00
# vgsync vg00

[paul cummings]

Already did the mkboots before. the 1st command using -l. Also already tried the second mkboot -a command you list. re: the 3rd command, I thought there was a 10 character limit on the quoted string? And what is the real difference between command 2 and command 3?

[James R. Ferguson]

Hi:

If 'lvlnboot -v' fails to show a disk as a "boot disk" it isn't for the reason that it was not 'pvcreate'd correctly. That is, no 'pvcreate -B' was done for the disk in question.

Start over. 'vgreduce' the physical volume out of the volume group and begin anew with a 'pvcreate -B'...

Regards!

...JRF...

[paul cummings]

The instructions I was using listed the pvcreate -B -f. Pretty sure I did that, But I'll re-do as suggested just to make sure!

BTW, the vg commands in the 2 replies back did not help.

[Michael Steele_2]

Tells 'hpux' to substitute the HW path to the disk, find and load the kernel, /stand/vmunix.

Its mostly obsolete but is more complete then relying upon hpux to make the correct substitutions.

So at this point, pvcreate -B and start over.

[paul cummings]

As suggested I started over and I did the following steps and lvlnboot -v now shows what I want to see! Now I just have root mirror will boot up on it's own. I'm lvreducing/vgreducing the root in prep for o.s. patch cluster so I want to have a pre-patch root disk to fall back on if there's a problem with the upgrade. Here's what I did.

lvreduced all vg00 lvols
vgreduce vg00

# pvcreate -f -B /dev/rdsk/c0t1d0

# mkboot -l /dev/rdsk/c0t1d0 (which created LIF files!!)

# lifls -v /dev/rdsk/c0t1d0
ISL 1
AUTO 1
HPUX 1
PAD 1
LABEL 1
# mkboot -a "hpux -lq" /dev/rdsk/c0t1d0

# lifcp /dev/rdsk/c0t1d0:AUTO-

# lifls -lv /dev/rdsk/c0t1d0
volume ISL10 data size 7984 directory size 8 96/05/28 04:10:13
filename type start size implement created
===============================================================
ISL -12800 584 240 0 96/05/28 04:10:13
AUTO -12289 824 1 0 96/05/28 04:10:13
HPUX -12928 832 848 0 96/05/28 04:10:13
PAD -12290 1680 1652 0 96/05/28 04:10:14
LABEL BIN 3336 8 0 03/06/17 15:41:38

# vgextend /dev/vg00 /dev/dsk/c0t1d0
Volume group "/dev/vg00" has been successfully extended.
Volume Group configuration for /dev/vg00 has been saved in /etc/lvmconf/vg00.conf

# lvextend -m 1 /dev/vg00/lvol1 /dev/dsk/c0t1d0
The newly allocated mirrors are now being synchronized. This operation will
take some time. Please wait ....
Logical volume "/dev/vg00/lvol1" has been successfully extended.
Volume Group configuration for /dev/vg00 has been saved in /etc/lvmconf/vg00.conf
did the same for lvol2-->lvol10
# lvlnboot -r /dev/vg00/lvol3 /dev/vg00
Volume Group configuration for /dev/vg00 has been saved in /etc/lvmconf/vg00.conf
# lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c4t6d0 (10/0.6.0) -- Boot Disk
/dev/dsk/c0t1d0 (8/0.1.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c4t6d0
/dev/dsk/c0t1d0
Root: lvol3 on: /dev/dsk/c4t6d0
/dev/dsk/c0t1d0
Swap: lvol2 on: /dev/dsk/c4t6d0
/dev/dsk/c0t1d0
Dump: lvol2 on: /dev/dsk/c4t6d0, 0
Dump: lvol4 on: /dev/dsk/c4t6d0, 1

# lvlnboot -b /dev/vg00/lvol1 /dev/vg00
# lvlnboot -s /dev/vg00/lvol2 /dev/vg00
# lvlnboot -d /dev/vg00/lvol2 /dev/vg00
=> Update BDRA (root, boot, swap and dump)
# lvlnboot -v
=> Check to make sure both disks are listed for root, boot and swap definition.
# setboot
=> Display boot path an set the boot path to the desired path with "setboot -a|-p"
# setboot
Primary bootpath : 8/0.1.0
Alternate bootpath : 8/0.1.0

Autoboot is ON (enabled)
Autosearch is ON (enabled)
# setboot -a 10/0.6.0
# setboot
Primary bootpath : 8/0.1.0 (HASS disk)
Alternate bootpath : 10/0.6.0 (internal disk)

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

[paul cummings]

So after setboot -p 8/0.1.0 I think my system may have rebooted on 10/0.6.0. How do I tell which disk I booted from without being at the console terminal when it rebooted?

# lvlnboot -v /dev/vg00
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c4t6d0 (10/0.6.0) -- Boot Disk
/dev/dsk/c0t1d0 (8/0.1.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c4t6d0
/dev/dsk/c0t1d0
Root: lvol3 on: /dev/dsk/c4t6d0
/dev/dsk/c0t1d0
Swap: lvol2 on: /dev/dsk/c4t6d0
/dev/dsk/c0t1d0
Dump: lvol2 on: /dev/dsk/c4t6d0, 0
Dump: lvol4 on: /dev/dsk/c4t6d0, 1

[James R. Ferguson]

Hi Paul:

You can ascertain your last boot path with:

# echo boot_string/S|adb /stand/vmunix /dev/mem

Regards!

...JRF...

[Michael Steele_2]

echo boot_string/S|adb /stand/vmunix /dev/kmem

How's about some points big guy?

[paul cummings]

Actually either of these syntax's worked!

# echo boot_string/S | adb /stand/vmunix /dev/kmem
boot_string:
boot_string: disc(8/0.1.0;0)/stand/vmunix
#
# echo 'boot_string/S' | adb /stand/vmunix /dev/kmem
boot_string:
boot_string: disc(8/0.1.0;0)/stand/vmunix
#

Awesome dudes! It booted from the disk I wanted it to which proves the root mirror can be lvreduced+vgreduced as fall back disk!

Thanx much!
-Paul