Hi Zdenek,
Thanks for the reply! Here are the missing version number…
root@proxmox0:~# uname -a
Linux proxmox0 6.8.12-5-pve #1 SMP PREEMPT_DYNAMIC PMX 6.8.12-5
(2024-12-03T10:26Z) x86_64 GNU/Linux
/etc/os-release says "Debian GNU/Linux 12 (bookworm)”.
root@proxmox0:~# lvm version
LVM version: 2.03.16(2) (2022-05-18)
Library version: 1.02.185 (2022-05-18)
Driver version: 4.48.0
Configuration: ./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=$/include --mandir=$/share/man
--infodir=$/share/info --sysconfdir=/etc --localstatedir=/var
--disable-option-checking --disable-silent-rules
--libdir=$/lib/x86_64-linux-gnu --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking
--libdir=/lib/x86_64-linux-gnu --sbindir=/sbin
--with-usrlibdir=/usr/lib/x86_64-linux-gnu --with-optimisation=-O2
--with-cache=internal --with-device-uid=0 --with-device-gid=6
--with-device-mode=0660 --with-default-pid-dir=/run
--with-default-run-dir=/run/lvm --with-default-locking-dir=/run/lock/lvm
--with-thin=internal --with-thin-check=/usr/sbin/thin_check
--with-thin-dump=/usr/sbin/thin_dump
--with-thin-repair=/usr/sbin/thin_repair --with-udev-prefix=/
--enable-applib --enable-blkid_wiping --enable-cmdlib --enable-dmeventd
--enable-editline --enable-lvmlockd-dlm --enable-lvmlockd-sanlock
--enable-lvmpolld --enable-notify-dbus --enable-pkgconfig
--enable-udev_rules --enable-udev_sync --disable-readline
root@proxmox0:~# thin_repair -V
0.9.0
I did try to "apt install --only-upgrade thin-provisioning-tools”, but
it said "thin-provisioning-tools is already the newest version
(0.9.0-2)”. Maybe I need a better repository? Here is the
sources.list:
deb http://ftp.de.debian.org/debian bookworm main contrib
deb http://ftp.de.debian.org/debian bookworm-updates main contrib
deb http://security.debian.org bookworm-security main contrib
deb http://download.proxmox.com/debian/pve bookworm pve-no-subscription
The damage was caused by two disks of a six disk raid-5 array going
offline for some reason. They are both back online and the controller
rebuilt the raid-5 without any obvious errors.
Thanks,
Ray
------ Original Message ------
From "Zdenek Kabelac" <[email protected]>
To "Ray Davis" <[email protected]>; [email protected]
Date 09.04.2026 22:32:56
Subject Re: LVM-thin metadata corruption on Proxmox after RAID-5 issues
– thin_repair/thin_dump fail
Dne 09. 04. 26 v 17:55 Ray Davis napsal(a):
Hello,
I’m looking for advice on an LVM-thin metadata corruption case on a Proxmox
host. I have stopped further repair attempts and preserved the current state
for analysis.
Environment
* Proxmox VE host
* Thin pool: `VMDATA0/VMDATA0`
* Backing storage had RAID-5 issues involving two disks
* After reseating the disks, the RAID came back online, but the thin pool would
no longer activate
* Created temporary metadata LVs
* Used `lvconvert --swapmetadata` to extract the pool metadata
* Activated the extracted metadata LV
* Preserved a raw image of the extracted metadata
* Ran `thin_check`
* Ran `thin_repair`
* Ran `thin_dump —repair`
I can provide access to the full case directory or a tarball over HTTP if
someone is willing to look at it. I would prefer to share the link privately
with anyone interested.
My main questions are:
1. Is there any remaining offline recovery path worth trying with the standard
dm-thin/LVM tools?
Hi
Very extensive report - but it looks like the key element here would be -
what are the versions in use.
Kernel ?
lvm2 ?
thin_repair -V ?
2. Does this failure pattern usually indicate that the mapping metadata is
beyond recovery by `thin_repair`/`thin_dump`?
3. Would it be useful to inspect the raw metadata image further, and if so,
what specific tools or commands would you recommend next?
I can provide any command output that would be useful.
If you are using latest tools - then authors of this tool will need to have
access to the damaged metadata whether there is something that can be
recovered.
It'd also greatly help knowing what kind of 'damange' may have caused this.
Regards
Zdenek
