[SOLVED] Duplicate VG name pve after moving from 3.4 to 4.4

P

plofkat

Active Member
Mar 20, 2013
51
2
28
Background info:

Cluster of 7 proxmox servers - in place upgrade to 4.4 failed, did 4.4 install from CD.
Restored cluster, restored VMS from backups.
VMS running on shared storage - no issues there

Local storage seems a bit messed up after upgrade, most of my servers have multiple drives, used to backup VMS from the shared storage.

First install was done a couple of years ago - If I remember correctly, the data volume was extended to include the extra drives - after the re-install I suspect the old LVM settings remained somehow
The data on the extra drives is mostly old backups, so I am not overly worried about it.

What would be the safest way to repair this issue on a running system?
The PV UUID on the drives seems to be different after the install - would it be possible to remove the old UUID and replace it with the current one?


Code: 
root@vwk-prox01:~# pvs
  WARNING: Duplicate VG name pve: rj3oK2-fJha-Dnj0-ssBF-yBX5-T5Hf-copeiM (created here) takes precedence over 71h4As-Gd2h-MwFn-tjRo-QJHn-qx06-JL4Ag3
  WARNING: Duplicate VG name pve: Existing rj3oK2-fJha-Dnj0-ssBF-yBX5-T5Hf-copeiM (created here) takes precedence over 71h4As-Gd2h-MwFn-tjRo-QJHn-qx06-JL4Ag3
  Couldn't find device with uuid B1cjBQ-U2Om-qvRP-fwRj-HDEP-SNCR-ZDswSs.
  PV             VG   Fmt  Attr PSize   PFree
  /dev/sda3      pve  lvm2 a--  464.47g 15.82g
  /dev/sdb1      pve  lvm2 a--    2.00t 16.00g
  unknown device pve  lvm2 a-m  464.23g     0

root@vwk-prox01:~# vgs
  WARNING: Duplicate VG name pve: rj3oK2-fJha-Dnj0-ssBF-yBX5-T5Hf-copeiM (created here) takes precedence over 71h4As-Gd2h-MwFn-tjRo-QJHn-qx06-JL4Ag3
  WARNING: Duplicate VG name pve: rj3oK2-fJha-Dnj0-ssBF-yBX5-T5Hf-copeiM (created here) takes precedence over 71h4As-Gd2h-MwFn-tjRo-QJHn-qx06-JL4Ag3
  WARNING: Duplicate VG name pve: Existing rj3oK2-fJha-Dnj0-ssBF-yBX5-T5Hf-copeiM (created here) takes precedence over 71h4As-Gd2h-MwFn-tjRo-QJHn-qx06-JL4Ag3
  Couldn't find device with uuid B1cjBQ-U2Om-qvRP-fwRj-HDEP-SNCR-ZDswSs.
  WARNING: Duplicate VG name pve: rj3oK2-fJha-Dnj0-ssBF-yBX5-T5Hf-copeiM (created here) takes precedence over 71h4As-Gd2h-MwFn-tjRo-QJHn-qx06-JL4Ag3
  VG   #PV #LV #SN Attr   VSize   VFree
  pve    2   3   0 wz-pn-   2.45t 16.00g
  pve    1   3   0 wz--n- 464.47g 15.82g

