LVM and VxVM
cancel
Showing results for 
Search instead for 
Did you mean: 

Re: VG activation error after Server is migrated from 1 DC to another, with 3par disk replication

 
Highlighted
HPE Pro

VG activation error after Server is migrated from 1 DC to another, with 3par disk replication

Hi Team,

I have a server rx6600 with HPUX 11.31, that was ship and lift from one DC to another. There are 3par luns configured in the server, which are replicated to both DC 1 and 2. Now that server is in new DC2 coming from DC1, the vg disk information was change as stated below.. Thus we cannot activate the vgs.

vgchange -a y /dev/vgcldp01
vgchange: Warning: Couldn't attach to the volume group physical volume "/dev/disk/disk30":
The path of the physical volume refers to a device that does not
exist, or is not configured into the kernel.
vgchange: The path of the physical volume refers to a device that does not
exist, or is not configured into the kernel.
vgchange: The path of the physical volume refers to a device that does not
exist, or is not configured into the kernel.
vgchange: Couldn't activate volume group "/dev/vgcldp01":
Quorum not present, or some physical volume(s) are missing.

 

strings /etc/lvmconf/vgora01.conf

CONFIG01

/dev/vgora01

/dev/rdisk/disk85 è old disk from Sateri, now this will be replaced by new disk /dev/disk/disk107 in Helsinki

LVMREC01

ITVGDA0001

VGSA0001Z

 

 

 

 

Accept or Kudo

7 REPLIES 7
Highlighted
Acclaimed Contributor

Re: VG activation error after Server is migrated from 1 DC to another, with 3par disk replication

if you have different special device files now, you need to vgexport/vgimport the VG.


Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Highlighted
HPE Pro

Re: VG activation error after Server is migrated from 1 DC to another, with 3par disk replication

Hi Torsten,

Please see specific error below, the old disks that was save from map files are /dev/disk/disk30, /dev/disk/disk31 and /dev/disk/disk32 and since the server was move from another DC. This disks are now not available, and the replicated disk from local storage is /dev/disk/disk109. Now the question is how can I add this new disk that holds its data to activate the VG.

Will the below option from man page, could sove the issue:

Restore LVM configuration information stored for /dev/rdsk/c0t7d0 in
default configuration file vg01.conf to physical volume
/dev/rdsk/c0t6d0:

vgcfgrestore -n /dev/vg01 -o /dev/rdsk/c0t7d0 /dev/rdsk/c0t6d0

 

error below:

fiesdpc901.emea.nsn-net.net:/# vgimport -v -s -m /tmp/vgcldp01.map /dev/vgcldp01
Beginning the import process on Volume Group "/dev/vgcldp01".
vgimport: Volume group "/dev/vgcldp01" already exists in the "/etc/lvmtab" file.
fiesdpc901.emea.nsn-net.net:/#
fiesdpc901.emea.nsn-net.net:/#
fiesdpc901.emea.nsn-net.net:/# vgchange -a y /dev/vgcldp01
vgchange: Warning: Couldn't attach to the volume group physical volume "/dev/disk/disk30":
The path of the physical volume refers to a device that does not
exist, or is not configured into the kernel.
vgchange: The path of the physical volume refers to a device that does not
exist, or is not configured into the kernel.
vgchange: The path of the physical volume refers to a device that does not
exist, or is not configured into the kernel.
vgchange: Couldn't activate volume group "/dev/vgcldp01":
Quorum not present, or some physical volume(s) are missing.

vgchange: Warning: couldn't query physical volume "/dev/disk/disk30":
The volume group is not activated
vgchange: Warning: couldn't query physical volume "/dev/disk/disk31":
The volume group is not activated
vgchange: Warning: couldn't query physical volume "/dev/disk/disk32":
The volume group is not activated
vgchange: Warning: couldn't query the list of physical volumes.
fiesdpc901.emea.nsn-net.net:/#

Accept or Kudo

Highlighted
HPE Pro

Re: VG activation error after Server is migrated from 1 DC to another, with 3par disk replication

Hi Torsten,

I think the main issue is that the disk was renumbered from the vg, since the server was transfered from one DC to another with different storage, But the disks from storage are replicated to keep data consistent to different DC, now the question is how to activate the VG with the new disk and is it possible to still have the data intact?

Accept or Kudo

Highlighted
HPE Pro

Re: VG activation error after Server is migrated from 1 DC to another, with 3par disk replication

Hi Torsten,

vexport/vgimport did work but for some it had an error like below. Hope you can help me on this.

vgimport -s -m /tmp/vgDP.map /dev/vgDP /dev/rdisk/disk71 /dev/rdisk/disk72 /dev/rdisk/disk73 /dev/rdisk/disk74 /dev/rdisk/disk75 /dev/rdisk/disk76 /dev/rdisk/disk57

Couldn't access the list of physical volumes for volume group "/dev/vgDP"

# vgchange -a y /dev/vgcldp01_3par
vgchange: Couldn't activate volume group "/dev/vgcldp01_3par":
Quorum not present, or some physical volume(s) are missing.

Accept or Kudo

Highlighted
Acclaimed Contributor

Re: VG activation error after Server is migrated from 1 DC to another, with 3par disk replication

just to start, run

vgscan -p -v

and tell the result.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Highlighted
HPE Pro

Re: VG activation error after Server is migrated from 1 DC to another, with 3par disk replication

hi Torsten, 

For issue: 

# vgimport -s -m /tmp/vgDP.map /dev/vgDP
Couldn't access the list of physical volumes for volume group "/dev/vgDP".

below is the vgscan -p -v output:

# vgscan -p -v
vgscan: Warning: couldn't query physical volume "/dev/dsk/c44t0d1":
The specified path does not correspond to physical volume attached to
this volume group
vgscan: Warning: couldn't query physical volume "/dev/dsk/c47t0d1":
The specified path does not correspond to physical volume attached to
this volume group
vgscan: Warning: couldn't query all of the physical volumes.
vgscan: The physical volume "/dev/dsk/c44t0d1" is already recorded in the "/etc/lvmtab" file.
vgscan: The physical volume "/dev/dsk/c47t0d1" is already recorded in the "/etc/lvmtab" file.
vgscan: The physical volume "/dev/dsk/c44t0d2" is already recorded in the "/etc/lvmtab" file.
vgscan: The physical volume "/dev/dsk/c47t0d2" is already recorded in the "/etc/lvmtab" file.


/dev/vg00
/dev/disk/disk4_p2
/dev/disk/disk3_p2

 

/dev/vgdp
/dev/dsk/c44t0d1
/dev/dsk/c47t0d1

 

/dev/vgTMPDP
/dev/dsk/c44t0d2
/dev/dsk/c47t0d2


Couldn't stat physical volume "/dev/dsk/c0t0d0":
Invalid argument
Couldn't stat physical volume "/dev/dsk/c44t12d4":
Invalid argument
Couldn't stat physical volume "/dev/dsk/c47t12d4":
Invalid argument

 

Accept or Kudo

Highlighted
HPE Pro

Re: VG activation error after Server is migrated from 1 DC to another, with 3par disk replication

And for the other issue:

vgimport -s -m /tmp/vgDP.map /dev/vgDP /dev/rdisk/disk71 /dev/rdisk/disk72 /dev/rdisk/disk73 /dev/rdisk/disk74 /dev/rdisk/disk75 /dev/rdisk/disk76 /dev/rdisk/disk57

Couldn't access the list of physical volumes for volume group "/dev/vgDP"

output of vgscan -p -v:

