Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • After having read that several times I am still not sure what your disk looked like. What layer is encrypted, the whole disk, a single partition, an LV? What is the PV? "so I chose to copy the table to the disk" - Does that mean you had a partition table within a LUKS volume / disk and have copied that to the disk itself? That would have destroyed the LUKS header. Commented Nov 22, 2014 at 2:16
  • Run the command vgchange -ay fedora_hostname. After that what is the output of vgdisplay -v fedora_hostname? Commented Nov 23, 2014 at 5:54
  • I think it's not a problem that the sda2 UUID is reused in DM device names. Probably means: "This is the decrypted version of $UUID". That it is detected as PV but cannot be scanned may mean that the LVM metadata has been destroyed. If the LVs have been created without fragmentation then it should be possible to recreate them (with the correct size) to get access to the data. I am not familiar with testdisk but it should show you where the LVs are. You need to know their size and must (re)create them in the right order. IMHO this cannot cause (more) damage. Commented Nov 24, 2014 at 4:48