LVM volume group fails to be activated in another server due to system id mismatch

Applies to

Red Hat Enterprise Linux 8
Red Hat Enterprise Linux 9
LVM2

Symptoms

~]# vgchange -ay G350_VG01
Cannot access VG G350_VG01 with system ID DBNODE02 with unknown local system ID.

Cause

The system_id_source = "uname" option is missing in /etc/lvm/lvm.conf.

Solution

  1. Set system_id_source = "uname" in /etc/lvm/lvm.conf.

  2. Then execute command below to activate volume group.

    ~]# vgchange -y --config local/extra_system_ids=[\"DBNODE02\"] --systemid DBBCV01 G350_VG01
    ~]# vgchange -ay G350_VG01

Reference

・ LVM volume group fails to be activated in another server due to system id mismatch.pdf |
・ How do I manually activate a volume group managed by an LVM-activate resource with system_id on another node.pdf |