Help needed getting vm and its data back from a broken install.

[Savicks]

Something broke with my Proxmox and it would not boot anymore. I really wanted the contents of some files that was on the VM so I decided to install Proxmox on another ssd that I had and got it up and running. Now I want to add the old ssd with the old VM inside to get this back but I can't seem to figure out how to get it back. When I try to mount the lvm group I get an error message:


I don't know what to do at this point. is there anyone who can help?

 

[bbgeek17]

I don't know what to do at this point. is there anyone who can help?

I think you are going to need to get familiar with Linux command line, and LVM specifically. The PVE GUI is not designed to handle special cases, like the one you have.

This might be a good place to start https://linuxhandbook.com/lvm-guide/
It shows how to list what you have and understand relationship between disks and LVM architecture (dont create or remove anything yet).

Given that you are trying to recover disk that used to serve as PVE installation, you likely have a name conflict. Once you get a better view of what you have from CLI, come back here with that information and someone might be able to help.

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[Savicks]

I will output what I could get from the check commands to not alter any data so far.

pvdisplay outputs:

WARNING: Metadata location on /dev/sda3 at offset 22016 begins with invalid name.
WARNING: Checksum error on /dev/sda3 at offset 22016.
WARNING: invalid metadata text from /dev/sda3 at 22016.
WARNING: metadata on /dev/sda3 at 22016 has invalid summary for VG.
Retrying metadata scan.
WARNING: Metadata location on /dev/sda3 at offset 22016 begins with invalid name.
WARNING: Checksum error on /dev/sda3 at offset 22016.
WARNING: invalid metadata text from /dev/sda3 at 22016.
WARNING: metadata on /dev/sda3 at 22016 has invalid summary for VG.
WARNING: bad metadata text on /dev/sda3 in mda1
WARNING: scanning /dev/sda3 mda1 failed to read metadata summary.
WARNING: repair VG metadata on /dev/sda3 with vgck --updatemetadata.
WARNING: scan failed to get metadata summary from /dev/sda3 PVID cbWAcI0U0PeNGZLGj0KdejQy232lJP8p
--- Physical volume ---
PV Name /dev/sdb3
VG Name pve
PV Size 446.13 GiB / not usable <1.82 MiB
Allocatable yes
PE Size 4.00 MiB
Total PE 114209
Free PE 4097
Allocated PE 110112
PV UUID kIbF2u-Fglt-vbFh-bRlb-5m4u-TFLa-VY4TcM

WARNING: PV /dev/sda3 is marked in use but no VG was found using it.
WARNING: PV /dev/sda3 might need repairing.
"/dev/sda3" is a new physical volume of "<222.57 GiB"
--- NEW Physical volume ---
PV Name /dev/sda3
VG Name
PV Size <222.57 GiB
Allocatable NO
PE Size 0
Total PE 0
Free PE 0
Allocated PE 0
PV UUID cbWAcI-0U0P-eNGZ-LGj0-Kdej-Qy23-2lJP8p




vgs outputs:
WARNING: Metadata location on /dev/sda3 at offset 22016 begins with invalid name.
WARNING: Checksum error on /dev/sda3 at offset 22016.
WARNING: invalid metadata text from /dev/sda3 at 22016.
WARNING: metadata on /dev/sda3 at 22016 has invalid summary for VG.
Retrying metadata scan.
WARNING: Metadata location on /dev/sda3 at offset 22016 begins with invalid name.
WARNING: Checksum error on /dev/sda3 at offset 22016.
WARNING: invalid metadata text from /dev/sda3 at 22016.
WARNING: metadata on /dev/sda3 at 22016 has invalid summary for VG.
WARNING: bad metadata text on /dev/sda3 in mda1
WARNING: scanning /dev/sda3 mda1 failed to read metadata summary.
WARNING: repair VG metadata on /dev/sda3 with vgck --updatemetadata.
WARNING: scan failed to get metadata summary from /dev/sda3 PVID cbWAcI0U0PeNGZLGj0KdejQy232lJP8p
VG #PV #LV #SN Attr VSize VFree
pve 1 3 0 wz--n- <446.13g 16.00g


vgdisplay outputs:
WARNING: Metadata location on /dev/sda3 at offset 22016 begins with invalid name.
WARNING: Checksum error on /dev/sda3 at offset 22016.
WARNING: invalid metadata text from /dev/sda3 at 22016.
WARNING: metadata on /dev/sda3 at 22016 has invalid summary for VG.
Retrying metadata scan.
WARNING: Metadata location on /dev/sda3 at offset 22016 begins with invalid name.
WARNING: Checksum error on /dev/sda3 at offset 22016.
WARNING: invalid metadata text from /dev/sda3 at 22016.
WARNING: metadata on /dev/sda3 at 22016 has invalid summary for VG.
WARNING: bad metadata text on /dev/sda3 in mda1
WARNING: scanning /dev/sda3 mda1 failed to read metadata summary.
WARNING: repair VG metadata on /dev/sda3 with vgck --updatemetadata.
WARNING: scan failed to get metadata summary from /dev/sda3 PVID cbWAcI0U0PeNGZLGj0KdejQy232lJP8p
--- Volume group ---
VG Name pve
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 7
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 3
Open LV 2
Max PV 0
Cur PV 1
Act PV 1
VG Size <446.13 GiB
PE Size 4.00 MiB
Total PE 114209
Alloc PE / Size 110112 / 430.12 GiB
Free PE / Size 4097 / 16.00 GiB
VG UUID 1EvjAp-3WvF-7n52-iXCn-Zfba-jxxX-2Nb44R


Would this help in any way?

 

[bbgeek17]

Would this help in any way?

Yes, you can plug the errors into google to see how other people dealt with it. These are not PVE specific.
The error output also contains command that the system thinks might help you. Run it at your own risk.

Good luck

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[Savicks]

yeah it's not like I havent tried those. ty anyway

 

[bbgeek17]

yeah it's not like I havent tried those. ty anyway

You havent mentioned what you tried except mounting the disk and getting an error. If you think you tried all variations of metadata recovery, the the next step is to restore from backup. There is no special functionality that Proxmox contains for data recovery beyond standard LVM facilities.
You can try ddrescure as last resort.

Good luck

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox