Problems with VG00

[Gustavo Souza Lima]

Hi guys,

I have a big problem. I have a server with HPUX 11.00 and the VG00 was setting to work with Mirror, but always that the sync process ran the mirror disk was unavailable status. I try to reconfigure the mirror settings but when I try to extend the VG00 again and run vgscan -v command the vg00 didn't appear in the lvmtab file. I believe my problems with mirror happend because of the vg00 trouble.
I read a article about LVM Maintenance Mode on HPUX and I saw it's possible to export/import the VG00 in this Mode. My question is: My problem will be solved if I export/import the VG00 in this Mode???

Please anyone help me!!!!
Regards

[Adam W.]

Gustavo,
Run the command ioscan -Fnc disk and post the output.

[Adam W.]

HA typo, ioscan -fnC disk

[Gustavo Souza Lima]

Follow.. the ioscan command.
PS.: the disk c1t6d0 was the mirror disk, but now I remove the mirror configuration, so the VG00 is using only the disk c2t6d0.

svuxpmt1:/# ioscan -fnC disk
Class I H/W Path Driver S/W State H/W Type Description
======================================================================================
disk 0 0/0/1/0.1.0 sdisk CLAIMED DEVICE HP DVD-ROM 304
/dev/dsk/c0t1d0 /dev/rdsk/c0t1d0
disk 333 0/0/2/0.6.0 sdisk CLAIMED DEVICE SEAGATE ST318404LC
/dev/dsk/c1t6d0 /dev/rdsk/c1t6d0
disk 1 0/0/2/1.6.0 sdisk CLAIMED DEVICE SEAGATE ST318203LC
/dev/dsk/c2t6d0 /dev/rdsk/c2t6d0
disk 41 0/4/0/0.97.117.19.0.0.0 sdisk CLAIMED DEVICE DGC CX3-80WDR5
/dev/dsk/c54t0d0 /dev/rdsk/c54t0d0
disk 44 0/4/0/0.97.117.19.0.0.1 sdisk CLAIMED DEVICE DGC CX3-80WDR5
/dev/dsk/c54t0d1 /dev/rdsk/c54t0d1
disk 45 0/4/0/0.97.117.19.0.0.2 sdisk CLAIMED DEVICE DGC CX3-80WDR5
/dev/dsk/c54t0d2 /dev/rdsk/c54t0d2
disk 46 0/4/0/0.97.117.19.0.0.3 sdisk CLAIMED DEVICE DGC CX3-80WDR5
/dev/dsk/c54t0d3 /dev/rdsk/c54t0d3
disk 47 0/4/0/0.97.117.19.0.0.4 sdisk CLAIMED DEVICE DGC CX3-80WDR5
/dev/dsk/c54t0d4 /dev/rdsk/c54t0d4
disk 48 0/4/0/0.97.117.19.0.0.5 sdisk CLAIMED DEVICE DGC CX3-80WDR5
/dev/dsk/c54t0d5 /dev/rdsk/c54t0d5
disk 49 0/4/0/0.97.117.19.0.0.6 sdisk CLAIMED DEVICE DGC CX3-80WDR5
/dev/dsk/c54t0d6 /dev/rdsk/c54t0d6
disk 50 0/4/0/0.97.117.19.0.0.7 sdisk CLAIMED DEVICE DGC CX3-80WDR5
/dev/dsk/c54t0d7 /dev/rdsk/c54t0d7
disk 51 0/4/0/0.97.117.19.0.1.0 sdisk CLAIMED DEVICE DGC CX3-80WDR5
/dev/dsk/c54t1d0 /dev/rdsk/c54t1d0
disk 52 0/4/0/0.97.117.19.0.1.1 sdisk CLAIMED DEVICE DGC CX3-80WDR5
/dev/dsk/c54t1d1 /dev/rdsk/c54t1d1
disk 53 0/4/0/0.97.117.19.0.1.2 sdisk CLAIMED DEVICE DGC CX3-80WDR5
/dev/dsk/c54t1d2 /dev/rdsk/c54t1d2
disk 54 0/4/0/0.97.117.19.0.1.3 sdisk CLAIMED DEVICE DGC CX3-80WDR5
/dev/dsk/c54t1d3 /dev/rdsk/c54t1d3
disk 55 0/4/0/0.97.117.19.0.1.4 sdisk CLAIMED DEVICE DGC CX3-80WDR5
/dev/dsk/c54t1d4 /dev/rdsk/c54t1d4
disk 42 1/10/0/0.106.116.19.0.0.0 sdisk CLAIMED DEVICE DGC CX3-80WDR5
/dev/dsk/c53t0d0 /dev/rdsk/c53t0d0
disk 43 1/10/0/0.106.116.19.0.0.1 sdisk CLAIMED DEVICE DGC CX3-80WDR5
/dev/dsk/c53t0d1 /dev/rdsk/c53t0d1
disk 56 1/10/0/0.106.116.19.0.0.2 sdisk CLAIMED DEVICE DGC CX3-80WDR5
/dev/dsk/c53t0d2 /dev/rdsk/c53t0d2
disk 57 1/10/0/0.106.116.19.0.0.3 sdisk CLAIMED DEVICE DGC CX3-80WDR5
/dev/dsk/c53t0d3 /dev/rdsk/c53t0d3
disk 58 1/10/0/0.106.116.19.0.0.4 sdisk CLAIMED DEVICE DGC CX3-80WDR5
/dev/dsk/c53t0d4 /dev/rdsk/c53t0d4
disk 59 1/10/0/0.106.116.19.0.0.5 sdisk CLAIMED DEVICE DGC CX3-80WDR5
/dev/dsk/c53t0d5 /dev/rdsk/c53t0d5
disk 60 1/10/0/0.106.116.19.0.0.6 sdisk CLAIMED DEVICE DGC CX3-80WDR5
/dev/dsk/c53t0d6 /dev/rdsk/c53t0d6
disk 61 1/10/0/0.106.116.19.0.0.7 sdisk CLAIMED DEVICE DGC CX3-80WDR5
/dev/dsk/c53t0d7 /dev/rdsk/c53t0d7
disk 62 1/10/0/0.106.116.19.0.1.0 sdisk CLAIMED DEVICE DGC CX3-80WDR5
/dev/dsk/c53t1d0 /dev/rdsk/c53t1d0
disk 63 1/10/0/0.106.116.19.0.1.1 sdisk CLAIMED DEVICE DGC CX3-80WDR5
/dev/dsk/c53t1d1 /dev/rdsk/c53t1d1
disk 64 1/10/0/0.106.116.19.0.1.2 sdisk CLAIMED DEVICE DGC CX3-80WDR5
/dev/dsk/c53t1d2 /dev/rdsk/c53t1d2
disk 65 1/10/0/0.106.116.19.0.1.3 sdisk CLAIMED DEVICE DGC CX3-80WDR5
/dev/dsk/c53t1d3 /dev/rdsk/c53t1d3
disk 66 1/10/0/0.106.116.19.0.1.4 sdisk CLAIMED DEVICE DGC CX3-80WDR5
/dev/dsk/c53t1d4 /dev/rdsk/c53t1d4

