Mirrored boot drive recovery help

[Gary Glick]

Howdy

Yesterday I had a boot drive fail on one of my HP-UX Servers. It was mirrored with another drive. I was unable to vgreduce the bad disk out. I'm getting:
vgreduce: Couldn't query physical volume "/dev/dsk/c0t5d0":
The specified path does not correspond to physical volume attached to
this volume group.

I've since replaced the failed hard drive & I can't get the VG cleaned up. I did get the lvols cleaned up with lvreduce -m 0 -k 2 /lvol#, but the VG cleanup eludes me.
Worst case, I suppose that I could reload from an ignite tape, of which I have plenty, but I'd rather not take the outage, if I can avoid it.

Thanks for any ideas on how to procede.

[Pete Randall]

Gary,

Here's a great guide:

http://docs.hp.com/en/5991-1236/When_Good_Disks_Go_Bad.pdf


Pete

[Mel Burslan · Accepted solution]

after you replace the disk drive, without vgreduce/vgextend business, you can run

vgcfgrestore -n vg00 /dev/rdsk/cXtXdX

vgchange -a y vg00

then do your normal lvextend -m 1 /dev/vg00/lvol1 ... lvolN

if you had not reduced the lvols, you could simply do a vgsync and you could have been done, but too late now. Nothing major, just more typing (which I absolutely hate)

Hope this helps..

[Raj D.]

Hi Gary ,

After replacing the failed disk ,

1. vgcfgrestore -n /dev/vg00 /dev/rdsk/c0t5d0
2. vgchange -a y /dev/vg00
3. vgsync vg00

should work in this case.

Cheers,
Raj.

[Morcos]

Gary,
After replacing the bad disk:
- vgcfgrestore -n /dev/vg00 /dev/rdsk/cxtxdx
- vgchange -a y /dev/vg00
(if ur failed drive is the boot then
- mkboot /dev/rdsk/cxtxdx ; to create the boot area
- mkboot -a " hpux lq " /dev/rdsk/cxtxdx; to specify low quorum in boot area )

If you reduced lvols then:
for in 1 2 3 ...
>do
>lvextend -m 1 /dev/vg00/lvol${i} /dev/dsk/cxtxdx
>done
( in this manner u don't write lvextend for each lvol)

If you didn't reduce lvols, then vgsync

Hope this helps,
Ziad

[Devender Khatana]

Hi,


As the disk has been removed and mirroed LE's are allocated to this. Allthough you have removed the LE's through using lvreduce -k, the PV is still linked to this volume group. For getting this removed from the vg use

#vgreduce -f

Once done extend Vg normally to the new disk inserted either on same or different path and remirror root as per normal procedure.

HTH,
Devender

[Gary Glick]

Thank you to everyone that contributed.
I've got it solved now.

The vgcfgrestore -n vg00 /dev/c0t5d0 followed by vgchange -a y /dev/vg00. got it & the lvols have been remirrored.

One of the things that took a while was that when I applied the vgcfgrestore command the system sould kick back what looked like an error message then say that the config was restored. I finally just ran the vgchange command the error was fixed.

Thanks again for everyones help.

Gary