Upgrade to 7.1 gone wrong: activating LV 'pve/data' failed

P

Pride1922

Member
Dec 13, 2021
8
1
8
36
Hey guys,

I just upgrade proxmox to 7.1, everything went good. Upon reboot I get this error: "activating LV 'pve/data' failed: Activation of logical volume pve/data is prohibited while logical volume pve/data_tmeta is active. (500)".

Bash: 
root@proxmox:~# lsblk
NAME               MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda                  8:0    0 10.9T  0 disk
├─sda1               8:1    0 1007K  0 part
├─sda2               8:2    0  512M  0 part /boot/efi
└─sda3               8:3    0 10.9T  0 part
  ├─pve-swap       253:0    0    8G  0 lvm  [SWAP]
  ├─pve-root       253:1    0   96G  0 lvm  /
  ├─pve-data_tmeta 253:2    0 15.8G  0 lvm
  └─pve-data_tdata 253:3    0 10.8T  0 lvm
sdb                  8:16   0  1.8T  0 disk
└─sdb1               8:17   0  1.8T  0 part
sr0                 11:0    1 1024M  0 rom

storage.cfg
dir: local path /var/lib/vz content vztmpl,backup,iso lvmthin: local-lvm thinpool data vgname pve content rootdir,images



Any good soul that could help?

Appreciate your time.
 
Last edited:
Solution: add "thin_check_options = [ "-q", "--skip-mappings" ]" to lvm.conf

Explanation: "It's not an LVM bug, but should rather be considered a bug in Proxmox VE's (and likely Debian's) init configuration/handling. What (likely) happens is that the thin_check during activation takes too long and pvscan is killed (see here for more information)."
 
Pride1922 said:
Solution: add "thin_check_options = [ "-q", "--skip-mappings" ]" to lvm.conf

Explanation: "It's not an LVM bug, but should rather be considered a bug in Proxmox VE's (and likely Debian's) init configuration/handling. What (likely) happens is that the thin_check during activation takes too long and pvscan is killed (see here for more information)."
Click to expand...
i have same problem
TASK ERROR: activating LV 'pve/data' failed: Activation of logical volume pve/data is prohibited while logical volume pve/data_tmeta is active.
is that solution can help and not remove the data?
 
kautsaridris said:
i have same problem
TASK ERROR: activating LV 'pve/data' failed: Activation of logical volume pve/data is prohibited while logical volume pve/data_tmeta is active.
is that solution can help and not remove the data?
Click to expand...
yes, first make a local copy of lvm.conf, just in case, then add thin_check_options = [ "-q", "--skip-mappings" ] to your lvm.conf and reboot the machine.

cd /etc/lvm
cp lvm.conf lvm.backup
nano lvm.conf

inside nano is CTRL +W to search for thin_check_options, uncomment / edit it to look like: thin_check_options = [ "-q", "--skip-mappings" ] .

Save the file and reboot the server.

Hope this helps.

Edit: You will not lose any data.
 
  • Like
Reactions: wegiii
Pride1922 said:
yes, first make a local copy of lvm.conf, just in case, then add thin_check_options = [ "-q", "--skip-mappings" ] to your lvm.conf and reboot the machine.

cd /etc/lvm
cp lvm.conf lvm.backup
nano lvm.conf

inside nano is CTRL +W to search for thin_check_options, uncomment / edit it to look like: thin_check_options = [ "-q", "--skip-mappings" ] .

Save the file and reboot the server.

Hope this helps.

Edit: You will not lose any data.
Click to expand...
in command [ "-q", "--skip-mappings" ] should use space or not ?
 
That's what I mean, sorry, my English is not to good, I already write in lvm.conf and restart the server, but still the local-lvm not active
 
  • Like
Reactions: TechQI
Pride1922 said:
Solution: add "thin_check_options = [ "-q", "--skip-mappings" ]" to lvm.conf

Explanation: "It's not an LVM bug, but should rather be considered a bug in Proxmox VE's (and likely Debian's) init configuration/handling. What (likely) happens is that the thin_check during activation takes too long and pvscan is killed (see here for more information)."
Click to expand...
For other people stumbling upon this thread: This is missing the required update-initramfs -u command. Please link to the full post/thread next time.
 
Pride1922 said:
Solution: add "thin_check_options = [ "-q", "--skip-mappings" ]" to lvm.conf

Explanation: "It's not an LVM bug, but should rather be considered a bug in Proxmox VE's (and likely Debian's) init configuration/handling. What (likely) happens is that the thin_check during activation takes too long and pvscan is killed (see here for more information)."
Click to expand...
I recently encounter this issue as well." TASK ERROR: activating LV 'pve/data' failed: Check of pool pve/data failed (status:1). Manual repair required!" The first occurred after power outage 2 months ago. I was not able to fix it and I ended restalling proxmox and now it happed again yesterday. Can you explain where can I find lvm.conf and how to add
"thin_check_options = [ "-q", "--skip-mappings" ]" to lvm.conf
Click to expand...
 
Hi,
wintok said:
I recently encounter this issue as well." TASK ERROR: activating LV 'pve/data' failed: Check of pool pve/data failed (status:1). Manual repair required!" The first occurred after power outage 2 months ago. I was not able to fix it and I ended restalling proxmox and now it happed again yesterday. Can you explain where can I find lvm.conf and how to add
Click to expand...
see the full post mentioned here:
fiona said:
For other people stumbling upon this thread: This is missing the required update-initramfs -u command. Please link to the full post/thread next time.
Click to expand...

But your issue does sound different. It's not about partial activation, but about (seemingly) corrupted metadata, hence the message about the manual repair. Did you check if your phyiscal disks are still healthy, e.g. with smartctl -a /path/to/device? Any interesting messages in /var/log/syslog?
 
You must log in or register to reply here.
Top Bottom