Hello. I had qubes installed using Legacy. Sold the old computer and kept the SSD. Bought a new one and there was only UEFI. The BIOS detects the SSD without any problems and that’s where the good news ends: it doesn’t boot, using the rescue mode didn’t help. An attempt to mount it from under the new system didn’t work. I assume that I’m not the only one with this problem, maybe there is already a solution or everything is bad?
I’m not certain but I think you are out of luck with this. But if you have a secondary computer with legacy bios that meets qubes os system requirements then you can create a qubes backup and then you can go back to your uefi laptop and install qubes os and then restore the backup.
Doing backups really is 101. You should have made one already before.
Legacy and UEFI partition the drives differently. Legacy has two partitions, UEFI has three
Some laptops seem to only have UEFI but often there is a bios option to support legacy as fallback
What exactly you tried in the attempt to mount the contents of your SSD that has a “legacy” disk partition table, which would be Master Boot Record type partition table, is not clear. What is suggested below is a bit of a shot in the dark.
You should be able to attach, say /dev/sdc, instead of /dev/sdc1 to a qube. In that qube, when you run parted /dev/sdc print, you should see the partitions.
Well. I use in dom0 sudo fdisk -l and then qvm-block attach work dom0:sda.
In qube work i again use sudo fdisk -l and now its xvdi (with xvdi1 and xvdi2) i found it by disk identifier and volume.
Then i try sudo cryptsetup luksOpen /dev/xvdi samsung and got answer Device /dev/xvdi is not a valid LUKS device. Whats next?
Try it with /dev/xvdi2