QoS4.2.4 Freeze during usb boot paths.target - path units

User Support
1

Im trying to install QoS 4.2.4 on a Lenovo T490
I have a second model of this computer that it does work on.
Ive made the usb with Rufus - DD mode. Same way I always do.
It boots until it reach the “reached target paths.target - Path Units.” and it just sits there forever.
Ive tried redownloading the iso. Ive tried using 3 different USB. Same result.
Used diskpart and 7zip to extract the iso to the fresh made usb. Same thing.

Ive had the bios run entire diagnostics. Nothing.

I can see that previous versions of QOS have had same issues for some users.

Im a bit out of ideas here.

2

You can always try to download and install a slightly older release, like 4.2.3 or 4.2.2, because your laptop is old enough NOT to depend on newer kernels. If it works, you can upgrade normally and reach a state equivalent to 4.2.4.

3

Tried that. Even with a 4.2.0
Same result.

4

Well… you didn’t say. :smiley:

Next idea is to clobber the hard drive (ssd/nvme/whatyouhave) by running dd to zero a few megabytes at the beginning… I have vague recollection of stories about Linux installer(s) hanging/crashing while trying to figure out what - if anything - is already on the disk.

5

But shouldnt the disk only begin be loaded when you run the installer ?
Its when I boot on the USB. So at this point it shouldnt even care if there even is a disk or not. Or am I mistaken here ?

6

A simple forum search finds this thread from a while ago, where the fix seems to be: kernel-latest and check/set/reset BIOS RAID settings.

7

I found this already. And I tried that as well. Didnt work.

8

I have the same problem, if I manage to install it I will let you know. I tried to install version Qubes-R4.2.3 and Qubes-R4.2.4 only version worked Qubes-R4.1.2

9

This solution with editing GROUPS with the E button helped me

Introduction: Problem Description and System Information

The user reports an issue with installing Qubes OS versions 4.2.4 and 4.2.3 on a ThinkPad T490 laptop. During the installation process, the system hangs at the plymouth-start.service stage, preventing further installation. Notably, an older version of the system, Qubes OS 4.1.2, installs on the same hardware without any issues. The user has attempted the installation using three different USB drives, suggesting that the problem is not related to the specific installation media. Additionally, the user has provided details about the GRUB menu and messages displayed during the system boot. The fact that the older version installs correctly on the same laptop suggests that the issue lies in the changes made between version 4.1.2 and the newer 4.2.x releases.

Attempts to Resolve the Problem and Observations

