My generic brand 256G 2.5" SATA SSD (from sources unknown) was showing signs of failure (unrecoverable data in one of my VMs and a few other issues) so I used Clonezilla to push it over to a 2TB 2.5" SATA SSD (CT2000MX500SSD1).
First, Clonezilla failed to clone a bootable drive the first go so I had to set the --recover flag. This allowed it to clone but it wouldn't boot, so I cloned again with sector-by-sector mode and that was bootable into PVE, but now when it tries to launch my containers, I get:
TASK ERROR: activating LV 'pve/data' failed:
I naturally get this on every container since the ENTIRE data volume isn't mounting.
Made a dump at ~/lvbackup. It shows:
Any guidance would be awesome. Answers would be awesome too, but I'm here to learn. If push comes to shove I'll just restore from backup but all the data exists so I'd love to watch it all come back together.
Extra info:
meta_1 and 2 were generated from attempts at lvconvert --repair.
I'm going to stop here for the moment as I'm getting thick in the weeds (yak shaving, no?) and probably need to back off lol
First, Clonezilla failed to clone a bootable drive the first go so I had to set the --recover flag. This allowed it to clone but it wouldn't boot, so I cloned again with sector-by-sector mode and that was bootable into PVE, but now when it tries to launch my containers, I get:
TASK ERROR: activating LV 'pve/data' failed:
Code:
Thin pool pve-data-tpool (252:6) transaction\_id is 0, while expected 1680.Made a dump at ~/lvbackup. It shows:
- data transaction_id = 1680 (not 0 like the error states, so this must be the source of the error's expectation)
- All my containers have unique Transaction IDs
Any guidance would be awesome. Answers would be awesome too, but I'm here to learn. If push comes to shove I'll just restore from backup but all the data exists so I'd love to watch it all come back together.
Extra info:
- I resized the partition and then expanded the volume to fill. I was getting the error before I did that, however, and it appears the resize was successful and not part of the issue.
- lvdisplay shows all my containers with LV Status NOT available (naturally)
- I ran lsblk:
Code:
sda 8:0 0 1.8T 0 disk
├─sda1 8:1 0 1007K 0 part
├─sda2 8:2 0 1G 0 part /boot/efi
└─sda3 8:3 0 1.8T 0 part
├─pve-swap 252:0 0 4G 0 lvm \[SWAP\]
├─pve-root 252:1 0 66.6G 0 lvm
├─pve-data\_meta0 252:2 0 1.4G 0 lvm
└─pve-data\_meta1 252:3 0 1.4G 0 lvm
└─pve-data\_meta2 252:4 0 1.4G 0 lvmmeta_1 and 2 were generated from attempts at lvconvert --repair.
I'm going to stop here for the moment as I'm getting thick in the weeds (yak shaving, no?) and probably need to back off lol
Last edited: