as you can see here the software area just keep loading when i set it up,
everything else works fine, but i just can’t continue without it
any clarifying question will be answered, as i don’t know what more information i should give
1 Like
Did you verify your ISO with matching the checksums after download?
I think something might be wrong with the installation medium.
1 Like
it’s working, i installed Qubes, but after reboot and pressing finish configuration, it’s loading and then give this error
can any one help
1 Like
Hi uyuiyui
Can you share a bit about the hardware you are trying to install Qubes OS on (CPU/GPU/disk)?
You could try to skip the “Initial Setup” – that will leave you with a dom0 … but once you have dom0, you can open one terminal and run:
sudo /usr/libexec/initial-setup/initial-setup-graphical
and at the same time (from a second terminal) access the log files listed in the error.
1 Like
hi ChrisA
thanks for replying
here are my specs:
Ultra 9 285k
Gigabyte z890 aorus elite wifi 7
Corsair ddr 2x48gb
Gigabyte aorus nvme 2tb pcie5
Gigabyte aorus nvme 2tb pcie4
Next water cooler 360mm led
Gigabyte rtx5090 gaming oc 32gb
Super flower leader 1300w gold pcie5
i will try to get the logs and add it to this message
1 Like
Hi uyuiyui
Can you try:
fdisk /dev/nvme0n1 -x | grep sectors
and
fdisk /dev/nvme1n1 -x | grep sectors
and share the output?
1 Like
sorry it took 3 days, here is the outputs of the commands
i tried to do fresh install again
and this is a media check before the installation
i tried both torrent and non torrent download
the same result
even tried linked mirrors
I take back all my suggestions. just to be on the correct side, I created a Qubes4.4.2 ISO on a USB flash drive, and the self verification failed just as yours does…
I searched for why the verification might have failed in the past.
i found a note in github that at one time, earlier version of Qubes, the same exact failure of self verification occurred at about 4 percent. Their finding was that the at some time the USB flash drive upon which the Qubes ISO was installed had been put into a Windows computer.
I ripped open a brand new package to a USB Flash drive, USB 3.2.
I used the tool in Mint Linux, “USB Image Writer” to put Qubes.4.2.4 ISO onto the Flash drive. What I know so far is that the self verification gets to 100 percent completion.
so should i make bare metal mint installation and from that make the qubes os
and i need a new usb?
It is what I would try. but, I gotta be honest. I have never seen this error message before, failure to verify. I am suspicious about others hardware, whether it will easily take Qubes, and what special thing the person doing the install is doing. That is, some try a dual boot, and don’t tell us when asking questions. Some more advanced pieces of hardware are not accounted for yet in the Qubes. You mention an Ultra 9, I think you might required a later kernel, that question is really beyond my experience. The later kernel in the install might not have the verification. But that only means, if you run the verification, and it completes correctly and the install crashes again, you would try the later Kernel.
I receive Social Security, and as I am poor, I am usually hesitant to recommend to spend even a little money. Like buying a new USB. Or whether there is an easy way to overwrite the USB you have. and be sure nothing on it is corrupted.
but yeah, Bare Metal Mint. to download the Qubes ISO.
Use Mint to write the image to the -Qubes 4.2.4 ISO to the USB.
I read in the HCL that others have Ultra 9. and seems to work.
Then the next stumbling block would be to make sure that Qubes ISO is set to handle the graphics card.
Likely you have seen that. Not sure how much more advanced what they installed than the standard Qubes ISO, or whether the standard Qubes ISO would not work.
and just write over the Mint, not attempt a dual boot. While I would guess you are the kind of person who is attentive to detail. Make sure the BIOS/EFI is set to Legacy, and the virtualization is turned on.
So, ?? I am a person who tries things. I don’t always try to spend a lot of time analyzing error messages, which some here are more competent to do than myself.
So if it failed while trying to write over the Mint Linux on the drive, I would format the drive and try again.