root@vwk-prox01:~# fdisk -l |grep sd
Disk /dev/sda: 464.7 GiB, 498999492608 bytes, 974608384 sectors
/dev/sda1    2048      4095      2048     1M BIOS boot
/dev/sda2    4096    528383    524288   256M EFI System
/dev/sda3  528384 974608350 974079967 464.5G Linux LVM
Disk /dev/sdb: 3.7 TiB, 3997997989888 bytes, 7808589824 sectors
/dev/sdb1   2048 7808589790 7808587743  3.7T Linux LVM

 pvdisplay
  WARNING: Duplicate VG name pve: rj3oK2-fJha-Dnj0-ssBF-yBX5-T5Hf-copeiM (created here) takes precedence over 71h4As-Gd2h-MwFn-tjRo-QJHn-qx06-JL4Ag3
  WARNING: Duplicate VG name pve: Existing rj3oK2-fJha-Dnj0-ssBF-yBX5-T5Hf-copeiM (created here) takes precedence over 71h4As-Gd2h-MwFn-tjRo-QJHn-qx06-JL4Ag3
  Couldn't find device with uuid B1cjBQ-U2Om-qvRP-fwRj-HDEP-SNCR-ZDswSs.
  --- Physical volume ---
  PV Name               unknown device
  VG Name               pve
  PV Size               464.23 GiB / not usable 3.00 MiB
  Allocatable           yes (but full)
  PE Size               4.00 MiB
  Total PE              118842
  Free PE               0
  Allocated PE          118842
  PV UUID               B1cjBQ-U2Om-qvRP-fwRj-HDEP-SNCR-ZDswSs

  --- Physical volume ---
  PV Name               /dev/sdb1
  VG Name               pve
  PV Size               2.00 TiB / not usable 3.00 MiB
  Allocatable           yes
  PE Size               4.00 MiB
  Total PE              524287
  Free PE               4095
  Allocated PE          520192
  PV UUID               uWvHkq-6Ps8-Eqs0-eLRz-j3q8-pKt3-x8tygh

  --- Physical volume ---
  PV Name               /dev/sda3
  VG Name               pve
  PV Size               464.48 GiB / not usable 4.98 MiB
  Allocatable           yes
  PE Size               4.00 MiB
  Total PE              118905
  Free PE               4050
  Allocated PE          114855
  PV UUID               zMuwsk-0ZVk-FcSq-fPz9-cl1V-OIPe-dZBoGk

root@vwk-prox01:~# lvdisplay
  WARNING: Duplicate VG name pve: rj3oK2-fJha-Dnj0-ssBF-yBX5-T5Hf-copeiM (created here) takes precedence over 71h4As-Gd2h-MwFn-tjRo-QJHn-qx06-JL4Ag3
  WARNING: Duplicate VG name pve: rj3oK2-fJha-Dnj0-ssBF-yBX5-T5Hf-copeiM (created here) takes precedence over 71h4As-Gd2h-MwFn-tjRo-QJHn-qx06-JL4Ag3
  WARNING: Duplicate VG name pve: Existing rj3oK2-fJha-Dnj0-ssBF-yBX5-T5Hf-copeiM (created here) takes precedence over 71h4As-Gd2h-MwFn-tjRo-QJHn-qx06-JL4Ag3
  Couldn't find device with uuid B1cjBQ-U2Om-qvRP-fwRj-HDEP-SNCR-ZDswSs.
  --- Logical volume ---
  LV Path                /dev/pve/swap
  LV Name                swap
  VG Name                pve
  LV UUID                c3ySu6-TbJ3-xeON-Oeed-9xk7-ccpw-f8Darz
  LV Write Access        read/write
  LV Creation host, time proxmox, 2012-07-12 12:02:54 +0200
  LV Status              NOT available
  LV Size                31.00 GiB
  Current LE             7936
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto

  --- Logical volume ---
  LV Path                /dev/pve/root
  LV Name                root
  VG Name                pve
  LV UUID                OZkrVO-fV4B-oYeU-Mui0-Wk7G-FGd1-viycEQ
  LV Write Access        read/write
  LV Creation host, time proxmox, 2012-07-12 12:02:54 +0200
  LV Status              NOT available
  LV Size                96.00 GiB
  Current LE             24576
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto

  --- Logical volume ---
  LV Path                /dev/pve/data
  LV Name                data
  VG Name                pve
  LV UUID                nCIGc3-uXzg-Al1n-kClB-IIE6-4VOm-hJzRgk
  LV Write Access        read/write
  LV Creation host, time proxmox, 2012-07-12 12:02:54 +0200
  LV Status              NOT available
  LV Size                2.31 TiB
  Current LE             606522
  Segments               2
  Allocation             inherit
  Read ahead sectors     auto

  WARNING: Duplicate VG name pve: rj3oK2-fJha-Dnj0-ssBF-yBX5-T5Hf-copeiM (created here) takes precedence over 71h4As-Gd2h-MwFn-tjRo-QJHn-qx06-JL4Ag3
  --- Logical volume ---
  LV Path                /dev/pve/swap
  LV Name                swap
  VG Name                pve
  LV UUID                zD0Y1U-T766-RdRQ-0W0C-R3U1-OxU6-unxPbJ
  LV Write Access        read/write
  LV Creation host, time proxmox, 2017-04-08 08:34:49 +0200
  LV Status              available
  # open                 2
  LV Size                8.00 GiB
  Current LE             2048
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           251:1

  --- Logical volume ---
  LV Path                /dev/pve/root
  LV Name                root
  VG Name                pve
  LV UUID                4NCzEX-MbNU-pn5f-7006-2cPb-rRXb-TvF0nb
  LV Write Access        read/write
  LV Creation host, time proxmox, 2017-04-08 08:34:49 +0200
  LV Status              available
  # open                 1
  LV Size                96.00 GiB
  Current LE             24576
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           251:0

  --- Logical volume ---
  LV Name                data
  VG Name                pve
  LV UUID                WdEkwG-Sa84-scXZ-LUOW-T392-qdTb-PzumUD
  LV Write Access        read/write
  LV Creation host, time proxmox, 2017-04-08 08:34:50 +0200
  LV Pool metadata       data_tmeta
  LV Pool data           data_tdata
  LV Status              available
  # open                 0
  LV Size                344.48 GiB
  Allocated pool data    0.00%
  Allocated metadata     0.43%
  Current LE             88187
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           251:4
 