# vgscan -p -v
vgscan: Warning: couldn't query physical volume "/dev/dsk/c26t0d3":
The specified path does not correspond to physical volume attached to
this volume group
vgscan: Warning: couldn't query physical volume "/dev/dsk/c23t0d3":
The specified path does not correspond to physical volume attached to
this volume group
vgscan: Warning: couldn't query the list of physical volumes.
vgscan: Warning: couldn't query physical volume "/dev/disk/disk86":
The specified path does not correspond to physical volume attached to
this volume group
vgscan: Warning: couldn't query the list of physical volumes.
vgscan: Warning: couldn't query physical volume "/dev/disk/disk85":
The specified path does not correspond to physical volume attached to
this volume group
vgscan: Warning: couldn't query the list of physical volumes.
vgscan: Warning: couldn't query physical volume "/dev/disk/disk88":
The specified path does not correspond to physical volume attached to
this volume group
vgscan: Warning: couldn't query the list of physical volumes.
vgscan: Warning: couldn't query physical volume "/dev/disk/disk87":
The specified path does not correspond to physical volume attached to
this volume group
vgscan: Warning: couldn't query the list of physical volumes.
vgscan: The physical volume "/dev/dsk/c26t0d1" is already recorded in the "/etc/lvmtab" file.
vgscan: The physical volume "/dev/dsk/c23t0d1" is already recorded in the "/etc/lvmtab" file.
vgscan: The physical volume "/dev/dsk/c26t0d2" is already recorded in the "/etc/lvmtab" file.
vgscan: The physical volume "/dev/dsk/c23t0d2" is already recorded in the "/etc/lvmtab" file.
vgscan: The physical volume "/dev/dsk/c26t0d3" is already recorded in the "/etc/lvmtab" file.
vgscan: The physical volume "/dev/dsk/c23t0d3" is already recorded in the "/etc/lvmtab" file.
vgscan: The physical volume "/dev/dsk/c26t0d4" is already recorded in the "/etc/lvmtab" file.
vgscan: The physical volume "/dev/dsk/c23t0d4" is already recorded in the "/etc/lvmtab" file.
vgscan: The physical volume "/dev/dsk/c26t0d5" is already recorded in the "/etc/lvmtab" file.
vgscan: The physical volume "/dev/dsk/c23t0d5" is already recorded in the "/etc/lvmtab" file.

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/c17t3d0s2


/dev/vg00
/dev/disk/disk35_p2
/dev/disk/disk36_p2

 

/dev/vgora01
/dev/dsk/c26t0d1
/dev/dsk/c23t0d1

 

/dev/vgclora01
/dev/dsk/c26t0d2
/dev/dsk/c23t0d2


vgscan: has no corresponding valid raw device file under /dev/rdsk.
Verification of unique LVM disk id on each disk in the volume group
/dev/vgcldp01 failed.


/dev/vgtmp
/dev/dsk/c26t0d4
/dev/dsk/c23t0d4

 

/dev/vgdp
/dev/dsk/c26t0d5
/dev/dsk/c23t0d5


The Volume Group /dev/vgclDP01 was not matched with any Physical Volumes.
The Volume Group /dev/vgora01_3par was not matched with any Physical Volumes.
The Volume Group /dev/vgclora01_3par was not matched with any Physical Volumes.
The Volume Group /dev/vgtmp_3par was not matched with any Physical Volumes.
vgscan: Warning: couldn't query physical volume "/dev/disk/disk58":
The specified path does not correspond to physical volume attached to
this volume group
vgscan: Warning: couldn't query physical volume "/dev/disk/disk64":
The specified path does not correspond to physical volume attached to
this volume group
vgscan: Warning: couldn't query physical volume "/dev/disk/disk69":
The specified path does not correspond to physical volume attached to
this volume group
vgscan: Warning: couldn't query physical volume "/dev/disk/disk74":
The specified path does not correspond to physical volume attached to
this volume group
vgscan: Warning: couldn't query physical volume "/dev/disk/disk49":
The specified path does not correspond to physical volume attached to
this volume group
vgscan: Warning: couldn't query physical volume "/dev/disk/disk44":
The specified path does not correspond to physical volume attached to
this volume group
vgscan: Warning: couldn't query the list of physical volumes.
vgscan: Warning: couldn't query physical volume "/dev/disk/disk90":
The specified path does not correspond to physical volume attached to
this volume group
vgscan: Warning: couldn't query the list of physical volumes.
Couldn't stat physical volume "/dev/dsk/c18t0d0":
Invalid argument
Couldn't stat physical volume "/dev/dsk/c17t4d0":
Invalid argument
Couldn't stat physical volume "/dev/dsk/c23t12d4":
Invalid argument
Couldn't stat physical volume "/dev/dsk/c26t12d4":
Invalid argument
Couldn't stat physical volume "/dev/dsk/c23t1d2":
Invalid argument
Couldn't stat physical volume "/dev/dsk/c26t1d2":
Invalid argument


/dev/vgxSwap
/dev/dsk/c26t0d6
/dev/dsk/c23t0d6

The Volume Group /dev/vgDP was not matched with any Physical Volumes.

Accept or Kudo