! qubes won't boot - no access to data - please help

[IT Geek]

Hi,

my qubes installation won't boot, I have no backup... :/

I started it today, dom0 started but any of the VMs could'nt start. there was an error:

"domain has failed to start volume qubes_dom0/vm... missing" - more less. I cant remember exact error

then I rebooted the machine and I failed completely...

I have error:

.
error: unknown filesystem
Entering rescue mode
grub rescue>



Is it possible to mount drive with qubes in other system and rescue my data? I have the encryption password

[awokd]

IT Geek:

Yes, you should be able to mount the drive either in another system or
with a rescue boot CD/image on the same system. Look for cryptsetup +
LVM recovery.

--
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots

[pkw]

W dniu niedziela, 8 grudnia 2019 16:20:20 UTC+1 użytkownik awokd napisał:

Yes, you should be able to mount the drive either in another system or
with a rescue boot CD/image on the same system. Look for cryptsetup +
LVM recovery.

--
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots

Thank you for the answer, just burning qubes usb.

Once I mount main system, where to look for for the private VM files? I would like to copy it to some other drive, I suspect the one I have now is faulty.

[pkw]

not god... qubes rescue mode  doesn't work..

.

It asks to choose from 4 options, when I chose to mount as read-only it asks me for LUKS password for sda2,

when I enter it there is a message that I don't have any Linux partitions..

Any clues how to proceed?

[awokd]

pkw:

Check
https://www.mail-archive.com/qubes...@googlegroups.com/msg22764.html
for some ideas.

[pkw]

W dniu niedziela, 8 grudnia 2019 16:56:20 UTC+1 użytkownik awokd napisał:

Check
https://www.mail-archive.com/qubes...@googlegroups.com/msg22764.html
for some ideas.

--
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots

I'm stuck ...

root@X230:/qubes# ls -la /dev/mapper/
total 0
drwxr-xr-x  2 root root      80 Dec  8 17:50 .
drwxr-xr-x 21 root root    4460 Dec  8 17:50 ..
crw-------  1 root root 10, 236 Dec  8 17:26 control
lrwxrwxrwx  1 root root       7 Dec  8 17:50 qubes -> ../dm-0

root@X230:/qubes# lsblk
NAME      MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sda         8:0    0 119,2G  0 disk 
└─sda1      8:1    0 119,2G  0 part  /
sdb         8:16   0 931,5G  0 disk 
└─sdb1      8:17   0 930,6G  0 part  /media/user/1tb-ext4
sdc         8:32   0 465,8G  0 disk 
├─sdc1      8:33   0     1G  0 part 
└─sdc2      8:34   0 464,8G  0 part 
  └─qubes 253:0    0 464,8G  0 crypt

root@X230:/qubes# mount /dev/mapper/qubes /qubes
mount: /qubes: unknown filesystem type 'LVM2_member'.

root@X230:/qubes# lvmdiskscan
  Incorrect metadata area header checksum on /dev/mapper/qubes at offset 4096
  /dev/mapper/qubes [    <464,76 GiB] LVM physical volume
  /dev/sda1         [     119,24 GiB]
  /dev/sdb1         [     930,61 GiB]
  /dev/sdc1         [       1,00 GiB]
  /dev/sdc2         [     464,76 GiB]
  0 disks
  4 partitions
  1 LVM physical volume whole disk
  0 LVM physical volumes

[pkw]

also:

root@X230:/qubes# vgscan
  Reading volume groups from cache.
root@X230:/qubes# vgscan --cache

  Incorrect metadata area header checksum on /dev/mapper/qubes at offset 4096
  Incorrect metadata area header checksum on /dev/mapper/qubes at offset 4096
  Incorrect metadata area header checksum on /dev/mapper/qubes at offset 4096

  Reading volume groups from cache.

[awokd]

pkw:

>
>
> W dniu niedziela, 8 grudnia 2019 18:13:58 UTC+1 użytkownik pkw napisał:

>> *sdc 8:32 0 465,8G 0 disk ├─sdc1 8:33 0 1G 0 part
>> └─sdc2 8:34 0 464,8G 0 part └─qubes 253:0 0 464,8G 0 crypt*

>>
>>
>> root@X230:/qubes# mount /dev/mapper/qubes /qubes

>> *mount: /qubes: unknown filesystem type 'LVM2_member'.*

Did you cryptsetup open somewhere in there? You may also need to install
the LVM thin package, I think it's named thinprovisioningtools.