Migrating a server that boot from SAN: Warning: Volume Group contains "3" PVs, "4" specified

[VIGNOLA,ALESSANDRO]

I'm moving a vpar from a Superdome to another. The old one boot from EVA storage, so I did a mirror of the boot disk and presented to the new Superdome partition. From the new one I did the boot in mantenance mode then removed the lvmtab
#cd /etc
#mv lvmtab
#mv /etc/ioconfig
#ioinit –c
#ioscan
#insf –e
#vgscan –v
but the vgimport failed
#vgimport –v /dev/vg00 disks
ERROR:
# vgimport -v -m /tmp/ema.map2 vg00 /dev/dsk/c28t0d1s2 /dev/dsk/c32t0d1s2 /dev/dsk/c26t0d1s2 /dev/dsk/c30t0d1s2
Beginning the import process on Volume Group "vg00".
vgimport: Warning: Volume Group belongs to different CPU ID.
Can not determine if Volume Group is in use on another system. Continuing.
vgimport: Warning: Volume Group contains "3" PVs, "4" specified. Continuing.
vgimport: Quorum not present, or some physical volume(s) are missing.
Logical volume "/dev/vg00/lvol1" has been successfully created
with lv number 1.
Logical volume "/dev/vg00/lvol2" has been successfully created
with lv number 2.
Logical volume "/dev/vg00/lvol3" has been successfully created
with lv number 3.
Logical volume "/dev/vg00/lvol4" has been successfully created
with lv number 4.
Logical volume "/dev/vg00/lvol5" has been successfully created
with lv number 5.
Logical volume "/dev/vg00/lvol6" has been successfully created
with lv number 6.
Logical volume "/dev/vg00/lvol7" has been successfully created
with lv number 7.
Logical volume "/dev/vg00/lvol8" has been successfully created
with lv number 8.
Volume group "/dev/vg00" has been successfully created.
Warning: A backup of this volume group may not exist on this machine.
Please remember to take a backup using the vgcfgbackup command after activating the volume group.

SEEMS that the old configuration is still present on the Vgarea.
Suggestions?
thanks
Alex.

[likid0]

You can do a vgchid to get rid of the first warning:
vgimport: Warning: Volume Group belongs to different CPU ID.

the 3 PVs warning, if you want to get rid of it just import first 3 disks then vgextend vg00 and add the forth path.

But in the end they are warnings the import worked ok:

Volume group "/dev/vg00" has been successfully created.

When migrating, I ussualy prefer on 11.11 and 11.23 to restore and ignite image of the server on to the new vpar.

[sujit kumar singh]

hi


please compare the O/Ps of the strings /etc/lvmtab in section vg00 with that list of the disks as u get in the ioscan -fnCdisk.

might be one of the disks are not available or identified by the system or from the storgae one disk has not been presented to this host.

yes the idea to take an ignite and restore that on the new SD NPAR is a good one ,that is more standard and also u will need to do the morroriong of the disks after u install the New System with the Ignite of the old one.


Regards
sujit

[Eric SAUBIGNAC]

Bonjour Alessandro,

"SEEMS that the old configuration is still present on the Vgarea"

Quiet normal. And it is necessary to import a VG. So in a first approach I would say that there is no problem : the 4 disks you try to import to the new superdome partition are 4 pathes to the same Vdisk on the EVA (Lun 1), right ?

What is surprising, is that vgimport speaks of only 3 PVs in the VG you try to import. It should be also 4, unless you have less pathes from the original superdome to the eva. Could you post "vgdisplay -v vg00" from original vPar ?


Eric

[sujit kumar singh]

hi


yes ot seems that the 4 PVs are the 4 paths to the root VG disk . thats true and also booting in the LVM Maintennace mode , exporting the VG vg00, mkdir /dev/vg00 , mknod /dev/vg00/group c 64 0x000000, and reimporting the VG vg00 followed by vgcfgbackyp vg00 and lvnboot -r , -b , -s , -d shall work.


but what has happened to the 4th path of that disk.

that must not be present earlier config as that seems.


please post the ioscan -fnCdisk and the strings /etc/lvmtab currebt O/P.


rebooting in LVM Maintenance mode and exporting and reimporting is reqd.

make sure that all the 4 paths to that LUN u are able to see in the ioscan.


Regrards
sujit

[Eric SAUBIGNAC · Accepted solution]