The user tried to install Qubes OS versions 4.2.4 and 4.2.3, and the problem occurs in both versions. When booting from the installation media, the user observes the following messages in the GRUB menu before the system hangs:
[ OK ] Started plymouth-start.service - Show Plymouth Boot... [source](https://forum.qubes-os.org/t/installation-failed/20846) - cancel waiting for multipath siblings of nvme1n1.

After entering the GRUB menu and editing the boot options, the user sees the following configuration for the “Install Qubes OS R4.2.4” option:
setparams 'Install Qubes OS R4.2.4', multiboot2 /images/pxeboot/xen-gz console=none.
The laptop is a ThinkPad T490, and the bootable system is on a USB drive. The user tried three different USB drives, and the problem occurs each time. Qubes-R4.1.2-x86_64 installs without any issues. The issue appears to occur after starting the plymouth-start.service, suggesting a problem with initializing the graphical boot screen or related components. The successful installation of the older version points to potential changes in the newer releases that cause a conflict with the ThinkPad T490 hardware specification.

Analysis of Potential Causes Based on Forums and Documentation

Issues with plymouth-start.service

The system hanging on the plymouth-start.service could indicate various issues. In the context of installation, this might be related to corrupted installation files or kernel issues during the attempt to load the graphical boot interface. While the user is performing a clean installation, it cannot be ruled out that the ISO image is corrupted or that the kernel version in Qubes OS 4.2.x encounters an error while initializing graphics on this particular hardware. Forum users have reported similar issues, and one suggested diagnostic approach is to disable the Plymouth service in the GRUB boot parameters to see more detailed system messages.

Compatibility Issues with ThinkPad T490 in Qubes OS 4.2.x

There are threads on the Qubes OS forums regarding installation issues and functionality problems with newer Qubes OS versions on ThinkPad laptops, including errors related to PCI device reset after installation. Although this particular issue occurs during installation, it suggests potential hardware support problems in newer versions of Qubes OS on this laptop model. Numerous reports of general installation problems with Qubes OS 4.2.x, including system hangs and black screens on various hardware configurations, suggest that the user’s problem might be part of a broader pattern.

Hardware and Driver Differences Between Qubes OS 4.1.2 and 4.2.x

A key difference between Qubes OS 4.1.2 and 4.2.x is the updated Fedora base system and the Linux kernel version. Qubes OS 4.2.x uses a newer Linux kernel from the 6.x series, whereas version 4.1.2 likely uses a kernel from the 5.x series. This kernel change could lead to driver compatibility issues with certain hardware components in the ThinkPad T490, explaining why the older version installs successfully.

Potential Issues with the Installation Media

Although the user has tried three different USB drives, it is still possible that the issue lies with how the installation media was created or the ISO image itself. It is recommended to verify the checksum of the downloaded ISO image and try using different tools to write the image to USB, such as the dd tool recommended by Qubes OS. Additionally, the option “Install Qubes OS R4.2.x using kernel-latest” from the GRUB menu might help, as newer kernels may better support newer hardware or bypass errors in the default installation kernel.

BIOS Settings Impact

Incorrect BIOS settings could prevent Qubes OS from installing correctly. Key settings to check include enabling virtualization (Intel VT-x and Intel VT-d) and disabling Secure Boot. In some cases, other settings, such as display mode or DMA support, might also be important.

Role of GRUB Boot Parameters

Modifying GRUB boot parameters during the installation might help resolve installation hangs. Parameters such as nomodeset can resolve issues with graphic drivers, while plymouth.enable=0 disables the graphical Plymouth boot screen, allowing text-based messages to be displayed during boot, which may help identify the root cause of the issue. The efi=attr=uc parameter could help with some UEFI-related problems.

Known Bugs in Qubes OS 4.2.x

It is possible that the user’s issue is caused by a known bug in Qubes OS 4.2.x that was not present in version 4.1.2. Various issues with installation and booting of newer versions of Qubes OS, including installation hangs on certain hardware configurations, have been reported in forums and the Qubes OS issue tracker. In some cases, adding parameters like modprobe.blacklist=xen_acpi_processor rd.driver.blacklist=xen_acpi_processor to the GRUB boot parameters helped resolve the issue.

Recommended Troubleshooting Steps and Potential Solutions

Modifying GRUB Boot Parameters During Installation

When booting the system from USB, press the “e” key to edit the selected boot entry (usually “Install Qubes OS R4.2.x”).

  1. Add the nomodeset parameter at the end of the line starting with module2 /images/pxeboot/unlinuz. This tells the kernel not to load graphic drivers until the boot process is complete, which may resolve issues with incompatible drivers.
  2. Replace quiet with plymouth.enable=0 to disable the graphical Plymouth boot screen and display text-based messages during boot, which may help identify errors.
  3. Add the efi=attr=uc parameter at the end of the line starting with multiboot2 /images/pxeboot/xen-gz to help with potential UEFI-related issues.
  4. Add the parameters modprobe.blacklist=xen_acpi_processor rd.driver.blacklist=xen_acpi_processor to the line starting with module2 /images/pxeboot/unlinuz to block the xen_acpi_processor module, which in some cases has caused installation hangs on ThinkPad laptops.
  5. Press F10 or Ctrl+X to boot with the modified parameters.

BIOS Configuration for Optimal Compatibility

  1. Boot the laptop and enter the BIOS menu (usually by pressing F1, F2, Delete, or Esc at the start of the boot process).
  2. Ensure that Intel VT-x and Intel VT-d (or similar virtualization-related settings) are enabled.
  3. Disable Secure Boot.
  4. Check other settings, such as setting “Primary Display” to “External” if an external monitor is used during installation, and enabling “Kernel DMA Protection” and “Thunderbolt” if applicable.

Trying Alternative Installation Methods

  1. In the GRUB menu, select “Install Qubes OS R4.2.x using kernel-latest”. This option uses a newer Linux kernel, which may better support hardware or bypass errors in the default installation kernel.
  2. Try the “Troubleshooting - verbose boot” option in the GRUB menu to display more detailed messages during boot, which may help pinpoint the cause of the installation hang.

Verifying ISO Integrity and USB Creation Process

  1. Verify the checksum of the downloaded Qubes OS ISO against the official project website.
  2. Try using a different tool to write the ISO image to USB, especially the dd tool recommended by Qubes OS.
  3. If the problem persists, try using a different USB drive.

Searching Forums and Bug Reports

The user should search Qubes OS forums and the GitHub issue tracker for threads or bug reports related to Qubes OS 4.2.x installation issues on ThinkPad T490 laptops. Specific solutions or workarounds for this issue may be available.

Conclusion

The analysis suggests that the installation hang of Qubes OS 4.2.x on the ThinkPad T490 during the plymouth-start.service is likely related to changes in hardware support and drivers in the newer versions of the system, especially the new Linux kernel and updated Fedora base system. The successful installation of the older version 4.1.2 confirms that the underlying hardware is compatible with Qubes OS.