📖 ~1 min read
Table of contents
Symptom & Impact
VolumeGroup is degraded and dependent volumes refuse to activate, halting database services.
Environment & Reproduction
Triggered after SAN reconfiguration or disk swap on SLES 15 storage nodes.
Root Cause Analysis
PV UUID metadata cannot be located because the device path or WWID changed.
Quick Triage
Run `pvs`, `vgs`, and `lvs` and look for `[unknown]` PVs in the output.
Step-by-Step Diagnosis
Use `vgcfgrestore –list` to list metadata backups and identify the last good revision.

Solution – Primary Fix
Replace the failed PV with `pvcreate –restorefile` and `vgcfgrestore`, then `vgchange -ay`.
Still having issues? Our Server Management team can diagnose and resolve this for you. Get in touch for a free consultation.

Solution – Alternative Approaches
Re-add the new disk into the VG with `vgextend` and migrate data using `pvmove`.
Verification & Acceptance Criteria
All LVs activate, filesystems mount, and applications resume normal IO.
Rollback Plan
Restore from backup if metadata restoration fails or produces inconsistent state.
Prevention & Hardening
Use multipath WWID-based persistent names and monitor PV health.
Related Errors & Cross-Refs
Common with `Couldn’t find device with uuid` warnings in dmesg.
Related tutorial: View the step-by-step tutorial for sles-15.
View all sles-15 tutorials on the Tutorials Hub →
Browse all common problems & solutions on the Tutorials Hub.
References & Further Reading
SUSE LVM administration guide and multipath configuration documentation.
Need Expert Help?
If you cannot resolve this yourself, our team offers hands-on Server Management, Managed IT Services, and flexible Support Plans. Contact us today — we respond within one business day.