Safest way - use vgimportclone to rename VG on /dev/sdb, and, if you need, save data from these volume and reinitialize it.

Another way - use vgcfgbackup to save VG metadata, edit it by hand (remove abcent volume, change UUID) and use vgcfgrestore to restore correct VG metadata.
 
Alexander Pytlev said:
Safest way - use vgimportclone to rename VG on /dev/sdb, and, if you need, save data from these volume and reinitialize it.

Another way - use vgcfgbackup to save VG metadata, edit it by hand (remove abcent volume, change UUID) and use vgcfgrestore to restore correct VG metadata.
Click to expand...



Thanks, I tried first option, however LVM is determined to give me a hard time.
Code: 
vgimportclone -t /dev/sdb1
  WARNING: Duplicate VG name pve: rj3oK2-fJha-Dnj0-ssBF-yBX5-T5Hf-copeiM (created here) takes precedence over 71h4As-Gd2h-MwFn-tjRo-QJHn-qx06-JL4Ag3
  WARNING: Duplicate VG name pve: rj3oK2-fJha-Dnj0-ssBF-yBX5-T5Hf-copeiM (created here) takes precedence over 71h4As-Gd2h-MwFn-tjRo-QJHn-qx06-JL4Ag3
  WARNING: Duplicate VG name pve: Existing rj3oK2-fJha-Dnj0-ssBF-yBX5-T5Hf-copeiM (created here) takes precedence over 71h4As-Gd2h-MwFn-tjRo-QJHn-qx06-JL4Ag3
  Couldn't find device with uuid B1cjBQ-U2Om-qvRP-fwRj-HDEP-SNCR-ZDswSs.
  WARNING: Duplicate VG name pve: rj3oK2-fJha-Dnj0-ssBF-yBX5-T5Hf-copeiM (created here) takes precedence over 71h4As-Gd2h-MwFn-tjRo-QJHn-qx06-JL4Ag3
  Couldn't find device with uuid B1cjBQ-U2Om-qvRP-fwRj-HDEP-SNCR-ZDswSs.
Volume Group pve has unknown PV(s), skipping.
- Were all associated PV(s) supplied as arguments?

The missing volume is now the volume proxmox is installed on.


Code: 
lvdisplay
  WARNING: Duplicate VG name pve: rj3oK2-fJha-Dnj0-ssBF-yBX5-T5Hf-copeiM (created here) takes precedence over 71h4As-Gd2h-MwFn-tjRo-QJHn-qx06-JL4Ag3
  WARNING: Duplicate VG name pve: rj3oK2-fJha-Dnj0-ssBF-yBX5-T5Hf-copeiM (created here) takes precedence over 71h4As-Gd2h-MwFn-tjRo-QJHn-qx06-JL4Ag3
  WARNING: Duplicate VG name pve: Existing rj3oK2-fJha-Dnj0-ssBF-yBX5-T5Hf-copeiM (created here) takes precedence over 71h4As-Gd2h-MwFn-tjRo-QJHn-qx06-JL4Ag3
  Couldn't find device with uuid B1cjBQ-U2Om-qvRP-fwRj-HDEP-SNCR-ZDswSs.
  --- Logical volume ---
  LV Path                /dev/pve/swap
  LV Name                swap
  VG Name                pve
  LV UUID                c3ySu6-TbJ3-xeON-Oeed-9xk7-ccpw-f8Darz
  LV Write Access        read/write
  LV Creation host, time proxmox, 2012-07-12 12:02:54 +0200
  LV Status              NOT available
  LV Size                31.00 GiB
  Current LE             7936
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto

  --- Logical volume ---
  LV Path                /dev/pve/root
  LV Name                root
  VG Name                pve
  LV UUID                OZkrVO-fV4B-oYeU-Mui0-Wk7G-FGd1-viycEQ
  LV Write Access        read/write
  LV Creation host, time proxmox, 2012-07-12 12:02:54 +0200
  LV Status              NOT available
  LV Size                96.00 GiB
  Current LE             24576
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto

  --- Logical volume ---
  LV Path                /dev/pve/data
  LV Name                data
  VG Name                pve
  LV UUID                nCIGc3-uXzg-Al1n-kClB-IIE6-4VOm-hJzRgk
  LV Write Access        read/write
  LV Creation host, time proxmox, 2012-07-12 12:02:54 +0200
  LV Status              NOT available
  LV Size                2.31 TiB
  Current LE             606522
  Segments               2
  Allocation             inherit
  Read ahead sectors     auto

  WARNING: Duplicate VG name pve: rj3oK2-fJha-Dnj0-ssBF-yBX5-T5Hf-copeiM (created here) takes precedence over 71h4As-Gd2h-MwFn-tjRo-QJHn-qx06-JL4Ag3
  --- Logical volume ---
  LV Path                /dev/pve/swap
  LV Name                swap
  VG Name                pve
  LV UUID                zD0Y1U-T766-RdRQ-0W0C-R3U1-OxU6-unxPbJ
  LV Write Access        read/write
  LV Creation host, time proxmox, 2017-04-08 08:34:49 +0200
  LV Status              available
  # open                 2
  LV Size                8.00 GiB
  Current LE             2048
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           251:1

  --- Logical volume ---
  LV Path                /dev/pve/root
  LV Name                root
  VG Name                pve
  LV UUID                4NCzEX-MbNU-pn5f-7006-2cPb-rRXb-TvF0nb
  LV Write Access        read/write
  LV Creation host, time proxmox, 2017-04-08 08:34:49 +0200
  LV Status              available
  # open                 1
  LV Size                96.00 GiB
  Current LE             24576
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           251:0

  --- Logical volume ---
  LV Name                data
  VG Name                pve
  LV UUID                WdEkwG-Sa84-scXZ-LUOW-T392-qdTb-PzumUD
  LV Write Access        read/write
  LV Creation host, time proxmox, 2017-04-08 08:34:50 +0200
  LV Pool metadata       data_tmeta
  LV Pool data           data_tdata
  LV Status              available
  # open                 0
  LV Size                344.48 GiB
  Allocated pool data    0.00%
  Allocated metadata     0.43%
  Current LE             88187
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           251:4

Any data on the old drive is now out of date and irrelevant, so losing it is not an issue. My goal now is to get rid of the duplicate pve VG, add the large drive back on the VG and to expand the volumes back to the 2012 sizes if possible.
It seems I am stuck in a bit of a loop, I can't remove the missing PV because I have a duplicate VG, I cannot change the VG because I have a missing PV
 
Right parameters: vgimportclone -n pve_old /dev/sdb1

but better run: vgcfgbackup -f /tmp/pve_cfg.vg pve
and attach file /tmp/pve_cfg.vg to message, I look it, edit and send back,
after that you try run vgcfgrestore -f /tmp/pve_cfg_new.vg pve
 
It appears that vgcfgbackup only exports the first VG named pve and not the second one that is actually running.
Is this expected behaviour?

