I can’t install Qubes OS. When I click on ‘Install,’ it just shows me some logs and gets stuck on that log screen. I have no idea what is happening, since I have installed Qubes OS on this same machine before. However, I removed it because I needed direct access to my hardware recently.
1 Like
what’s your hardware?
2 Likes
What was the last working Qubes OS version on the machine?
1 Like
I’m not sure, but I think it was Qubes 4.2.1. I used it at the beginning of 2024, in February/March. My hardware:
CPU: Ryzen 7 5800x
Motherboard: Gigabyte B550M Aorus Elite
BIOS Version: FFC (Sep 02, 2024)
BIOS Version i was using on my last Qubes OS installation: FB (Nov 18, 2022)
Hard Disk: SSD Corsair MP600 Core XT 4TB
RAM: Corsair 128GB(4x32)
GPU: GTX 1060 6GB Galax OC
1 Like
Someone can help me?
1 Like
Hmm… The last thing I can see there relates to the NVMe drive. Here’s a few things to try:
Try prepping your SSD in a LiveISO such as Debian and format the drive (at least create a fresh partition table).
Swapping SSD out for another.
Ensure SSD works in another OS and computer.
2 Likes
I already tried these steps and none of them worked for me, unfortunately. I already tried installing Debian, Ubuntu, Kali, Windows 10/11, all of these OSes just for testing purpose and all of them worked perfectly. Installed without any problems as Live ISO too. Tried reseting my BIOS to default settings (since the 1st time i installed Qubes my BIOS was on default settings.), i tried to reseting my SSD with this command (dd if=/dev/urandom of=/dev/nvme0n1 bs=1M status=progress) and didn’t work too.
1 Like
The only significant change I made during that time frame was updating my BIOS to the latest version to improve security. Below is the update log from the official Gigabyte website
My BIOS version when i was using Qubes: FB/FE
My actual version: FFc
1 Like
Try to downgrade the bios one version at a time to see if it works, if so, you have to decide between updating back to the newer firmware version and write a bug report because Qubes OS is incompatible due to something, or use Qubes OS on an older firmware.
1 Like
It could be a similar issue:
https://bugzilla.redhat.com/show_bug.cgi?id=2271185
The thread mentions a few things you can try, like booting with rd.multipath=off
This doesn’t happen on F40 because starting with that release, multipath automatically blacklists all nvme devices if native nvme multipathing (the default) is detected.
It sounds like part of the problem could be that dom0 is using an older version of Fedora.
1 Like
In addition, you could try installing using kernel-latest (I think the installer is on 6.10 right now).
1 Like
None of the solutions above fixed the problem, unfortunately. To be honest, i haven’t tried yet to Downgrade my BIOS version, according to Solene and don’t want to. I was facing problems with older versions of my BIOS and don’t want to downgrade it just to use Qubes. So i will not install qubes right now, but if someone has another solution to give to me, sure i will try. Thanks everyone for now!
1 Like
Just a quick observation, if the only prior thing that you can think of doing which might impact this was the BIOS upgrade & your system is an AMD made by Gigabyte…I know of some settings that I regularly have to redo every time that I update a known system of that combination that impinge upon proper Qubes operations. You maybe could check on the settings before you downgrade your BIOS. The SVM perhaps?
1 Like
Okay, try installing Qubes OS on a USB drive and booting from that instead to fault isolate.
I already checked my settings, reset them to the default ones, but it didn’t work either. My current BIOS settings are: SVM enabled, IOMMU enabled, DMAA enabled, TPM and Secure Boot disabled (because I can’t boot the Qubes installer with Secure Boot enabled), and that’s it. My first Qubes installation attempt was with the default settings, and my latest attempt was also with the default settings. I apologize, this was my mistake—I’ve just remembered that I tried to install Qubes before updating my BIOS to the latest version, so the updated BIOS has nothing to do with the issue.
1 Like
How can i do that? SInce i cannot even acess the installer to select the drive i want to install Qubes
1 Like
Just a reminder to anyone else tripping thru here that some manufacturers do reset such a setting on updating BIOS & otherwise @connor.blane forget about this portion. However, if you look thru the forum - search or someone else comes forward - I could have sworn that some others had had to turn IOMMU off to get their Qubes installation at first. Not like I have every forum post memorized so you should search while others consider it…for example one post that I just pulled up just to add an edit: Qubes 4.1 Not booting after bios update please help although this one might have a better take on it: I can only install Qubes OS without IOMMU but then it doesn't work correctly
2 Likes
The only reason I think caused the issue is the new version of Qubes, since the last time I installed it successfully was the 4.2.1 version. But I cannot install the older version now. I renember they used to let you download the older versions
1 Like
I understand what you’re suggesting, but the default settings of my BIOS have IOMMU disabled, as well as Secure Boot, DMA Protection, Memory Encryption, and many others. Since my first Qubes installation was with the default settings of my BIOS, I don’t think the problem lies in the BIOS settings. Unfortunately, I can’t provide any more explanation about my problem, since even the “verbose” installation stops at “cancel-multipath-wait-nvme0n1.timer…”.
1 Like
If you have a different and separate computer available, you can install Qubes OS onto a USB drive through that installation wizard, then attempt to boot from it on this previously working machine to potentially bypass this NVMe issue.