Sometimes, upon reboot, I see this timeout error. I couldn't figure out what's causing it: other than systemd printing the error and putting me into emergency mode everything looks fine. In particular, if I quit the emergency mode with Ctrl+d, boot continues and the partition in question gets mounted properly.

Content of /etc/fstab:

#
# /etc/fstab: static file system information
#
# <file system> <dir>   <type>  <options>       <dump>  <pass>
UUID=443bd794-4b17-4bf2-8801-b0d5cf1c3432 /             btrfs  rw,noatime,autodefrag,compress=zstd      0 0

UUID=664cfee5-16d7-4e43-933a-ca2e1e25d72f /boot     ext4   defaults,noatime         0 2
UUID=024D-8283 /boot/efi     vfat   defaults         0 1

# a dir we're using for development purposes
tmpfs /mnt/block_dev         tmpfs  rw,nosuid,nodev,noatime,size=500M                0 0

# UUID=dbb01c54-a041-4d53-8a6e-847d0e2c4570 none        swap   defaults         0 0

lsblk -f output after quitting "emergency mode", and getting booted:

$ lsblk -f
NAME   FSTYPE LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINT
sda
├─sda1 vfat   ESP   024D-8283                               572M     4% /boot/efi
├─sda2 ext4         664cfee5-16d7-4e43-933a-ca2e1e25d72f    314M    20% /boot
├─sda3 swap         817bb5c9-e259-4139-b3e4-c2ae5c9232ed                [SWAP]
└─sda4 btrfs        443bd794-4b17-4bf2-8801-b0d5cf1c3432  618.3G    33% /
sr0

systemd version the issue has been seen with

243.51 (and older, possibly everywhere)

Used distribution

Archlinux

Expected behaviour you didn't see

No Timed out waiting for device error

Unexpected behaviour you saw

"Timed out" error appears, and systemd stops booting and quits to emergency mode. Relevant lines from ournalctl:

окт 15 09:37:08 constantine-N61Ja systemd[1]: dev-disk-by\x2duuid-024D\x2d8283.device: Job dev-disk-by\x2duuid-024D\x2d8283.device/start timed out.
окт 15 09:37:08 constantine-N61Ja systemd[1]: Timed out waiting for device /dev/disk/by-uuid/024D-8283.
окт 15 09:37:08 constantine-N61Ja systemd[1]: Dependency failed for File System Check on /dev/disk/by-uuid/024D-8283.
окт 15 09:37:08 constantine-N61Ja systemd[1]: Dependency failed for /boot/efi.
окт 15 09:37:08 constantine-N61Ja systemd[1]: Dependency failed for Local File Systems.
окт 15 09:37:08 constantine-N61Ja systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'.
окт 15 09:37:08 constantine-N61Ja systemd[1]: local-fs.target: Triggering OnFailure= dependencies.
окт 15 09:37:08 constantine-N61Ja systemd[1]: boot-efi.mount: Job boot-efi.mount/start failed with result 'dependency'.
окт 15 09:37:08 constantine-N61Ja systemd[1]: systemd-fsck@dev-disk-by\x2duuid-024D\x2d8283.service: Job systemd-fsck@dev-disk-by\x2duuid-024D\x2d8283.service/start failed with result 'dependency'.
окт 15 09:37:08 constantine-N61Ja systemd[1]: dev-disk-by\x2duuid-024D\x2d8283.device: Job dev-disk-by\x2duuid-024D\x2d8283.device/start failed with result 'timeout'.
окт 15 09:37:08 constantine-N61Ja systemd[1]: dev-disk-by\x2duuid-664cfee5\x2d16d7\x2d4e43\x2d933a\x2dca2e1e25d72f.device: Job dev-disk-by\x2duuid-664cfee5\x2d16d7\x2d4e43\x2d933a\x2dca2e1e25d72f.device/start timed out.

Steps to reproduce the problem

1. Reboot the laptop