Updated: 28 September 2026 · Applies to: LVM 2.03 on AlmaLinux and Rocky Linux 9 and 10, RHEL 9 and 10, Ubuntu 24.04 and 26.04, Debian 13
Every LVM physical volume (PV) and volume group (VG) has a unique ID (UUID). Two disks with the same UUIDs confuse LVM: this happens when a disk is cloned, a VM image is copied, or a SAN snapshot is shown to the same server. LVM then reports "Duplicate PV" or "WARNING: VG has the same name/UUID". You can give volumes new UUIDs. We tested the commands on AlmaLinux 9 with LVM 2.03.33.
Before you start
- Take a backup. Changing IDs is safe when done on the right disk, and dangerous on the wrong one.
- Check the current IDs:
pvs -o +pv_uuidandvgs -o +vg_uuid. - Never change the IDs of the volume group the running system boots from.
Cloned disks: use vgimportclone (recommended)
For a copy of an existing volume group, one command gives the PVs and the VG new UUIDs and renames the VG, so both copies can be used side by side:
vgimportclone --basevgname vgdata_clone /dev/sdc
List every PV of the cloned group on the command line. Afterwards, check with vgs and activate it with vgchange -ay vgdata_clone.
Change the UUIDs by hand
- Unmount the file systems of the volume group and deactivate it:
vgchange -an vgdata
- Give the volume group a new UUID:
vgchange -u vgdata
- Give each of its physical volumes a new UUID:
pvchange -u /dev/sdc
- Activate it again and check:
vgchange -ay vgdata vgs -o +vg_uuid pvs -o +pv_uuid
Common problems
- "Cannot change VG while PVs are missing" or duplicate warnings during the change: on AlmaLinux, Rocky Linux and RHEL, LVM only uses devices listed in
/etc/lvm/devices/system.devices. Check that the right disk is listed withlvmdevices, and add a device withlvmdevices --adddev /dev/sdc. - fstab or scripts refer to the old names: file system UUIDs (from
blkid) do not change with this procedure, but a renamed VG changes the/dev/vgname/...paths.
Official documentation: vgimportclone manual page and vgchange manual page.