I’m trying to recover data from one of my SSDs. The boot Qubes disk is still OK. It contains partial volunes for everything. Does it also contain a list of the block location of the “missing” partitions / data on the SSD which I have a problem with?
qubes-prefs or /etc/fstab may help
My Qubes data uses a logical volume across the two drives (one good, one problem) . I can open the OK SSD’s encrypted LUKS with this:
sudo cryptsetup luksOpen /dev/nvme1n1p6 small6
But I get this error trying to mount it “unknown filesystem type ‘LVM2_member’.” I guess because it is a logical volume and the system wants the rest of the volume on the other drive.
sudo vgdisplay and sudo lvscan both say the logical volumes are inactive because of the missing data on the other drive.
I wonder if I can issue commands which will tell me where Qubes thinks the missing partition on the SSD should be, and perhaps other parameters that would help me to recover it.
sudo vgdisplay WARNING: Couldn't find device with uuid 4VL0R0-xnFu-FYgn-rfDt-Ntzy-chWu-E2Y9Q1. WARNING: VG qubes_dom0 is missing PV 4VL0R0-xnFu-FYgn-rfDt-Ntzy-chWu-E2Y9Q1 (last written to /dev/mapper/luks-06277963-a537-4c7e-a81e-8c114b7854ef). --- Volume group --- VG Name qubes_dom0 System ID Format lvm2 Metadata Areas 1 Metadata Sequence No 157991 VG Access read/write VG Status resizable MAX LV 0 Cur LV 169 Open LV 0 Max PV 0 Cur PV 2 Act PV 1 VG Size <313.59 GiB PE Size 4.00 MiB Total PE 80279 Alloc PE / Size 64223 / 250.87 GiB Free PE / Size 16056 / <62.72 GiB VG UUID XTvHu6-sGuM-x0SZ-4foo-37ow-KhvH-FvhXtd Can I issue command sudo vgdisplay WARNING: Couldn't find device with uuid 4VL0R0-xnFu-FYgn-rfDt-Ntzy-chWu-E2Y9Q1. WARNING: VG qubes_dom0 is missing PV 4VL0R0-xnFu-FYgn-rfDt-Ntzy-chWu-E2Y9Q1 (last written to /dev/mapper/luks-06277963-a537-4c7e-a81e-8c114b7854ef).
open both drive and run
vgchange -ay then mount your lv
The other drive got formatted but the data is seemingly there. That is why I am trying to find out where partitions are.
ah, try check in /var/log/anaconda/storage.log
but since you cannot mount your root partition, i dont have idea.
but try opening the drive that working and run vgchange -ay and mount it, it may work
ACTIVE ‘/dev/qubes_dom0/swap’ [<7.29 GiB] inherit
The others say:
Refusing activation of partial LV qubes_dom0/root. Use ‘–activationmode partial’ to override.
Will it be destructive if I try to open any of those that refused? What do I want, root, or something else?
its recommended that you have backup first, then you can partially active the root, the log is inside root.