I must apologize since I deed a mistake in my post : when a VG is configured with one disk and alternate pathes, LVM counts only 1 disk, regardless number of alternate path to the disk that are configured in the VG.

Did a little test : on a vg with only one vDisk, configured with the 4 paths to the EVA, I did a vgreduce on one path so it leaves only 3 path in the VG. Exported the VG, re-imported with the 4 path. Here is the warning message received :

vgimport: Warning: Volume Group contains "1" PVs, "4" specified. Continuing.

So your message means than in your original vg00 you really have 3 different disks. If you have correctly pointed which disk(s) contains the LV you want to import on the new vPar, it should not matter. Which method did you use to mirror : LVM, Business Copy, Continuous Access ?

Eric.

[sujit kumar singh]

hi alex,


thats true , really that is a valid point Eric has made.

Thanks Eric for that , so that means that VG had three disks in that earlier. If that is so then does the current vgdisplay -v vg00 shows three disks(or more valid the three PVs if that VG Erlier was corect) and the corresponding alternate paths configured in?

perhaps if that is so a careful check that all the PVs and the corresponding alternate paths have been configured in the VG has to be checked.


thanks Eric once again.


Regards
sujit

[VIGNOLA,ALESSANDRO]

Hi All, sorry for late I was in trouble with the problem.
After the lvreduce of the mirror that has to be exported I did the vgcfgrestore of the configuration:

#vgcfgrestore -n vg00 -o /dev/rdsk/c2t0d1s2 /dev/rdsk/c30t0d2s2

The Problem was that the "new server" thinks to have a mirror in fact on the original server I had two disks mirrored and then I extended [with lvm mirror] on the third disk for new server, so the lvm configuration was dirty. In fact I Tried to reduce the vg00 without success
# vgreduce -f --> failed and vg00 still present 2 disk mirrored one in stale. Also tried
#lvreduce -k -m 0 /dev/vg00/lvolname pvkey_value . No success

Finally, I did again the mirror for the new server but before I left the original two disks mirror and then I did the one for the new server. In this way the system Boot correctly.
The only strange thing is that the boot disk present 5 partition [?!?]:
gmihsds001:/ ioscan -fnCdisk
Class I H/W Path Driver S/W State H/W Type Description
==========================================================================
disk 49 2/0/1/1/1.2.0 sdisk CLAIMED DEVICE Optiarc DVD RW AD-5170A
/dev/dsk/c35t2d0 /dev/rdsk/c35t2d0
disk 43 2/0/4/1/0/4/0.2.0.0.0.0.1 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c28t0d1 /dev/dsk/c28t0d1s4 /dev/rdsk/c28t0d1s2
/dev/dsk/c28t0d1s1 /dev/dsk/c28t0d1s5 /dev/rdsk/c28t0d1s3
/dev/dsk/c28t0d1s2 /dev/rdsk/c28t0d1 /dev/rdsk/c28t0d1s4
/dev/dsk/c28t0d1s3 /dev/rdsk/c28t0d1s1 /dev/rdsk/c28t0d1s5 <-----------------
disk 44 2/0/4/1/0/4/0.2.4.0.0.0.1 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c32t0d1 /dev/dsk/c32t0d1s3 /dev/rdsk/c32t0d1s2
/dev/dsk/c32t0d1s1 /dev/rdsk/c32t0d1 /dev/rdsk/c32t0d1s3
/dev/dsk/c32t0d1s2 /dev/rdsk/c32t0d1s1
disk 42 2/0/5/1/0/4/0.3.0.0.0.0.1 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c26t0d1 /dev/dsk/c26t0d1s3 /dev/rdsk/c26t0d1s2
/dev/dsk/c26t0d1s1 /dev/rdsk/c26t0d1 /dev/rdsk/c26t0d1s3
/dev/dsk/c26t0d1s2 /dev/rdsk/c26t0d1s1
disk 41 2/0/5/1/0/4/0.3.4.0.0.0.1 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c30t0d1 /dev/dsk/c30t0d1s3 /dev/rdsk/c30t0d1s2
/dev/dsk/c30t0d1s1 /dev/rdsk/c30t0d1 /dev/rdsk/c30t0d1s3
/dev/dsk/c30t0d1s2 /dev/rdsk/c30t0d1s1

Note:I think that the Ignite should be the right view, the problem is that the "old system" hasn't tape and no way to have an ignite sever.

[sujit kumar singh]

hi Alessandro,
for the findings as yours



