Arch Linux

derCalvin

Member

Registered: 2026-03-14

Posts: 6

[SOLVED] Timed out waiting for device after upgrade to 6.19.6

Hello everyone. I am new to arch and also not very experienced with linux so please excuse if I am not using the correct terms here.

After upgrading the kernel to 6.19.6 my system isn't booting anymore and I get hit with the error timed out waiting for device /dev/disk/by-uuid/08bfb3e4-1f66-4ee3-9164-d3994c33b21b

I compared lsblk -f to my /etc/fstab and this seems to be correct.

nvme1n1                                                                                 
├─nvme1n1p1 vfat   FAT32            F640-D44B                             677.9M    34% /boot
├─nvme1n1p2 swap   1                d566eeed-4852-4cfc-bdc3-5dabb5f105cb                [SWAP]
└─nvme1n1p3 ext4   1.0              08bfb3e4-1f66-4ee3-9164-d3994c33b21b    1.3T    21% /

# <file system> <dir> <type> <options> <dump> <pass>
# /dev/nvme1n1p3
UUID=08bfb3e4-1f66-4ee3-9164-d3994c33b21b       /               ext4            rw,relatime     0 1

# /dev/nvme1n1p1
UUID=F640-D44B          /boot           vfat            rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro   0 2

# /dev/nvme1n1p2
UUID=d566eeed-4852-4cfc-bdc3-5dabb5f105cb       none            swap            defaults        0 0

I also tried running sudo mkinitcpio -P + I reinstalled grub which didn't fix the problem.

I ended up downgrading the kernel again to 6.18.13 and everything works fine. Also linux-lts is working perfectly. I was reading through different forums but could not find anything similar for the latest kernel. So I suspect this is an issue on my side.

Thanks!

Last edited by derCalvin (2026-03-14 17:06:48)

frostschutz

Member

Registered: 2013-11-15

Posts: 1,637

Re: [SOLVED] Timed out waiting for device after upgrade to 6.19.6

