Proxmox LVM-thin recovery
Proxmox commonly stores VM disks as thin logical volumes inside an LVM thin pool. A full metadata area, missing physical volume, inactive volume group, storage configuration error, or interrupted snapshot can hide or disable VM volumes.
Understand the symptom
LVM-thin allocates blocks from a common data pool and records mappings in a separate metadata device. The logical volume name alone does not contain its disk data. Pool metadata exhaustion or corruption can affect many VMs simultaneously, and creating a replacement thin pool writes new mappings over recoverable state.
What you may see
The expected vm-<id>-disk volume is not listed or cannot activate.
Mapping updates cannot complete and pool health may degrade.
One or more physical volumes are missing, duplicated, or unreadable.
Thin metadata or storage configuration changed during the operation.
Protect the source
New thin metadata disconnects existing data blocks from their VM volumes.
An older backup may omit recent allocations or snapshots.
Shared-pool activity can overwrite free or orphaned blocks needed for recovery.
Do this now
Pause VMs, containers, backups, snapshots, replication, and pool repair.
Collect pvs, vgs, lvs, thin_check results, storage.cfg, VM configs, logs, and /etc/lvm backups.
Label devices, serials, paths, missing members, replacements, and clone history.
Do not create a new volume with the missing VM's name or size.
NEPFOSYS process
NEPFOSYS maps physical volumes, thin data, metadata, snapshots, and VM identifiers.
Underlying volumes are imaged before LVM repair attempts.
Candidate thin mappings are reconstructed and guest filesystems are validated.
A clear next step
Start a case with the exact symptoms, incident timeline, prior attempts, encryption details, and the files that matter most. NEPFOSYS will route the case to the appropriate DFW intake or nationwide mail-in path.
Start with a case reviewQuestions, answered
No. A new thin volume creates different mappings and can allocate blocks over the old data.
It maps each virtual block to shared pool extents; without it, raw pool data does not identify which VM owns each block.
No. They describe configuration and may help reconstruction, but guest sectors remain in the thin data pool.
DFW local · Nationwide mail-in