Fedora 40, Kernel 6.9.10/11 -- System does not boot correctly with error: "A start job is running for dev-disk-by\x2duuid-xxxxxxxx\x2dxxxx...\x2dxxxx.device"

Ask Fedora
, , , ,
1

Hi all,

I am running Fedora 40 workstation on an Intel NUC (8i7HVK, 32 GB RAM, 2x 512 GB Samsung 970 Pro NVMe SSDs) and with the newer Kernels 6.9.10 and 6.9.11 my system gets stuck at the boot up. Inspecting the boot messages shows it gets stuck with this message:

“A start job is running for dev-disk-by\x2duuid-xxxxxxxx\x2dxxxx…\x2dxxxx.device”

It is happening for two disks: root and swap. However, the uuids for both have not changed and are all the same as in fstab, the kernel cmdline and lsblk (see output below). Further, I do not get this problem with the older Kernels 6.9.9 and lower.

Any help on how to get around this problem would be really appreciated.

Thanks,
dfmidas

fstab:

#
# /etc/fstab
# Created by anaconda on Fri Apr  7 11:52:07 2023
#
# Accessible filesystems, by reference, are maintained under '/dev/disk/'.
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info.
#
# After editing this file, run 'systemctl daemon-reload' to update systemd
# units generated from this file.
#
UUID=6d5c198e-d55f-4ea1-a2d7-64a43710bb29 /                       xfs     defaults        0 0
UUID=4bab5585-d810-4e54-bb08-5e9e202e992e /boot                   ext2    defaults,nodev,noexec,nosuid,relatime        1 2
UUID=3E23-1E41          /boot/efi               vfat    umask=0077,shortname=winnt 0 2
UUID=1c41bd96-3da9-4bbd-bc09-94d15ac2a079 /home                   xfs     defaults,nodev,nosuid,relatime        0 0
UUID=e9fe8bed-817f-4686-9af4-a1597e43d033 /tmp                    xfs     defaults,nodev,nosuid,relatime        0 0
UUID=9c7aaa7d-0798-4d0d-8925-fbf50d850608 /var                    xfs     defaults,nosuid,relatime        0 0
UUID=ab8dc118-5ca4-45e8-a055-4e2f06d9ba74 none                    swap    defaults        0 0
tmpfs	/dev/shm	tmpfs	defaults,nodev,noexec,nosuid	0 0

Kernel cmdline:

BOOT_IMAGE=(hd1,gpt2)/vmlinuz-6.9.9-200.fc40.x86_64 root=UUID=6d5c198e-d55f-4ea1-a2d7-64a43710bb29 ro resume=UUID=ab8dc118-5ca4-45e8-a055-4e2f06d9ba74 randomize_kstack_offset=1 slab_nomerge page_alloc.shuffle=1 pti=on iommu.passthrough=0 iommu.strict=1 vsyscall=none module.sig_enforce=1 lockdown=confidentiality audit=on ipv6.disable=1 bluetooth.blacklist=yes systemd.zram=0 hibernate=no intel_iommu=on efi=disable_early_pci_dma spectre_v2=on tsx=off tsx_async_abort=full,nosmt mds=full,nosmt mmio_stale_data=full,nosmt l1tf=full,force nosmt=force kvm.nx_huge_pages=force rhgb quiet

lsblk -f output:

NAME        FSTYPE FSVER LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
nvme1n1                                                                            
└─nvme1n1p1 xfs          HOME  1c41bd96-3da9-4bbd-bc09-94d15ac2a079  408.2G    14% /home
nvme0n1                                                                            
├─nvme0n1p1 vfat   FAT32 EFI   3E23-1E41                             503.6M     1% /boot/efi
├─nvme0n1p2 ext2   1.0   BOOT  4bab5585-d810-4e54-bb08-5e9e202e992e  552.2M    40% /boot
├─nvme0n1p3 xfs          ROOT  6d5c198e-d55f-4ea1-a2d7-64a43710bb29  384.4G     4% /
├─nvme0n1p4 xfs          TMP   e9fe8bed-817f-4686-9af4-a1597e43d033    9.8G     1% /tmp
├─nvme0n1p5 xfs          VAR   9c7aaa7d-0798-4d0d-8925-fbf50d850608   49.9G    17% /var
└─nvme0n1p6 swap   1     SWAP  ab8dc118-5ca4-45e8-a055-4e2f06d9ba74                [SWAP]
2

Hello @dfmidas ,
For the swap mount on the command line for kernel args try to set a timeout for the resume args, it is defaulted to infinite (so boot up will wait indefinitely for the device to come up) after an update to F40, such as noted at [SOLVED] Boot hang - Job dev-disk-by\x2uuid... [no limit].

1 Like
3

Hi @jakfrost ,

Thanks for taking the time to reply to my post. I tried your suggestion and added:

systemd.gpt_auto=0

To my kernel cmd args list and it did not help in my case. Boot still hangs at the Fedora splash screen with the spinning circle showing. Typing ESC shows the same message as before.

Is there anything else I could check or try? I did not have this problem when I first upgraded to F40. It just started with Kernel 6.9.10. Only Kernel 6.9.9 boots successfully. What has changed between Kernel 6.9.9 and 6.9.10?

Many thanks,
dfmidas

4

If you don’t plan on using hibernate, you probably should remove the resume= entry in the kernel command line. With secure boot enabled it might not work anyway. man kernel_lockdown has more details.

Whether it fixes your problem, I don’t know.