For a regular partition, this is quite odd, unless you ran mkinitcpio elsewhere and nvme modules are somehow missing from initcpio (check with lsinitcpio what's in there or try booting the fallback initrd).

Or you have a bootloader misconfiguration and it's loading the wrong initrd, with not a single module working due to wrong kernel version.

Does it drop you to a shell where you could check lsmod?

derCalvin

Member

Registered: 2026-03-14

Posts: 6

Re: [SOLVED] Timed out waiting for device after upgrade to 6.19.6

Thanks for your reply!

[calvin@calvin-arch ~]$ lsinitcpio /boot/initramfs-linux.img | grep nvme
usr/lib/modules/6.18.13-arch1-1/kernel/drivers/nvme/
usr/lib/modules/6.18.13-arch1-1/kernel/drivers/nvme/common/
usr/lib/modules/6.18.13-arch1-1/kernel/drivers/nvme/common/nvme-auth.ko.zst
usr/lib/modules/6.18.13-arch1-1/kernel/drivers/nvme/common/nvme-keyring.ko.zst
usr/lib/modules/6.18.13-arch1-1/kernel/drivers/nvme/host/
usr/lib/modules/6.18.13-arch1-1/kernel/drivers/nvme/host/nvme-core.ko.zst
usr/lib/modules/6.18.13-arch1-1/kernel/drivers/nvme/host/nvme.ko.zst

but this shows only the downgraded kernel now. I had tried booting into fallback but I get the same error with the latest kernel.

I need to check later if I get a shell or not

EDIT: trying again to update. After pacman -Syu this is the output

[calvin@calvin-arch ~]$ lsinitcpio /boot/initramfs-linux.img | grep nvme
usr/lib/modules/6.19.6-arch1-1/kernel/drivers/nvme/
usr/lib/modules/6.19.6-arch1-1/kernel/drivers/nvme/common/
usr/lib/modules/6.19.6-arch1-1/kernel/drivers/nvme/common/nvme-auth.ko.zst
usr/lib/modules/6.19.6-arch1-1/kernel/drivers/nvme/common/nvme-keyring.ko.zst
usr/lib/modules/6.19.6-arch1-1/kernel/drivers/nvme/host/
usr/lib/modules/6.19.6-arch1-1/kernel/drivers/nvme/host/nvme-core.ko.zst
usr/lib/modules/6.19.6-arch1-1/kernel/drivers/nvme/host/nvme.ko.zst

going to check lsblk and fstab again and then reboot.

Last edited by derCalvin (2026-03-14 13:09:40)

derCalvin

Member

Registered: 2026-03-14

Posts: 6

Re: [SOLVED] Timed out waiting for device after upgrade to 6.19.6

[ 0.116801] RDSEED32 is broken. Disabling the corresponding CPUID bit.
[ TIME ] Timed out waiting for device /dev/disk/by-uuid/08bfb3e4-1f66-4ee3-9164-d3994c33b21b. 
[DEPEND] Dependency failed for /sysroot.
[DEPEND] Dependency failed for Initrd Root File System.
[DEPEND] Dependency failed for Mountpoints Configured in the Real Root.
[DEPEND] Dependency failed for Initrd Root Device.
[DEPEND] Dependency failed for File System Check on /dev/disk/by-uuid/08bfb3e4-1f66-4ee3-9164-d3994c33b21b
You are in emergency mode. After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, or "exit"
to continue bootup.
Cannot open access to console, the root account is locked.
See sulogin(8) man page for more details.
Press Enter to continue.

this is the exact error message. Enter doesnt work. it just hangs. I also tried to check journalctl -b for issues but it looks like it fails to early to log anything. Maybe I am using it wrong tho

Last edited by derCalvin (2026-03-14 13:46:13)

frostschutz

Member

Registered: 2013-11-15

Posts: 1,637

Re: [SOLVED] Timed out waiting for device after upgrade to 6.19.6

https://wiki.archlinux.org/title/Mkinit … _is_locked (also requires `base` hook)

then check lsmod, /proc/partitions, ...

you could also try your luck with non-systemd initcpio

derCalvin

Member

Registered: 2026-03-14

Posts: 6

Re: [SOLVED] Timed out waiting for device after upgrade to 6.19.6

Followed the steps on your link. Now I don't get the root account is locked error, but it still hangs on a blinking cursor and I cannot input anything. Tried with 2 different keyboards.

[calvin@calvin-arch ~]$ cat /etc/mkinitcpio.conf
# vim:set ft=sh:
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES=(usbhid xhci_hcd)
MODULES=(nvme)

# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image.  This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=()

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way.  This is useful for config files.
FILES=()

# HOOKS
# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
##   This setup specifies all modules in the MODULES setting above.
##   No RAID, lvm2, or encrypted root is needed.
#    HOOKS=(base)
#
##   This setup will autodetect all modules for your system and should
##   work as a sane default
#    HOOKS=(base udev autodetect microcode modconf block filesystems fsck)
#
##   This setup will generate a 'full' image which supports most systems.
##   No autodetection is done.
#    HOOKS=(base udev microcode modconf block filesystems fsck)
#
##   This setup assembles a mdadm array with an encrypted root file system.
##   Note: See 'mkinitcpio -H mdadm_udev' for more information on RAID devices.
#    HOOKS=(base udev microcode modconf keyboard keymap consolefont block mdadm_udev encrypt filesystems fsck)
#
##   This setup loads an lvm2 volume group.
#    HOOKS=(base udev microcode modconf block lvm2 filesystems fsck)
#
##   This will create a systemd based initramfs which loads an encrypted root filesystem.
#    HOOKS=(base systemd autodetect microcode modconf kms keyboard sd-vconsole sd-encrypt block filesystems fsck)
#
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    usr and fsck hooks.
HOOKS=(base systemd autodetect microcode modconf kms keyboard keymap sd-vconsole block filesystems fsck)

# COMPRESSION
# Use this to compress the initramfs image. By default, zstd compression
# is used for Linux ≥ 5.9 and gzip compression is used for Linux < 5.9.
# Use 'cat' to create an uncompressed image.
#COMPRESSION="zstd"
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"

# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()

# MODULES_DECOMPRESS
# Decompress loadable kernel modules and their firmware during initramfs
# creation. Switch (yes/no).
# Enable to allow further decreasing image size when using high compression
# (e.g. xz -9e or zstd --long --ultra -22) at the expense of increased RAM usage
# at early boot.
# Note that any compressed files will be placed in the uncompressed early CPIO
# to avoid double compression.
#MODULES_DECOMPRESS="no"

maybe this helps? I've tried with and without modules(nvme) - no change

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 74,314

Re: [SOLVED] Timed out waiting for device after upgrade to 6.19.6

Is this an AMD system?
https://bbs.archlinux.org/viewtopic.php … 8#p2290148

To enable the emergency shell, temporarily add SYSTEMD_SULOGIN_FORCE=1 to the kernel parameters.

but you're still dropped into the emergency shell anyway?

you could also try your luck with non-systemd initcpio

https://wiki.archlinux.org/title/Mkinitcpio#Hook_list

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

derCalvin

Member

Registered: 2026-03-14

Posts: 6

Re: [SOLVED] Timed out waiting for device after upgrade to 6.19.6

Is this an AMD system?

yes, it's actually the exact same model. Maybe this is a general issue then. Thanks! I did not find that when researching.

but you're still dropped into the emergency shell anyway?

yes, or at least it looks like one. But it doesn't accept any input. Says to hit ctrl + d to continue or enter

I still need to try the non-systemd approach but I need some more time to read into it.

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 74,314

Re: [SOLVED] Timed out waiting for device after upgrade to 6.19.6

I still need to try the non-systemd approach but I need some more time to read into it.

Postpone that and see whether 6.19.8 or disabling the iommu allows you to boot.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

derCalvin

Member

Registered: 2026-03-14

Posts: 6

Re: [SOLVED] Timed out waiting for device after upgrade to 6.19.6

Hooly

Is this an AMD system?
https://bbs.archlinux.org/viewtopic.php … 8#p2290148

that was really the issue here. Still no idea why this would be causing nvme issues but adding

GRUB_CMDLINE_LINUX="amd_iommu=on iommu=pt"

to the grub config fixed it!

Thanks a lot for all the help!

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 74,314

Re: [SOLVED] Timed out waiting for device after upgrade to 6.19.6

It's a kernel bug, it should™ be fixed w/ a patch cherry-picked for 6.19.8 (which is currently in the testing repos, in doubt just wait until it moves into core) and without IOMMU parameters.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc