Are you an LLM? You can read better optimized documentation at /en/docs/common/faq/caselibrary/pvs_vgs.md for this page in Markdown format
"Unknown" Errors in pvs or vgs
Symptom
When running pvs or vgs commands, physical volumes (PVs) or volume groups (VGs) may display "unknown" status.

Possible Causes
This issue typically occurs due to corrupted metadata, preventing the system from reading complete information about the storage components. The affected PV or VG becomes unusable until repaired. For verification, you can examine raw disk data using the hexdump utility (see LVM Label Corruption for details).
Solution
Fixing Unrecognized VGs
bash
pvck --repair --file /etc/lvm/backup/vg /dev/sdbVG backup files are stored in /etc/lvm/backup.
Repairing Unrecognized PVs
bash
pvcreate --uuid xxx --restorefile /etc/lvm/backup/vg /dev/sdc
vgcfgrestore --file /etc/lvm/backup/vg vg
vgchange -ay vgThe UUID can be found in the backup files located at /etc/lvm/backup. After performing these repairs, verify the fix by running pvs or vgs again. Normal output indicates successful restoration.
Licensed under the MulanPSL2
Copyright © 2026 openEuler. All rights reserved.J. ICP B. No. 2020036654-1
J.G.W.A.B. No. 11030102011597
Licensed underthe MulanPSL2
Copyright © 2026 openEuler. All rights reserved.