Fixing failed lvm recovery
8 views
Skip to first unread message
hut7no
Mar 8, 2020, 2:39:39 PM3/8/20
to qubes...@googlegroups.com
I recently deleted three large AppVMs on accident.
I panicked and shut off my computer to avoid writing.
The AppVMs were on a secondary usb drive, configured as show in the qubes documentation.
I tried to recover using the relevant /etc/lvm/archive/ files with vgcfgrestore and ended up using --force since I'm using thin volumes.
I used --test, it seemed to work, then I ran the command without --test, for each .vg file, from most recent to the oldest relevant file.
Once I tried to activate the volume group with vgchange -ay qubes, I got errors saying the transaction_id was wrong.
Lvscan shows the whole drive as inactive.
Is there anything I can do to fix this, or at least recover some individual files?
Thank you in advance.
I panicked and shut off my computer to avoid writing.
The AppVMs were on a secondary usb drive, configured as show in the qubes documentation.
I tried to recover using the relevant /etc/lvm/archive/ files with vgcfgrestore and ended up using --force since I'm using thin volumes.
I used --test, it seemed to work, then I ran the command without --test, for each .vg file, from most recent to the oldest relevant file.
Once I tried to activate the volume group with vgchange -ay qubes, I got errors saying the transaction_id was wrong.
Lvscan shows the whole drive as inactive.
Is there anything I can do to fix this, or at least recover some individual files?
Thank you in advance.
Reply all
Reply to author
Forward
0 new messages