Hello. Friend asked me to install the Qubes system on an external drive, I had the test version 4.2 rc.1 and it was an error. After the installation, the grub of My Qubes was corrupted on my PC and after installation it did not work what i show later.
After reinstalling on external SSD to stable version 4.1.2, Qubes already works on his external disk but now my is damaged.
When boot i have this announcement :
error : no such device ( and here number id … this external disk not mine )
error : unknow filesystem
can do it from the qubes terminal on an external drive ? it seems that in my case it will be sda1 which has 1 GB sda2 is the main qubes partition (but i see it havent /boot like for sda1 like it is on sdb1 1GB (external drive with qubes) , but how to choose the purpose so that the changes are only on the sda1 partition, what should I enter in the terminal earlier… isn’t that the point? or maybe i should reinstall grub but the same question how do it step by step from cli for this case
Do you have Qubes OS installed using UEFI or Legacy BIOS mode?
If it’s UEFI and assuming your Qubes OS drive is sda then sda1 should be EFI System partition, sda2 should be boot partition and sda3 should be main Qubes OS partition.
You can boot from any LiveUSB OS or from Qubes OS installed, mount your Qubes OS EFI System partition (sda1) there and add the required changes.
This is the Legacy BIOS mode, so the disk of my Qubes is SDA and there are only two partitions :
sda1 1GB (without mountpoint like : /boot) and sda2 main partition 500GB
I’ve read more or less on the forums but I don’t want to screw anything up so as not to have another problem to fix, so if you would be so kind as to tell me in such a scenario that I’m already on the live USB system, I run the terminal and what next?
The issues that I linked are only applicable for the EFI systems so that problem is not the issue that you’re facing.
You can try to fix up your like this:
First boot into any LiveUSB OS or in Qubes OS installer, mount your system (either manually or automatically if you’re booting from Qubes OS installer in rescue mode), chroot into it and then fix grub config:
I previously tried to run it from another disk with fedora39 from grub like “Windows 10” (dev/sda1) and :
error …/…/grub-core.commands/search.c.315:no such device: (number like 6857ED75 etc.)
setting partition type to 0x83
error: …/…grub-core/loader/i386/pc/chainloader.c213: invalid signature
Okay, someone tell me if it makes sense and is possible to create an image of an encrypted disk with Qubes, then reinstall cleanly Qubes and then replace the new partitions with this created image. Will this work well ?
Because I don’t consider it safe to copy all from a decrypted disk to another (used) USB and do it on new Qubes.
It’s possible but for it to work you’ll need to change the UUIDs of your encrypted disk, dom0 root and boot partitions in dom0 root and boot partition configs and have the same kernel boot files (initramfs, vmlinuz) in old boot partition that you have in new Qubes dom0.