[Adam W.]

I am confused as to your issue. You want to mirror it? If it was mirrored why was the mirror removed?

[Adam W.]

also are you using Veritas, ONline JFS?

[Adam W.]

If your looking to mirror here is the procedure I use. (Online JFS)

A. pvcreate â B /dev/rdsk/c?t?d?
(to make the local disk2 to a bootable physical volume.)

B. vgextend /dev/vg00 /dev/dsk/c?t?d?
(to encase local disk2 into volume group vg00)

C. mkboot â l /dev/rdsk/c?t?d?
(to place the boot utilities into the boot area of the disk)

D. mkboot â a â hpux â lq (;0)/stand/vmunixâ /dev/rdsk/c?t?d?
( points disk to /stand Dir.)
NOTE: -lq needed if only 2 disks exist in the mirroring; otherwise when booting it wonâ t boot (if one disk is bad) and need to do ISL> hpux-lq

E. lvextend â m 1 /dev/vg00/lvol1 /dev/dsk/c?t?d?
(do this for all lvols on disk1 to disk2)

F. lvlnboot â b /dev/vg00/lvol1
(make bootable lvol)

G. lvlnboot â r /dev/vg00/lvol3
(makes root lvol)

H. lvlnboot â s /dev/vg00/lvol2
(makes swap lvol)

I. lvlnboot â d /dev/vg00/lvol2
(makes lvol2 dump space)

J. lvlnboot â v
(to confirm you see both bootable disks)

K. lvdisplay â v /dev/vg00/lvol[1-?]
(to ensure both disks are available and current/synched and not stale)

L. setboot â a ?/?/?/?.?.?.?.? (physical address)
(sets disk2 as backup boot disk in case primary failes)
NOTE: the â a is for alternate, if primary is needed the argument is -p

[Adam W.]

All of the "â  " in the above are "-"

[Adam W.]

Attached is the "text" version of what I use

[Gustavo Souza Lima]

Sorry..
Let me explain better...

There was a mirror configuration on this server, but the mirror disk (c1t6d0) crashed and I tried to change the disk twice, but all the time, the disk c1t6d0 was unavailable when the sync process started. Because of that I remove the mirror configuration and changed the disk (c1t6d0) again and tried to reconfigure the mirror, but when I tried to run the command vgscan -v to recreate the lvmtab file, the VG00 didn't appeared.

Now Can you understand???
Sorry for the distarbe...

[Torsten.]

What steps did you use when replacing and sync the disk?

Any error messages during this?

Problems with "vgcfgrestore" maybe???

[Adam W.]

Please attach the output of the vgscan.

[Adam W.]

Can you run a vgdisplay -v vg00?

