Error during installation

[N00b5926]

I’m trying to install Qubes on my Thinkbook 14 g8 IAL.

The media test shows an error and won’t proceed to the installation screen. Even if I skip the media test and proceed with the installation, an error occurs midway and it fails to install properly. I used GNOME Disk Tool to burn the ISO.

Can someone help me?

[murdock]

Hi @N00b5926
Please follow the documentation at Installation guide — Qubes OS Documentation.

sudo dd if=Qubes-RX-x86_64.iso of=/dev/sdY status=progress bs=1M conv=fsync

Maybe the Gnome Disk Tool is not the right tool for creating the installation media. The fact, that the media test won’t be successful, is another point in the right direction.
Additional question: Do you’ve test the downloaded iso file as recommended at Verifying signatures — Qubes OS Documentation?
An corrupted iso file can be the reason for such errors also.

[Zrubi]

Also make sure if you have a big enough USB pendrive.
I have found out that the 4.3 .iso can’t really fit on my 8GB pendrive. Thanks to the ‘fake’ units used by the marketing teams!

[N00b5926]

When I used the dd command to write an ISO file to a USB drive and booted from that USB, it didn’t proceed to the installation screen and stopped at GRUB.

Does this mean it failed?

[murdock]

Hmm, not sure, what you mean with “stopped at GRUB”.
The QUBES installation media boots via GRUB also, on the screen you have then the options to proceed with installation and verify the media or to proceed without verify.
If you mean your default GRUB screen (from your existing OS), then yes, it fails to boot from your installation media.
Sometimes, GRUB is a little bit picky, so maybe try to use another USB-Stick (if you have one more).

[murdock]

And very important, use as target for the dd command the whole stick, not any partition on it (for example /dev/sda, not /dev/sda1).

[parulin]

@murdock

Maybe the Gnome Disk Tool is not the right tool for creating the installation media.

That’s the recommended tool to install Tails OS, so why not?

@N00b5926

Does this mean it failed?

You can re-verify the USB stick:

Verifying signatures

[N00b5926]

Stopping at GRUB means it doesn’t proceed to the installation screen.

I verified the ISO file, of course.

[N00b5926]

Whether using a USB drive with the dd command or one tested with GNOME Disk Utility, testing the media in Qubes OS results in failure.

Is there any solution? Should I try another USB drive?

[parulin]

@N00b5926

Should I try another USB drive?

Yes

[N00b5926]

I always get stuck at this screen and cannot complete the installation properly.

I have updated the drivers to the latest version.

I will try using a different USB flash drive later.

[alannis]

This issue has come up before on this forum. It is not a USB drive issue. Although i am not sure how to fix.

Fresh installation sys-firewall reset PCI device error at the end

Hi, I did fresh install of Qubes 4.1 with virtualization enabled. At the end of the installation I got an error(?) at the end. [ I did not pasted the exact text, but it is the same as the one below, with probably different pci device number ] [’/usr/bin/qvm-start’ ‘sys-firewall’] failed: stdout: “” stderr: "Start failed: internal error: Unable to reset PCI device 0000:03:00.1: internal error: Active 0000:03:00.0 devices on bus with 0000:03:00.1, not doing bus reset. see /var/log/libvirt/l…

PCI troubleshooting

Install failed near very end with the "Unable to reset PCI device". It boots but cannot run any qubes

I just installed 4.2.2 ISO on my Dell Precision 3650 64BG RAM, 4TB HD, & 6-core I5-10505. So its a solid machine. Install seemed to go well until the very end, with sys-firewalll reporting: [‘/usr/bin/qvm-start’, ‘sys-firewall’] failed: stdout: “” stderr: "Start failed: internal error: Unable to reset PCI device 0000:00:1f:6: no FLR, PM reset or bus reset available, see /var/log/libvirt/libxt/libxt-driver.log for details It did seem to boot though, but all qubes now fail with both sys-ne…

[N00b5926]

Thank you for your reply.

When this error message appears,

does that mean there is no solution?

[alannis]

After the problem appears as you show in your screenshot are you able to reboot the computer and log into Qubes? If you can, then you could try the following. Otherwise, there should be a way to do this pre-boot?

Installing Qubes - Unable to reset PCI Device

First, check that is actually the case: $ qvm-pci ls sys-firewall If there is indeed a controller attached to sys-firewall, detach it: $ qvm-pci detach sys-firewall [BACKEND:DEVICE_ID] The [BACKEND:DEVICE_ID] looks something like this: dom0:0x_xx.x Depending on your case, you may want to attach the extra controller to sys-net: $ qvm-pci attach sys-net dom0:0x_xx.x

[N00b5926]

Yes, I am able to log into Qubes. I’m sorry, but since I find it difficult to handle this issue myself, it would be helpful if you could create some sort of guide.

[N00b5926]

The sys-net device section displayed “00:1f.6 Network: Intel Corporation Unknown PCI Device” as enabled.

Disabling this allowed sys-net and sys-firewall to start.

However, I cannot connect to the internet in this state.

Is there a solution?

[murdock]

The error says, that the PCI device does not react properly to an reset. This is not a big problem and you can try to solve it in that way (according to PCI troubleshooting — Qubes OS Documentation):

• Go to the sys-net VM settings
• Go to Devices
• Make sure the device is in the right field
• Click “Configure strict reset for PCI devices”
• Select the device, click OK and apply

[N00b5926]

Thank you for your prompt reply.

May I ask one more question?

When I install Qubes and insert a USB drive, it says it can’t mount. Is there a solution?

[murdock]

Hmm, not completely sure, what you mean.
Is it, when you have Qubes installed and runs normally or is it during installation?
When you have Qubes installed and running normally, then app Qubes, based on both standard templates (Debian13 and fedora 42) supports alot of Filesystem types (ext3,4,ntfs,fat32,…) even windows encrypted filesystems (BitLocker).
If you have Qubes running normally:

• insert your USB-Stick
• start the App Qube, that you will mount the USB-Stick onto.
• open the devices shortcut (top of screen, right side)
• attach the filesystem (the complete USB-Stick like /dev/sdb, not /dev/sdb1!) to the App-Qube.
• open a filemanager in the App Qube (for example thunar)
• click on the USB filesystem (left side list) to mount it
• don’t forget to unmount the mounted USB stick, before you pull it out from your computer (to prevent damages on the filesystems of the USB stick)

[N00b5926]

I apologize for the delayed response.

First, since an error occurred during installation, the system is likely not in a normal state.

Is there a solution to this problem?