Qubes os stuck after entry disk password

fuckedup · April 19, 2025, 1:50pm

R4.2.4, 64GB RAM, B650M HDV
Hello everyone,
My Qubes OS R4.2.4 system is getting stuck during boot at the following lines:
[ OK ] Started qubes-core-agent.service - Qubes OS daemon.
[ OK ] Finished qubes-core.service - Qubes Dom0 startup setup.
[ OK ] Started qubes-exec-policy.daemon.service - Qubes remote exec policy daemon.
[ OK ] Finished qubes-core.service - Qubes Dom0 startup setup.

My system configuration includes 64GB of RAM and an ASRock B650M HDV motherboard.
Could anyone provide some insight into why this might be happening and how I can troubleshoot or fix this issue? Any suggestions or similar experiences would be greatly appreciated.
Thank you!

OvalZero · April 19, 2025, 2:13pm

Please help us, to help you. For a start:

What Hardware are you running things on?
Fresh Installation?
If not: what version of Qubes are you using? Is there anything you did / changed before this error came up?

Please describe errors / failing steps in words and avoid pictures, since nobody can search for anything depicted.

For translation use services like DeepL.

To get even better assistance please read:

github.com/selfteaching/How-To-Ask-Questions-The-Smart-Way

How-To-Ask-Questions-The-Smart-Way.md

master

## How To Ask Questions The Smart Way

### Eric Steven Raymond

[Thyrsus Enterprises](http://www.catb.org/~esr/)


```<esr@thyrsus.com>```


### Rick Moen


```<respond-auto@linuxmafia.com>```


Copyright © 2001,2006,2014 Eric S. Raymond, Rick Moen

| **Revision History**                                         |             |      |
| ------------------------------------------------------------ | ----------- | ---- |

This file has been truncated. show original

fuckedup · April 19, 2025, 2:27pm

I had to add qubes.skip_autostart in GRUB.
I pressed e in the GRUB menu, added it to the end of the module2 line, and hit Ctrl+X to boot.
To save it permanently, I edited /etc/default/grub in dom0, added qubes.skip_autostart to GRUB_CMDLINE_LINUX, and ran sudo grub2-mkconfig -o /boot/grub2/grub.cfg.
done!

fuckedup · April 19, 2025, 2:56pm

Hello again,
Following up on my previous issue where my system was stuck during boot, I tried adding qubes.skip_autostart to the kernel parameters as suggested in some troubleshooting guides.
While this allowed the system to boot further, I’m now encountering a problem where my sys-usb qube still fails to start automatically upon system boot. This is despite having qubes.skip_autostart in my boot configuration.
Has anyone else experienced this behavior? Is there a specific reason why sys-usb might be ignoring the qubes.skip_autostart parameter, or is there another method I should be using to prevent it from starting automatically?
Any help or suggestions would be greatly appreciated.
Thank you!

OvalZero · April 19, 2025, 3:11pm

Do you use some USB keyboard? (Or did use when installing?)

fuckedup · April 19, 2025, 3:21pm

yes

fuckedup · April 19, 2025, 3:22pm

I’ve found a temporary workaround. By going into GRUB → Advanced options for Qubes → Xen Hypervisor, version 4.17.5 → Qubes with kernel 6.6.7-1.qubes.fc37.x86_64, the system boots and everything (including sys-usb when I don’t use qubes.skip_autostart) works correctly.
This suggests the issue might be related to the default kernel or Xen version being used. Could anyone shed light on why this specific kernel/Xen combination resolves the problem? This information might help in finding a more permanent solution.

OvalZero · April 19, 2025, 3:34pm

No „preventing“ cron entries?

fuckedup · April 19, 2025, 3:45pm

So, I opened that file using sudo nano /etc/default/grub.
Next, I looked for the line that starts with GRUB_CMDLINE_LINUX. I found it.
After that i to add qubes.skip_autostart systemd.mask=crond.service to the end of that line. I made sure to put a space before it.
Then, I saved the file by pressing Ctrl+O and then Enter in nano.
After saving, I closed nano by pressing Ctrl+X.
Finally, I rebooted my Qubes OS system.
After it restarted, i have new issue

OvalZero · April 19, 2025, 3:48pm

Could you please give some hints on your hardware and installation? Is this fresh? (I don’t believe so, because kernel 6.6.7 seems rather outdated to me.)

fuckedup · April 19, 2025, 3:51pm

Yes, it’s a fresh installation 4.2.4. I downloaded the system today, and I think I just broke it. I downloaded the ISO from the Qubes OS website and used BalenaEtcher to put it on the USB drive
R4.2.4, 64GB RAM, B650M HDV 7900xtx 2tb disk

OvalZero · April 19, 2025, 3:53pm

OK. I’d give it a new start … re-download, check signatures and try to write it with rpi-imager or dd.

fuckedup · April 19, 2025, 3:53pm

While downloading Qubes OS today, I clicked ‘Test media & install Qubes OS’

fuckedup · April 19, 2025, 3:55pm

btw ive been doing this every single day since I got this system, and I always have to download it again.

OvalZero · April 19, 2025, 4:04pm

I understand the frustration. On the other hand, your hardware is somewhat “experimental”. Some other Gigabyte gaming boards have had their fair share of USB hazzle as well.

https://groups.google.com/g/qubes-users/c/FtLwlJauews/m/B2XZWKPIAgAJ

See for further reference: Hardware compatibility list (HCL) | Qubes OS