root mirror issue

 
SOLVED
Go to solution
Mark McDonald_2
Trusted Contributor

root mirror issue

Hi

I am doing an audit of some old HPUX machines that we have inherited.

lvlnboot shows:
# lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c2t1d0 (0/1/1/0.1.0) -- Boot Disk
/dev/dsk/c2t0d0 (0/1/1/0.0.0)
.
.
.

setboot is correct:
Primary bootpath : 0/1/1/0.1.0
Alternate bootpath : 0/1/1/0.0.0


lvdisplay -v - shows each root lv mirrored from c2t1d0 to c2t0d0


Why does the lvlnboot not show the 2nd disk as --boot?

Also I have noticed the usual boot files missing from lifls on the Alternate disk. I initially tried to copy these across with lifcp but got no space error.

I suspect the -B was missed on the pvcreate or mkboot was missed, but not sure which?

What is my best way to sort this out?

Currently I think the best option is to lv+vgreduce then start from scratch with pvcreate -fB.
18 REPLIES 18
sujit kumar singh
Honored Contributor

Re: root mirror issue

Hello


U can give the command as following to check if the other disk is alos bootable


#vgcfgrestore -l -n vg00
Volume Group Configuration information in "/etc/lvmconf/vg00.conf"
VG Name /dev/vg00
---- Physical volumes : 1 ----
/dev/rdisk/disk3_p2 (Bootable)

This will tell u all the disks in the VG that are bootable.

however in ur scenario as the O/P shows,

# lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c2t1d0 (0/1/1/0.1.0) -- Boot Disk
/dev/dsk/c2t0d0 (0/1/1/0.0.0)


the boot disk is the dosk that the system has bppted the Kernel or the OS on the last boot.

regards

Sujit



sujit kumar singh
Honored Contributor

Re: root mirror issue

hello



if u suspect that the pvcreate -B option was not used for the other disk in the option u can try reading the boot area information of the disk or the autofile content using the following command on a PARISC platform:

1)
#lifls -l /dev/rdsk/c2t0d0
this shows the boot related files present in the LIF area of the disk.

2)
#lifcp /dev/rdsk/c2t0d0:AUTO -

this will copy the contents of the auto file to the stdout that is ur console display and if the AUTO file is present as u can see in the O/P of the last command , u can see the auto strinf stored in the AUTO file in the LIF area of the disk.


So if u find both these things and also as in the previous post the O/P for the command
#vgcfgrestore -l -n /dev/vg00

get tsure that the otehr disk is also bootable and the lvlnboot -v showsthe current boot disk information.

Regards
Sujit
Mark McDonald_2
Trusted Contributor

Re: root mirror issue

# vgcfgrestore -l -n vg00
Volume Group Configuration information in "/etc/lvmconf/vg00.conf"
VG Name /dev/vg00
---- Physical volumes : 2 ----
/dev/rdsk/c2t1d0 (Bootable)
/dev/rdsk/c2t0d0 (Non-bootable)


The lifls tells me the files are missing.
likid0
Honored Contributor

Re: root mirror issue

If that's the case the best thing you can do is completly redo the mirror.

lvextend -m 0 /dev/vg00/lvolx /dev/dsk/c2t0d0
vgreduce /dev/vg00 /dev/dsk/c2t0d0

And then start again, but this time with the pvcreate -B

Windows?, no thanks
Mark McDonald_2
Trusted Contributor

Re: root mirror issue

Thanks, thats what I expected - home time now, I will leave the thread open until tomorrow incase anyone else has any input.
sujit kumar singh
Honored Contributor

Re: root mirror issue

Hi


Yes this is suggested that u do whole of the pvcreate -B and do the whole of the miroring of all the LVs in there.
as u also told that LIF area is not having any files in there.

# lifls -l /dev/rdisk/disk3_p2
volume ISL10 data size 7984 directory size 8 08/06/27 23:56:28
filename type start size implement created
===============================================================
ISL -12800 584 242 0 08/06/27 23:56:28
AUTO -12289 832 1 0 08/06/27 23:56:28
HPUX -12928 840 1024 0 08/06/27 23:56:28
PAD -12290 1864 1468 0 08/06/27 23:56:28
LABEL BIN 3336 8 0 98/01/01 00:17:20

can u see any of the files as listed in there in the lifls -l display?

If u have not an LIF area in there only option is to do a pvcreate -B and do mirroring all over.




and yes to remove the mirrors of the LV from that disk make sure that u use the command for all the LVs on that disk as

#lvreduce -m 0 /dev/vg00/lvol1 /dev/dsk/c2t0d0


and so on.

after that make sure that u do
#vgreduce /dev/vg00 /dev/dsk/c2t0d0
#lvlnboot -R
#lvlnboot -v

then again

#pvcreate -f /dev/rdsk/c2t0d0
#pvcreate -B /dev/rdsk/c2t0d0
#vgextend /dev/vg00 /dev/dsk/c2t0d0
#mkboot -l /dev/rdsk/c2t0d0
#mkboot -a "hpux /stand/vmunix -lq" /dev/rdsk/c2t0d0


Then follow the mirroring for all the LVs in the VG as

#lvextend -m 1 /dev/vg00/lvol1 /dev/dsk/c2t0d0

Repeat this for all the LVs, This can take take a lot of time.

#lvlnboot -R /dev/vg00
#lvlnboot -v

to check that u have the Second disk also included again in there.

#vi /stand/bootconf to put the entry of that disk as


l /dev/rdsk/c2t0d0


this is l that is SMALL L and NOT 1


then u have done the necessary things done


also make sure that u have the syatem setboot alternate path pointing to this disk


#setboot -a
#setboot

to see that the boot path is set properly


Regards

Sujit


check that this disk is set
Mark McDonald_2
Trusted Contributor

Re: root mirror issue

Thanks - as I stated at the top setboot is correct.

Also:
lifls is only showing the LABEL
and lifcp returns with outofspace.

Does this mean that pvcreate did have the -B option?
sujit kumar singh
Honored Contributor

Re: root mirror issue

Hi


Can u try giving the following command on the disk as:


#mkboot -a "hpux /stand/vmunix -lq" /dev/rdsk/c2t0d0

and after that can u give the O/P of the command
#lifls -l /dev/rdsk/c2t0d0
#lifcp /dev/rdsk/c2t0d0:AUTO -
#vgcfgrestore -l -n vg00

the effort to do an mkboot is not going to harm the existing LVM structre on the disk


Regards

Sujit
Mark McDonald_2
Trusted Contributor

Re: root mirror issue

# mkboot -a "hpux /stand/vmunix -lq" /dev/rdsk/c3t15d0
There appear to be non-boot logical volumes on this device.
Overwriting them could destroy all the data on this device
Should the logical volumes be overwritten [y/n]?


Seems a bit risky without a change in place!!!