( WARNING: Duplicate VG name pve: rj3oK2-fJha-Dnj0-ssBF-yBX5-T5Hf-copeiM (created here) takes precedence over 71h4As-Gd2h-MwFn-tjRo-QJHn-qx06-JL4Ag3)

Can it be run somehow using the VG UUID?
 
If You don't ran vgimportclone -n pve_old /dev/sdb1 to rename VG on sdb1, you have one VG named pve, but two UUD for it on different PV
run vgcfgbackup -f /tmp/pve_cfg.vg pve it's safe
and look inside /tmp/pve_cfg.vg
If you rename VG on sdb1, run vgcfgbackup -f /tmp/pve_old_cfg.vg pve_old too
 
Ah, sorry - unable to rename because of missing PV, unable to remove missing due to duplicate VG name.

Code: 
vgimportclone -n pve_old /dev/sdb1
  WARNING: Duplicate VG name pve: rj3oK2-fJha-Dnj0-ssBF-yBX5-T5Hf-copeiM (created here) takes precedence over 71h4As-Gd2h-MwFn-tjRo-QJHn-qx06-JL4Ag3
  WARNING: Duplicate VG name pve: rj3oK2-fJha-Dnj0-ssBF-yBX5-T5Hf-copeiM (created here) takes precedence over 71h4As-Gd2h-MwFn-tjRo-QJHn-qx06-JL4Ag3
  WARNING: Duplicate VG name pve: Existing rj3oK2-fJha-Dnj0-ssBF-yBX5-T5Hf-copeiM (created here) takes precedence over 71h4As-Gd2h-MwFn-tjRo-QJHn-qx06-JL4Ag3
  Couldn't find device with uuid B1cjBQ-U2Om-qvRP-fwRj-HDEP-SNCR-ZDswSs.
  WARNING: Duplicate VG name pve: rj3oK2-fJha-Dnj0-ssBF-yBX5-T5Hf-copeiM (created here) takes precedence over 71h4As-Gd2h-MwFn-tjRo-QJHn-qx06-JL4Ag3
  Couldn't find device with uuid B1cjBQ-U2Om-qvRP-fwRj-HDEP-SNCR-ZDswSs.
Volume Group pve has unknown PV(s), skipping.
- Were all associated PV(s) supplied as arguments?

content of pve_cfg.vg

As far as I can see, this is the config of the previous install

pve {
id = "rj3oK2-fJha-Dnj0-ssBF-yBX5-T5Hf-copeiM"
seqno = 7
format = "lvm2" # informational
status = ["RESIZEABLE", "READ", "WRITE"]
flags = []
extent_size = 8192 # 4 Megabytes
max_lv = 0
max_pv = 0
metadata_copies = 0

physical_volumes {

pv0 {
id = "B1cjBQ-U2Om-qvRP-fwRj-HDEP-SNCR-ZDswSs"
device = "unknown device" # Hint only

status = ["ALLOCATABLE"]
flags = ["MISSING"]
dev_size = 973559808 # 464.229 Gigabytes
pe_start = 2048
pe_count = 118842 # 464.227 Gigabytes
}

pv1 {
id = "uWvHkq-6Ps8-Eqs0-eLRz-j3q8-pKt3-x8tygh"
device = "/dev/sdb1" # Hint only

status = ["ALLOCATABLE"]
flags = []
dev_size = 4294965247 # 2 Terabytes
pe_start = 2048
pe_count = 524287 # 2 Terabytes
}
}

logical_volumes {

swap {
id = "c3ySu6-TbJ3-xeON-Oeed-9xk7-ccpw-f8Darz"
status = ["READ", "WRITE", "VISIBLE"]
flags = []
creation_host = "proxmox"
creation_time = 1342087374 # 2012-07-12 12:02:54 +0200
segment_count = 1

segment1 {
start_extent = 0
extent_count = 7936 # 31 Gigabytes

type = "striped"
stripe_count = 1 # linear

stripes = [
"pv0", 0
]
}
}

root {
id = "OZkrVO-fV4B-oYeU-Mui0-Wk7G-FGd1-viycEQ"
status = ["READ", "WRITE", "VISIBLE"]
flags = []
creation_host = "proxmox"
creation_time = 1342087374 # 2012-07-12 12:02:54 +0200
segment_count = 1

segment1 {
start_extent = 0
extent_count = 24576 # 96 Gigabytes

type = "striped"
stripe_count = 1 # linear

stripes = [
"pv0", 7936
]
}
}

data {
id = "nCIGc3-uXzg-Al1n-kClB-IIE6-4VOm-hJzRgk"
status = ["READ", "WRITE", "VISIBLE"]
flags = []
creation_host = "proxmox"
creation_time = 1342087374 # 2012-07-12 12:02:54 +0200
segment_count = 2

segment1 {
start_extent = 0
extent_count = 86330 # 337.227 Gigabytes

type = "striped"
stripe_count = 1 # linear

stripes = [
"pv0", 32512
]
}
segment2 {
start_extent = 86330
extent_count = 520192 # 1.98438 Terabytes

type = "striped"
stripe_count = 1 # linear

stripes = [
"pv1", 0
]
}
}
}
}
Click to expand...
 
