khan-man
(Khan Man)
January 30, 2026, 5:00am
1
I’m new here, so sorry in advance.
My system keeps booting in emergency mode with this error:
“Timed out waiting for device dev-nvme0n1p2.device - /dev/nvme0n1p2”
I’m running Fedora 43 KDE Plasma.
I don’t know why I keep getting this error, but it seemed to show up without fail after I tried switching to the Trinity Desktop Environment, following the installation instructions exactly, even after I gave up and reenabled SDDM.
Hi.
Assuming you can eventually get this machine to boot, post the output of inxi -Fzxx (use text formatting via the </> button in this dialog box - makes the layout and formatting much easier to read) and the output of lsblk -f, again, as preformatted text.
If you can only get to an emergency screen, a phone picture will suffice of the lsblk output, it’s the more important of the two piece of output.
khan-man
(Khan Man)
January 30, 2026, 6:04pm
3
OK, this is what I got:
System:
Kernel: 6.18.6-200.fc43.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
Desktop: KDE Plasma v: 6.5.5 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
Distro: Fedora Linux 43 (KDE Plasma Desktop Edition)
Machine:
Type: Desktop Mobo: ASRock model: X570 Phantom Gaming 4
serial: <superuser required> Firmware: BIOS vendor: American Megatrends
v: P4.50 date: 10/19/2022
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M510
serial: <filter> charge: 55% (should be ignored) status: discharging
CPU:
Info: 6-core model: AMD Ryzen 5 4500 bits: 64 type: MT MCP arch: Zen 2
rev: 1 cache: L1: 384 KiB L2: 3 MiB L3: 8 MiB
Speed (MHz): avg: 2394 min/max: 413/4211 boost: enabled cores: 1: 2394
2: 2394 3: 2394 4: 2394 5: 2394 6: 2394 7: 2394 8: 2394 9: 2394 10: 2394
11: 2394 12: 2394 bogomips: 86400
Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a
ssse3 svm
Graphics:
Device-1: NVIDIA TU106 [GeForce RTX 2070] vendor: Micro-Star MSI
driver: nvidia v: 580.119.02 arch: Turing pcie: speed: 5 GT/s lanes: 16
ports: active: DP-3 empty: DP-1, DP-2, HDMI-A-1, Unknown-1 bus-ID: 09:00.0
chip-ID: 10de:1f02
Display: wayland server: Xwayland v: 24.1.9 compositor: kwin_wayland
driver: gpu: nv_platform,nvidia,nvidia-nvswitch display-ID: 0
Monitor-1: DP-3 model: PG27F15RS1A res: 1920x1080 hz: 60 dpi: 82
diag: 686mm (27")
API: EGL v: 1.5 platforms: device: 0 drv: nvidia device: 2 drv: swrast
gbm: drv: nvidia surfaceless: drv: nvidia wayland: drv: nvidia x11:
drv: nvidia inactive: device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 580.119.02
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 2070/PCIe/SSE2
display-ID: :0.0
API: Vulkan v: 1.4.328 surfaces: N/A device: 0 type: discrete-gpu
driver: nvidia device-ID: 10de:1f02 device: 1 type: cpu
driver: mesa llvmpipe device-ID: 10005:0000
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: nvidia-settings wl: wayland-info
x11: xdriinfo, xdpyinfo, xprop, xrandr
Audio:
Device-1: NVIDIA TU106 High Definition Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s lanes: 16
bus-ID: 09:00.1 chip-ID: 10de:10f9
Device-2: Advanced Micro Devices [AMD/ATI] Renoir/Cezanne HDMI/DP Audio
driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s lanes: 16
bus-ID: 0b:00.1 chip-ID: 1002:1637
Device-3: Advanced Micro Devices [AMD] Ryzen HD Audio vendor: ASRock
driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s lanes: 16
bus-ID: 0b:00.6 chip-ID: 1022:15e3
Device-4: HP HyperX Cloud III driver: hid-generic,snd-usb-audio,usbhid
type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 bus-ID: 1-3:2 chip-ID: 03f0:089d
API: ALSA v: k6.18.6-200.fc43.x86_64 status: kernel-api
Server-1: PipeWire v: 1.4.10 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin
Network:
Device-1: Qualcomm WCN785x Wi-Fi 7 320MHz 2x2 [FastConnect 7800]
vendor: Foxconn Band Simultaneous Wireless driver: ath12k_pci v: N/A pcie:
speed: 8 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 17cb:1107
IF: wlp4s0 state: up mac: <filter>
Device-2: Intel I211 Gigabit Network vendor: ASRock driver: igb v: kernel
pcie: speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 05:00.0 chip-ID: 8086:1539
IF: enp5s0 state: down mac: <filter>
Drives:
Local Storage: total: 4.1 TiB used: 18.29 GiB (0.4%)
ID-1: /dev/nvme0n1 vendor: Western Digital model: PC SN730
SDBPNTY-512G-1006 size: 476.94 GiB speed: 31.6 Gb/s lanes: 4
serial: <filter> temp: 38.9 C
ID-2: /dev/nvme1n1 vendor: Western Digital model: WD BLACK SN850X HS
4000GB size: 3.64 TiB speed: 63.2 Gb/s lanes: 4 serial: <filter>
temp: 31.9 C
Partition:
ID-1: / size: 474.94 GiB used: 17.66 GiB (3.7%) fs: btrfs
dev: /dev/nvme0n1p3
ID-2: /boot size: 1.9 GiB used: 641.7 MiB (33.0%) fs: ext4
dev: /dev/nvme0n1p2
ID-3: /home size: 474.94 GiB used: 17.66 GiB (3.7%) fs: btrfs
dev: /dev/nvme0n1p3
Swap:
ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 34.8 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 16 GiB available: 15.47 GiB used: 3.66 GiB (23.7%)
Processes: 398 Power: uptime: 10m wakeups: 0 Init: systemd v: 258
default: graphical
Packages: pm: rpm pkgs: N/A note: see --rpm pm: flatpak pkgs: 13
Compilers: gcc: 15.2.1 Shell: Bash v: 5.3.0 running-in: konsole inxi: 3.3.40
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
zram0 swap 1 zram0 ecc442e1-5cb1-4feb-8b8b-d0309123a826 [SWAP]
nvme0n1
├─nvme0n1p1
├─nvme0n1p2 ext4 1.0 4c58a7c3-0e46-4334-89b0-bca48a1aa05e 1.2G 33% /boot
└─nvme0n1p3 btrfs fedora e54764a6-e883-42f5-a6b5-cf5b2a1ae121 456.3G 4% /home
/
nvme1n1
└─nvme1n1p1 ext4 1.0 WD_BLACK b3cdcab8-f7db-4aed-bbb6-b7c6de8ce4e5
OK.
Check for an updated BIOS on the ASRock site - yours is from 2022 which is not terrible but it’s getting on for 3.5 years old now.
Check the smartctl stats for that drive and partition sudo smartctl -a /dev/nvme0n1p2
Boot from a live USB again and run a fsck on that drive - fsck.ext4 -f /dev/nvme0n1p2. This won’t fix any issues, but it will let us know that something is up with it.
Cant hurt to check for updated firmware on the connected devices - fwupdmgr refresh --force && fwupdmgr update
Let us know if any of that turned up anything interesting, or terrible.