Fedora boot stuck on "Job dev-disk-by/x2duuid-XXX [...] .device/start running"

Ask Fedora
, , , , ,
1

When booting it gets stuck on the line visible at the bottom of the picture (I have waited more than 49 seconds before).

I already went through this entire discussion: “Fedora boot stuck on Job dev-disk-by”, but the solution didn’t work for me.

PXL_20260213_142556994
PXL_20260213_1425569941920×1442 403 KB

This happens only in the newer versions

6.18.7-200.fc43.x86_64

&

6.18.9-200.fc43.x86_64

, but I was luckily still able to boot with my first installed version

6.17.1-300.fc43.x86_64

I don’t know what caused this, but I did modify /etc/default/grub using this tutorial:
“Nvidia Cuda is not shown in Blender - #6 by fedora30kvm”
It did not work, because - as I found out after - my graphic card isn’t supported for CUDA anymore (Nvidia Quadro M2000M), but I think this could be relevant to the problem. My grub reads:

GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=“$(sed ‘s, release .*$,g’ /etc/system-release)”
GRUB_DEFAULT=saved
GRUB_DISABLE_SUBMENU=true
GRUB_TERMINAL_OUTPUT=“console”
GRUB_CMDLINE_LINUX="rd.driver.blacklist=nouveau modprobe.blacklist=nouveau resume=UUID=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXX rd.driver.blacklist=nouveau modprobe.blacklist=nouveau "
GRUB_DISABLE_RECOVERY=“true”
GRUB_ENABLE_BLSCFG=true

My /etc/fstab, excluding the comments, reads:

UUID=ebdb1d02-f219-4e09-bb7a-91a01dddda83 / btrfs subvol=root,compress=zstd:1 0 0
UUID=c4e5aef9-0722-42e5-8941-12b7c3fbc007 /boot ext4 defaults 1 2
UUID=0BA5-5C26 /boot/efi vfat umask=0077,shortname=winnt 0 2
UUID=ebdb1d02-f219-4e09-bb7a-91a01dddda83 /home btrfs subvol=home,compress=zstd:1 0 0

I have no idea anymore. Please tell me, if relevant information to the problem is missing

2

I’d probably take that resume= section out, as I doubt you have a device with a UUID of all X’s.

The X’s in the instructions were meant to be replaced with your UUID pertient to your system. Not literally X’s.

This is why you get the delay - it’s trying to mount a device with a UUID of XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXX … which doesn’t exist and will never succeed.

3

I am indeed a fool…
Thank you, I’ll try it out!
If it doesn’t work, how do I find out which UUID to use? (I’m quite new to Linux and have no idea)
If I do sudo blkid in terminal I get 4 different ones (I can copy them if that’s necessary)

4

The resume part of that is ONLY necessary if you are actually using hibernation.
If you are then that would be the UUID of the physical swap partition used for hibernation.

If you are not using hibernation then leave it out permanently.

5

Thank you very much, it worked!

6

You also have this rd.driver.blacklist=nouveau modprobe.blacklist=nouveau in those options, twice, and it is best only entered once. Finally that is a very old entry and with newer versions of the nvidia drivers when installed from rpmfusion that part becomes rd.driver.blacklist=nouveau,nova-core modprobe.blacklist=nouveau,nova-core