What happens if you try:
Code: 
vgrename 71h4As-Gd2h-MwFn-tjRo-QJHn-qx06-JL4Ag3 pve_old
 
kobuki said:
What happens if you try:
Code: 
vgrename 71h4As-Gd2h-MwFn-tjRo-QJHn-qx06-JL4Ag3 pve_old
Click to expand...

Is it safe? If it works, it should rename my current working VG on a server that is currently live and part of a cluster...
 
You obviously need to specify the UUID of the VG you want to erase. From your post it looks like the UUID is that one. You cannot rename a VG that's in use.
 
kobuki said:
You obviously need to specify the UUID of the VG you want to erase. From your post it looks like the UUID is that one. You cannot rename a VG that's in use.
Click to expand...

Sure, gotcha - the UUID I need to remove is rj3oK2-fJha-Dnj0-ssBF-yBX5-T5Hf-copeiM

Code: 
 vgrename rj3oK2-fJha-Dnj0-ssBF-yBX5-T5Hf-copeiM pve_old
  WARNING: Duplicate VG name pve: rj3oK2-fJha-Dnj0-ssBF-yBX5-T5Hf-copeiM (created here) takes precedence over 71h4As-Gd2h-MwFn-tjRo-QJHn-qx06-JL4Ag3
  WARNING: Duplicate VG name pve: rj3oK2-fJha-Dnj0-ssBF-yBX5-T5Hf-copeiM (created here) takes precedence over 71h4As-Gd2h-MwFn-tjRo-QJHn-qx06-JL4Ag3
  WARNING: Duplicate VG name pve: Existing rj3oK2-fJha-Dnj0-ssBF-yBX5-T5Hf-copeiM (created here) takes precedence over 71h4As-Gd2h-MwFn-tjRo-QJHn-qx06-JL4Ag3
  Couldn't find device with uuid B1cjBQ-U2Om-qvRP-fwRj-HDEP-SNCR-ZDswSs.
  Cannot change VG pve while PVs are missing.
  Consider vgreduce --removemissing.
  WARNING: Duplicate VG name pve: rj3oK2-fJha-Dnj0-ssBF-yBX5-T5Hf-copeiM (created here) takes precedence over 71h4As-Gd2h-MwFn-tjRo-QJHn-qx06-JL4Ag3

Now, that leads me to vgreduce, however that only works with a VG name and not a UUID unless I am mistaken
 
Oh well, it's a mess. If you can afford a reboot, disable/unplug HDDs you want to keep and just erase the disks or at least the first few megabytes on them using a rescue cd... Or if you can exactly determine the old HDDs you can do it online and then do a vgscan to refresh the LVM caches and get rid of the old VGs.
 
kobuki said:
Oh well, it's a mess.
Click to expand...

Lol yeah, that's putting it mildly.

I have 7 servers with exactly the same issue. If I screw up, I do so with consistency.

Fortunately this issue has no bad side effects, except for severely reduced local storage space.
In most cases I should be able to determine the old drives reliably.
 
I think I finally got it!

I forced the removal of the physical volume on the old drive

Code: 
 pvremove /dev/sdb1 --force --force

That cleared the duplicate VG name, and everything seems to still be up and running.
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back