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

Solution Verified - Updated -

Issue

  • The LVM volume group somethimes required to be exported/imported between original and new servers for data backup/migration purpose, but volume group failed to be activated in new server with error below:
# vgchange -ay vg_name
  Cannot access VG `vg_name` with system ID xxxx with unknown local system ID.  <=======

Environment

  • Red Hat Enterprise Linux 8
  • Red Hat Enterprise Linux 9
  • LVM2

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content