Class I H/W Path Driver S/W State H/W Type Description
============================================================
==============
disk 49 2/0/1/1/1.2.0 sdisk CLAIMED DEVICE Optiarc DVD RW AD-5170A
/dev/dsk/c35t2d0 /dev/rdsk/c35t2d0
disk 43 2/0/4/1/0/4/0.2.0.0.0.0.1 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c28t0d1 /dev/dsk/c28t0d1s4 /dev/rdsk/c28t0d1s2
/dev/dsk/c28t0d1s1 /dev/dsk/c28t0d1s5 /dev/rdsk/c28t0d1s3
/dev/dsk/c28t0d1s2 /dev/rdsk/c28t0d1 /dev/rdsk/c28t0d1s4
/dev/dsk/c28t0d1s3 /dev/rdsk/c28t0d1s1 /dev/rdsk/c28t0d1s5 <-----------------
disk 44 2/0/4/1/0/4/0.2.4.0.0.0.1 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c32t0d1 /dev/dsk/c32t0d1s3 /dev/rdsk/c32t0d1s2
/dev/dsk/c32t0d1s1 /dev/rdsk/c32t0d1 /dev/rdsk/c32t0d1s3
/dev/dsk/c32t0d1s2 /dev/rdsk/c32t0d1s1
disk 42 2/0/5/1/0/4/0.3.0.0.0.0.1 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c26t0d1 /dev/dsk/c26t0d1s3 /dev/rdsk/c26t0d1s2
/dev/dsk/c26t0d1s1 /dev/rdsk/c26t0d1 /dev/rdsk/c26t0d1s3
/dev/dsk/c26t0d1s2 /dev/rdsk/c26t0d1s1
disk 41 2/0/5/1/0/4/0.3.4.0.0.0.1 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c30t0d1 /dev/dsk/c30t0d1s3 /dev/rdsk/c30t0d1s2
/dev/dsk/c30t0d1s1 /dev/rdsk/c30t0d1 /dev/rdsk/c30t0d1s3
/dev/dsk/c30t0d1s2 /dev/rdsk/c30t0d1s1



hello Alessandro,


u had a 2 way mirroring of the root disk earlier in the system and that is what u r having now also as u have extended one more mirror of the root disk as there had been already one just after the import of the VG on the new system.

can u see for the disk that has the details as
disk 43 2/0/4/1/0/4/0.2.0.0.0.0.1 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c28t0d1 /dev/dsk/c28t0d1s4 /dev/rdsk/c28t0d1s2
/dev/dsk/c28t0d1s1 /dev/dsk/c28t0d1s5 /dev/rdsk/c28t0d1s3
/dev/dsk/c28t0d1s2 /dev/rdsk/c28t0d1 /dev/rdsk/c28t0d1s4
/dev/dsk/c28t0d1s3 /dev/rdsk/c28t0d1s1 /dev/rdsk/c28t0d1s5

read how many Partitions this actually has by issuing the commands as:

#idisk /dev/rdsk/c28t0d1


this should actually show 3 becuase there are physically 3 ptns only.(and not 5)

and diskifo on all the ptns

#diskinfo -v /dev/rdsk/c28t0d1s1
#diskinfo -v /dev/rdsk/c28t0d1s2
#diskinfo -v /dev/rdsk/c28t0d1s3
#diskinfo -v /dev/rdsk/c28t0d1s4
#diskinfo -v /dev/rdsk/c28t0d1s5\
#vi /stand/bootconf


this shall help us know that things about the partions.

also please do know the following things:

#vgdisplay -v vg00

and know the PVs from the /dev/dsk/c28t0d1 that are included in there are those s2 and/or s4 s5 etc.


u can however if find that idisk shows 3 ptns to that disk then,

can do

#rm /dev/dsk/c28*
#rm /dev/rdsk/c28*


these are going to remove only the device files for the c28 disk which can be easily created.
do not worry about the VG as u already have the Mirror of the root disk.
#ioscan
#insf -eCdisk

the shall create the new dev files for the c28 disk.
#ioscan -fnCdisk to ensure that u have s1,s2 and s3 for the c28 disk.

then go on to do the following if reqd.

#vgreduce /dev/vg00 /dev/dsk/c28t0d1s4 or s4

#lvlnboot -R
#vgcfgbackup /dev/vg00


#vi /stand/bootconf

and include the disks appropriately

#setboot to set the system boot paths accordingly.



Regards
Sujit