[Adam W.]

Did you do a vgreduce when you removed the disk?

[Gustavo Souza Lima]

Steps that I followed:

1 - After changing the crashed disk I type - pvcreate -B /dev/rdsk/c1t6d0
2 - Then I executed the command -> vgcfgrestore -n /dev/vg00 /dev/rdsk/c1t6d0, and the messages Vgcfgrestore executed successfully to /dev/vg00 appeared.
3 - mv /etc/lvmtab /etc/lvmtab.old
4 - vgscan -v, and when I type strings /etc/lvmtab the vg00 didn't appear in the lvmtab.

From here, I rollback the lvmtab.old and stopped the mirror configutation.

[Torsten.]

Why you moved the lvmtab away???

Do you know this already?

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


Proceed with the old lvmtab file.

[Gustavo Souza Lima]

Follow the vgscan -v output;

svuxpmt1:/# vgscan -v
Creating "/etc/lvmtab".
vgscan: Couldn't access the list of physical volumes for volume group "/dev/vgapmt1".
vgscan: Couldn't access the list of physical volumes for volume group "/dev/vgbpmt1".
vgscan: Couldn't access the list of physical volumes for volume group "/dev/vgtst".
Couldn't stat physical volume "/dev/dsk/c0t1d0":
Invalid argument


/dev/vgtst
/dev/dsk/c1t6d0


Following Physical Volumes belong to one Volume Group.
Unable to match these Physical Volumes to a Volume Group.
Use the vgimport command to complete the process.
/dev/dsk/c2t6d0


/dev/vgapmt1
/dev/dsk/c54t0d0
/dev/dsk/c54t0d1
/dev/dsk/c54t0d2
/dev/dsk/c54t0d3
/dev/dsk/c54t0d4
/dev/dsk/c54t0d5
/dev/dsk/c53t0d0
/dev/dsk/c53t0d1
/dev/dsk/c53t0d2
/dev/dsk/c53t0d3
/dev/dsk/c53t0d4
/dev/dsk/c53t0d5



/dev/vgbpmt1
/dev/dsk/c54t0d6
/dev/dsk/c54t0d7
/dev/dsk/c54t1d0
/dev/dsk/c54t1d1
/dev/dsk/c54t1d2
/dev/dsk/c54t1d3
/dev/dsk/c54t1d4
/dev/dsk/c53t0d6
/dev/dsk/c53t0d7
/dev/dsk/c53t1d0
/dev/dsk/c53t1d1
/dev/dsk/c53t1d2
/dev/dsk/c53t1d3
/dev/dsk/c53t1d4

Ouput from the strings /etc/lvmtab

svuxpmt1:/# strings /etc/lvmtab
/dev/vgtst
/dev/dsk/c1t6d0
/dev/vgapmt1
/dev/dsk/c54t0d0
/dev/dsk/c54t0d1
/dev/dsk/c54t0d2
/dev/dsk/c54t0d3
/dev/dsk/c54t0d4
/dev/dsk/c54t0d5
/dev/dsk/c53t0d0
/dev/dsk/c53t0d1
/dev/dsk/c53t0d2
/dev/dsk/c53t0d3
/dev/dsk/c53t0d4
/dev/dsk/c53t0d5
/dev/vgbpmt1
/dev/dsk/c54t0d6
/dev/dsk/c54t0d7
/dev/dsk/c54t1d0
/dev/dsk/c54t1d1
/dev/dsk/c54t1d2
/dev/dsk/c54t1d3
/dev/dsk/c54t1d4
/dev/dsk/c53t0d6
/dev/dsk/c53t0d7
/dev/dsk/c53t1d0
/dev/dsk/c53t1d1
/dev/dsk/c53t1d2
/dev/dsk/c53t1d3
/dev/dsk/c53t1d4

The VG00 doesn't appear in the lvmtab.

[Adam W.]

I am confused as to why you renamed the lvmtab and created a new one? Nothing was "actually" changing. Put that old lvmtab back and keep on truckin! No need to do a vgscan. Use the old lvmtab and run an lvlnboot -v and a vgdisplay -v vg00 and I bet everything will be without error.

[Adam W.]

Then mirror everything again and you should be fine.

[Torsten.]

I don't really know what you did so far, but the disk is already part of another VG:

/dev/vgtst
/dev/dsk/c1t6d0

[Adam W.]

HA torsten ya beat me to it! I love that document. It helps A LOT! Gustavo, always pay close attention to what Torsten has to say he is normally right on with his answers.

[Gustavo Souza Lima]

Okay I will try it.
But it isn't normal the vg00 doesn't appear in the lvmtab, is it???

[Adam W.]

No not particularly, but there aren't many instances where you should NEED to run a vgscan. But Torsten is right that disk is already a part of another VG, so you have already added it elsewhere.

[Adam W.]

Is this (/dev/vgtst) Not your vg00?

[Adam W.]

Do a vgdisplay -v vg00