user10
September 6, 2024, 10:12am
1
I am a beginner, so please bare with me. I will try to be as detailed as possible.
I have tried to install Qubes (version 4.2.2) from two different USBs on a machine running fedora workstation (latest version). I have done this with the dd command, and I have verified the signatures & all downloaded files successfully. Verifying the written USBs has also been successful.
When I tried to install via the first USB I selected test and install Qubes and it failed the check. I tried afterwards to install (from the same USB) via the troubleshooting option to see what was wrong, Qubes installer runs normally, chose automatic configuration of an empty drive with no partitions, but then I get “An unknown error occurred” when I begin installation. When I check the debug section, it says “dnf.exceptions.Error: Some packages from local repository have incorrect checksum” and "msg: Package “{}” from local repository “{} has incorrect checksum.”
I tried another USB, 16gb. Passed all the verification checks for the written USB verification guide too.I tried to install through this one, and I get to the Qubes boot menu. But when I select any of the options to install, it gives me this error: “error: xz file corrupted or unsupported block options”.
I have tried to re-write both USBs but the same issue persists. I have enabled virtualization in BIOS and I have also enabled legacy boot. I am running a NVIDIA (NV167) graphics card so maybe that is an issue.
I have tried to re-write the USB multiple times (first with dd command, then with rufus on windows, verifying the files in both windows and fedora), and I have tried different ports. What can I do?
Thank you for your time.
user10
September 6, 2024, 11:00am
3
Thanks for your response. Just tried this (I was in the process of re-writing in Fedora again already).I ran test media and the check failed.
I then ran this:
sudo dd if=/dev/sdd bs=1M count=$(stat -c %s Qubes-R4.2.2-x86_64.iso) iflag=count_bytes | sha256sum
The check failed, it does not match the original. (When I did the verification just after writing, I ran sha256sum, md5sum, sha1sum and sha512sum, this time I skipped the rest of them due to the fail). Then I ran:
sudo dd if=/dev/sdd bs=1M count=6897252352 iflag=count_bytes | gpg -v --verify Qubes-R4.2.2-x86_64.iso.asc -
And got Bad signature. It seems something while attempting to install modifies the USB? The install destination is an external SSD drive, if that’s relevant.
Try to compare the ISO image to the USB disk like this to see where was it modified:
Check the binary changes between the images:
cmp -l file1.bin file2.bin | gawk '{printf "%08X %02X %02X\n", $1-1, strtonum(0$2), strtonum(0$3)}'
E.g.:
cmp -n $(stat -c %s Qubes-R4.2.2-x86_64.iso) -l Qubes-R4.2.2-x86_64.iso /dev/sdd | gawk '{printf "%08X %02X %02X\n", $1-1, strtonum(0$2), strtonum(0$3)}'
user10
September 6, 2024, 11:15am
5
I tried this command, and it gave an impossibly long output that’s all like this:
Spoilered because it's too big, this isn't the complete output either, it's long enough that I can't scroll far enough up to see the command I typed
`19B0081F1 00 33
19B0081F2 00 BB
What’s the output of these commands?
cmp -n $(stat -c %s Qubes-R4.2.2-x86_64.iso) -l Qubes-R4.2.2-x86_64.iso /dev/sdd | gawk '{printf "%08X %02X %02X\n", $1-1, strtonum(0$2), strtonum(0$3)}' | head
cmp -n $(stat -c %s Qubes-R4.2.2-x86_64.iso) -l Qubes-R4.2.2-x86_64.iso /dev/sdd | gawk '{printf "%08X %02X %02X\n", $1-1, strtonum(0$2), strtonum(0$3)}' | tail
user10
September 6, 2024, 11:38am
7
cmp -n $(stat -c %s Qubes-R4.2.2-x86_64.iso) -l Qubes-R4.2.2-x86_64.iso /dev/sdd | gawk '{printf "%08X %02X %02X\n", $1-1, strtonum(0$2), strtonum(0$3)}' | head
180006002 62 9D
cmp -n $(stat -c %s Qubes-R4.2.2-x86_64.iso) -l Qubes-R4.2.2-x86_64.iso /dev/sdd | gawk '{printf "%08X %02X %02X\n", $1-1, strtonum(0$2), strtonum(0$3)}' | tail
19B00AFF5 00 DD
I have no idea what could cause the USB disk modification starting with 6442475522 byte and up to 6895480831 byte specifically out of total 6895480831 bytes of the image.
Write the image on the USB disk in Fedora
Re-verify the USB disk after writing
Disconnect the USB disk and connect it back
Re-verify the USB disk after writing
user10
September 6, 2024, 11:52pm
9
I have now tried multiple times to re-write the USB in order to try this, but now, it keeps failing the check right away.
user10
September 7, 2024, 2:42am
10
Tried a final time to format and re-write the USB, this time with balenaEtcher on Linux. Immediately fails the written media check again. I will buy a new USB and report back. Hopefully maybe that can fix it, in case someone also has the problem in the future. Other than that I don’t know what else to try.
user10
September 7, 2024, 11:55pm
11
I have successfully installed Qubes with a new USB, in case anyone has this issue in the future.