On Sun, May 31, 2020 at 01:57:24PM -0700, Boot problems wrote: > /dev/xvdi but using that it just says permission denied.
so use "sudo fdisk -l /dev/xvdi" > the cryptsetup luksOpen /dev/xvdi2 name, then it says access denied, I so use "sudo cryptsetup luksOpen /dev/xvdi2 name" > can seemingly unencrypted it from the gnome-disks GUI but not mount it. it contains an lvm stack, so there will be many virtual volumes inside. after the luksOpen, check "ls -al /dev/mapper/*-private" and look for the devices with the names of your old VMs. you should be able to mount these. hint: use "sudo mount /dev/mapper/whatever-private /mnt/whatever" hint2: you will have to replace the "whatever" part there. hint3: you will have to "sudo mkdir /mnt/whatever" or create new VMs, and restore the whole private volumes with dd. > However I tried booting up the old hdd again and now it works as long > as the ssd is connected too but all my data is gone and is just a > clone of the new ssd, without the ssd connected it doesn't boot up > like before, I guess it has been formatted then, is there a way to that sounds more like you are just booting from your ssd into the fresh install. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20200531211905.GD1079%40priv-mua.
