Slow Boot time(1+ minute initrd, ~20 seconds firmware) on new build

I’m having slow boot times on a new PC build. I’m running Garuda Dragonized on a custom built desktop. Generally performance has been solid except it’s slow boot time(from GRUB to logon prompt). Also has slow restore time from suspend/hibernate. It take 1+ minutes initrd and 20+ seconds for firmware.

I’ve never had any other OS on this build, so I don’t have a baseline, and it’s possible something is wrong with the build, but the system is otherwise stable and benchmarks seems fine.

I’m a Linux user on and off again for ~15 years. Mostly switching back to windows a bit for gaming. Primarily my experience has been with Ubuntu and Arch based system, but never Garuda before this build.

I’ve tried a number of different BIOS settings changes with no impact. I’ve updated the BIOS on my motherboard. I did solve slow post time on motherboard by enabling Memory Context Restore. Expo on/off doesn’t seem to impact slow OS boot.
Per: https://www.reddit.com/r/MSI_Gaming/comments/1ewucfj/msi_mag_x670e_tomahawk_wifi_gaming_motherboard/

Per my reading of systemd-analyze blame it looks like my nvme is slow to start. I checked my motherboard manual and it doesn’t seem like it’s sharing any bandwidth with my GPU in a different PCIe slot.

I thought maybe it was missing UUID from /etc/fstab per this(https://forums.linuxmint.com/viewtopic.php?t=320860), but it doesn’t appear to be.

I’d appreciate any help with troubleshooting this issue. I’ve included everything that seemed relevant, but let me know if any additional system information would be useful.

garuda-inxi:

╰─λ garuda-inxi
System:
Kernel: 6.12.4-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=c076eea8-e53f-492e-968c-556fdf1dadae rw rootflags=subvol=@
quiet resume=UUID=803297b5-c04e-45f1-b0c0-fab8ba283a90 loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.2.4 tk: Qt v: N/A info: frameworks v: 6.9.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop Mobo: Micro-Star model: MAG X670E TOMAHAWK WIFI (MS-7E12)
v: 1.0 serial: <superuser required> uuid: <superuser required> UEFI: American
Megatrends LLC. v: 1.F0 date: 10/08/2024
CPU:
Info: model: AMD Ryzen 9 7950X3D bits: 64 type: MT MCP arch: Zen 4 gen: 4
level: v4 note: check built: 2022+ process: TSMC n5 (5nm) family: 0x19 (25)
model-id: 0x61 (97) stepping: 2 microcode: 0xA601209
Topology: cpus: 1x dies: 2 clusters: 2x1 cores: 16 threads: 32 tpc: 2
smt: enabled cache: L1: 1024 KiB desc: d-16x32 KiB; i-16x32 KiB L2: 16 MiB
desc: 16x1024 KiB L3: 128 MiB desc: 1x32 MiB, 1x96 MiB
Speed (MHz): avg: 2982 min/max: 545/5759 boost: enabled scaling:
driver: amd-pstate-epp governor: performance cores: 1: 2982 2: 2982 3: 2982
4: 2982 5: 2982 6: 2982 7: 2982 8: 2982 9: 2982 10: 2982 11: 2982 12: 2982
13: 2982 14: 2982 15: 2982 16: 2982 17: 2982 18: 2982 19: 2982 20: 2982
21: 2982 22: 2982 23: 2982 24: 2982 25: 2982 26: 2982 27: 2982 28: 2982
29: 2982 30: 2982 31: 2982 32: 2982 bogomips: 268799
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA AD102 [GeForce RTX 4070 Ti SUPER] vendor: Micro-Star MSI
driver: nvidia v: 565.77 alternate: nouveau,nvidia_drm non-free: 550.xx+
status: current (as of 2024-09) arch: Lovelace code: AD1xx
process: TSMC n4 (5nm) built: 2022+ pcie: gen: 2 speed: 5 GT/s lanes: 16
link-max: gen: 4 speed: 16 GT/s ports: active: none off: DP-1,DP-2
empty: HDMI-A-1,HDMI-A-2 bus-ID: 01:00.0 chip-ID: 10de:2689 class-ID: 0300
Display: wayland server: X.org v: 1.21.1.14 with: Xwayland v: 24.1.4
compositor: kwin_wayland driver: X: loaded: nvidia
unloaded: modesetting,nouveau alternate: fbdev,nv,vesa gpu: nvidia
d-rect: 6000x1440 display-ID: 0
Monitor-1: DP-1 pos: right res: 3440x1440 size: N/A modes: N/A
Monitor-2: DP-2 pos: primary,left res: 2560x1440 size: N/A modes: N/A
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia gbm:
drv: nvidia surfaceless: drv: nvidia wayland: drv: nvidia x11: drv: nvidia
API: OpenGL v: 4.6.0 vendor: nvidia v: 565.77 glx-v: 1.4
direct-render: yes renderer: NVIDIA GeForce RTX 4070 Ti SUPER/PCIe/SSE2
memory: 15.62 GiB display-ID: :1.0
API: Vulkan v: 1.4.303 layers: 15 device: 0 type: discrete-gpu name: NVIDIA
GeForce RTX 4070 Ti SUPER driver: N/A device-ID: 10de:2689
surfaces: xcb,xlib,wayland device: 1 type: cpu name: llvmpipe (LLVM
18.1.8 256 bits) driver: N/A device-ID: 10005:0000
surfaces: xcb,xlib,wayland
Audio:
Device-1: NVIDIA AD102 High Definition Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 01:00.1 chip-ID: 10de:22ba class-ID: 0403
Device-2: Advanced Micro Devices [AMD] Family 17h/19h/1ah HD Audio
vendor: Micro-Star MSI driver: snd_hda_intel v: kernel pcie: gen: 4
speed: 16 GT/s lanes: 16 bus-ID: 15:00.6 chip-ID: 1022:15e3 class-ID: 0403
Device-3: Razer USA BlackShark V2 Pro 2.4
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
lanes: 1 mode: 1.1 bus-ID: 3-4:2 chip-ID: 1532:0555 class-ID: 0300
serial: <filter>
API: ALSA v: k6.12.4-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 1.2.7 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Realtek RTL8125 2.5GbE vendor: Micro-Star MSI driver: r8169
v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 port: e000 bus-ID: 06:00.0
chip-ID: 10ec:8125 class-ID: 0200
IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Info: services: NetworkManager,systemd-timesyncd
Drives:
Local Storage: total: 931.51 GiB used: 256.76 GiB (27.6%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 990 EVO 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 126 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: 0B2QKXJ7 temp: 32.9 C
scheme: GPT
Partition:
ID-1: / raw-size: 897.72 GiB size: 897.72 GiB (100.00%)
used: 256.75 GiB (28.6%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 584 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 897.72 GiB size: 897.72 GiB (100.00%)
used: 256.75 GiB (28.6%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 897.72 GiB size: 897.72 GiB (100.00%)
used: 256.75 GiB (28.6%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 897.72 GiB size: 897.72 GiB (100.00%)
used: 256.75 GiB (28.6%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 30.94 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 max-streams: 32
dev: /dev/zram0
ID-2: swap-2 type: partition size: 33.5 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/nvme0n1p3 maj-min: 259:3
Sensors:
System Temperatures: cpu: 37.2 C mobo: 26.2 C
Fan Speeds (rpm): N/A
Info:
Memory: total: 32 GiB note: est. available: 30.94 GiB used: 4.34 GiB (14.0%)
Processes: 494 Power: uptime: 13m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.32 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1892 libs: 570 tools: octopi,paru Compilers:
clang: 18.1.8 gcc: 14.2.1 Shell: garuda-inxi default: fish v: 3.7.1
running-in: konsole inxi: 3.3.36
Garuda (2.6.26-1):
System install date:     2024-11-29
Last full system update: 2024-12-16
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       No/Undetected
Failed units:

systemd-analyze:

╰─λ systemd-analyze
Startup finished in 24.181s (firmware) + 6.024s (loader) + 1.028s (kernel) + 1min 6.272s (initrd) + 5.441s (userspace) = 1min 42.948s
graphical.target reached after 3.215s in userspace.

systemd-analyze critical-chain:

╰─λ systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @3.215s
└─multi-user.target @3.214s
└─libvirtd.service @3.172s +42ms
└─network.target @3.171s
└─NetworkManager.service @2.892s +278ms
└─basic.target @2.890s
└─dbus-broker.service @2.856s +31ms
└─dbus.socket @2.853s
└─sysinit.target @2.851s
└─systemd-update-done.service @2.838s +13ms
└─ldconfig.service @1.427s +1.410s
└─systemd-tmpfiles-setup.service @1.366s +59ms
└─systemd-journal-flush.service @1.284s +81ms
└─var-log.mount @1.277s +5ms
└─dev-disk-by\x2duuid-c076eea8\x2de53f\x2d492e\x2d968c\x2d556fdf1dadae.device

systemd-analyze blame:

╰─λ systemd-analyze blame
1min 6.388s sys-devices-LNXSYSTM:00-LNXSYBUS:00-MSFT0101:00-tpmrm-tpmrm0.device
1min 6.388s dev-tpmrm0.device
1min 6.388s dev-ttyS1.device
1min 6.388s sys-devices-platform-serial8250-serial8250:0-serial8250:0.1-tty-ttyS1.device
1min 6.387s sys-devices-platform-serial8250-serial8250:0-serial8250:0.0-tty-ttyS0.device
1min 6.387s dev-ttyS0.device
1min 6.387s dev-ttyS2.device
1min 6.387s sys-devices-platform-serial8250-serial8250:0-serial8250:0.2-tty-ttyS2.device
1min 6.386s sys-devices-platform-serial8250-serial8250:0-serial8250:0.3-tty-ttyS3.device
1min 6.386s dev-ttyS3.device
1min 6.376s sys-module-fuse.device
1min 6.375s sys-module-configfs.device
1min 6.352s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart2.device
1min 6.351s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_EVO_1TB_S7M3NL0X938323M\x2dpart2.device
1min 6.351s dev-disk-by\x2dpartlabel-root.device
1min 6.351s sys-devices-pci0000:00-0000:00:01.2-0000:02:00.0-nvme-nvme0-nvme0n1-nvme0n1p2.device
1min 6.351s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-2.device
1min 6.351s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartlabel-root.device
1min 6.351s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_EVO_1TB_S7M3NL0X938323M_1\x2dpart2.device
1min 6.351s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-c076eea8\x2de53f\x2d492e\x2d968c\x2d556fdf1dadae.device
1min 6.351s dev-disk-by\x2duuid-c076eea8\x2de53f\x2d492e\x2d968c\x2d556fdf1dadae.device
1min 6.351s dev-disk-by\x2dpartuuid-867afa77\x2d4953\x2d44ed\x2db130\x2d63997dfc36ca.device
1min 6.351s dev-disk-by\x2ddiskseq-1\x2dpart2.device
1min 6.351s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-867afa77\x2d4953\x2d44ed\x2db130\x2d63997dfc36ca.device
1min 6.351s dev-disk-by\x2did-nvme\x2deui.0025382941a0bd4b\x2dpart2.device
1min 6.351s dev-nvme0n1p2.device
1min 6.350s dev-disk-by\x2duuid-F26E\x2d0F24.device
1min 6.350s dev-disk-by\x2ddiskseq-1\x2dpart1.device
1min 6.350s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart1.device
1min 6.350s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-F26E\x2d0F24.device
1min 6.350s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-1845b5c8\x2dfbca\x2d4e4b\x2db292\x2d820fdd3d1bc5.device
1min 6.350s dev-disk-by\x2dpartuuid-1845b5c8\x2dfbca\x2d4e4b\x2db292\x2d820fdd3d1bc5.device
1min 6.350s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-1.device
1min 6.350s dev-disk-by\x2did-nvme\x2deui.0025382941a0bd4b\x2dpart1.device
1min 6.350s sys-devices-pci0000:00-0000:00:01.2-0000:02:00.0-nvme-nvme0-nvme0n1-nvme0n1p1.device
1min 6.350s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_EVO_1TB_S7M3NL0X938323M\x2dpart1.device
1min 6.350s dev-nvme0n1p1.device
1min 6.350s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_EVO_1TB_S7M3NL0X938323M_1\x2dpart1.device
1min 6.349s dev-nvme0n1p3.device
1min 6.349s dev-disk-by\x2dlabel-swap.device
1min 6.349s dev-disk-by\x2duuid-803297b5\x2dc04e\x2d45f1\x2db0c0\x2dfab8ba283a90.device
1min 6.349s dev-disk-by\x2dpartuuid-b522beb5\x2d0f5b\x2d4921\x2d9889\x2d7bceb407e308.device
1min 6.349s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart3.device
1min 6.349s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-3.device
1min 6.349s dev-disk-by\x2did-nvme\x2deui.0025382941a0bd4b\x2dpart3.device
1min 6.349s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-b522beb5\x2d0f5b\x2d4921\x2d9889\x2d7bceb407e308.device
1min 6.349s dev-disk-by\x2ddiskseq-1\x2dpart3.device
1min 6.349s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_EVO_1TB_S7M3NL0X938323M_1\x2dpart3.device
1min 6.349s sys-devices-pci0000:00-0000:00:01.2-0000:02:00.0-nvme-nvme0-nvme0n1-nvme0n1p3.device
1min 6.349s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2dlabel-swap.device
1min 6.349s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-803297b5\x2dc04e\x2d45f1\x2db0c0\x2dfab8ba283a90.device
1min 6.349s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_EVO_1TB_S7M3NL0X938323M\x2dpart3.device
1min 6.343s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_EVO_1TB_S7M3NL0X938323M.device
1min 6.343s dev-nvme0n1.device
1min 6.343s dev-disk-by\x2ddiskseq-1.device
1min 6.343s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_EVO_1TB_S7M3NL0X938323M_1.device
1min 6.343s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1.device
1min 6.343s sys-devices-pci0000:00-0000:00:01.2-0000:02:00.0-nvme-nvme0-nvme0n1.device
1min 6.343s dev-disk-by\x2did-nvme\x2deui.0025382941a0bd4b.device
2.518s linux-modules-cleanup.service
1.410s ldconfig.service
982ms systemd-binfmt.service
871ms systemd-oomd.service
851ms systemd-timesyncd.service
354ms initrd-switch-root.service
278ms NetworkManager.service
149ms dev-zram0.swap
115ms systemd-udev-trigger.service
111ms dracut-pre-udev.service
87ms systemd-tmpfiles-setup-dev-early.service
82ms user@1000.service
81ms systemd-journal-flush.service
62ms systemd-remount-fs.service
62ms upower.service
59ms systemd-tmpfiles-setup.service
56ms lvm2-monitor.service
55ms systemd-userdbd.service
45ms systemd-tmpfiles-clean.service
44ms systemd-journald.service
42ms power-profiles-daemon.service
42ms libvirtd.service
39ms avahi-daemon.service
37ms systemd-random-seed.service
37ms polkit.service
37ms systemd-zram-setup@zram0.service
37ms boot-efi.mount
35ms systemd-udevd.service
35ms dracut-shutdown.service
34ms garuda-pacman-lock.service
34ms dracut-pre-pivot.service
32ms systemd-journal-catalog-update.service
31ms dbus-broker.service
31ms dev-hugepages.mount
30ms dev-mqueue.mount
30ms virtlogd.service
30ms sys-kernel-debug.mount
30ms systemd-logind.service
30ms sys-kernel-tracing.mount
29ms kmod-static-nodes.service
29ms systemd-hibernate-resume.service
28ms initrd-parse-etc.service
27ms udisks2.service
27ms user-runtime-dir@1000.service
27ms dracut-cmdline.service
27ms ModemManager.service
26ms systemd-hostnamed.service
26ms home.mount
25ms root.mount
25ms srv.mount
24ms systemd-vconsole-setup.service
24ms systemd-sysusers.service
24ms var-cache.mount
22ms systemd-user-sessions.service
21ms tmp.mount
19ms proc-sys-fs-binfmt_misc.mount
15ms systemd-fsck@dev-disk-by\x2duuid-F26E\x2d0F24.service
15ms modprobe@configfs.service
15ms initrd-udevadm-cleanup-db.service
14ms modprobe@fuse.service
13ms initrd-cleanup.service
13ms systemd-update-done.service
12ms systemd-tmpfiles-setup-dev.service
11ms lm_sensors.service
10ms dev-disk-by\x2duuid-803297b5\x2dc04e\x2d45f1\x2db0c0\x2dfab8ba283a90.swap
10ms systemd-machined.service
8ms systemd-fsck-root.service
8ms modprobe@dm_mod.service
7ms rtkit-daemon.service
7ms systemd-modules-load.service
7ms modprobe@loop.service
5ms systemd-update-utmp.service
5ms modprobe@drm.service
5ms systemd-udev-load-credentials.service
5ms systemd-sysctl.service
5ms var-log.mount
4ms var-tmp.mount
3ms sys-fs-fuse-connections.mount

cat /etc/fstab:

╰─λ cat /etc/fstab
File: /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=F26E-0F24                            /boot/efi      vfat    defaults,umask=0077 0 2
UUID=c076eea8-e53f-492e-968c-556fdf1dadae /              btrfs   subvol=/@,defaults,noatime,compress=zstd 0 0
UUID=c076eea8-e53f-492e-968c-556fdf1dadae /home          btrfs   subvol=/@home,defaults,noatime,compress=zstd 0 0
UUID=c076eea8-e53f-492e-968c-556fdf1dadae /root          btrfs   subvol=/@root,defaults,noatime,compress=zstd 0 0
UUID=c076eea8-e53f-492e-968c-556fdf1dadae /srv           btrfs   subvol=/@srv,defaults,noatime,compress=zstd 0 0
UUID=c076eea8-e53f-492e-968c-556fdf1dadae /var/cache     btrfs   subvol=/@cache,defaults,noatime,compress=zstd 0 0
UUID=c076eea8-e53f-492e-968c-556fdf1dadae /var/log       btrfs   subvol=/@log,defaults,noatime,compress=zstd 0 0
UUID=c076eea8-e53f-492e-968c-556fdf1dadae /var/tmp       btrfs   subvol=/@tmp,defaults,noatime,compress=zstd 0 0
UUID=803297b5-c04e-45f1-b0c0-fab8ba283a90 swap           swap    defaults   0 0
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0

Perhaps that can help
pls benchmark your nvme (example hdparm)
test with
sudo smartctl -a /dev/nvme0
perhaps your nvme is the problem.
make a bios update again. ( it´s a beta bios but…with new agesa)
https://www.msi.com/Motherboard/MAG-X670E-TOMAHAWK-WIFI/support

disabling serial ports ( if you don`t need ) + fastboot
on which m.2 slot is your nvme ?
if your samsung nvme in slot 1 change to slot 2 and test it again.
reason …your Samsung nvme, which virtually maxes out PCIe 4.0, but does not really support PCIe 5.0. ( only with 2 lanes…that´s enough but perhaps the prob.

also take a look there
https://uk.msi.com/blog/boost-the-performance-of-amd-ryzen-9000-series-msi-pbo-enhanced-mode-set-thermal-point-and-high-efficiency-mode

2 Likes

Thanks for the suggestions. Good call on the nvme gen 4 vs gen 5 slots. It was in the m2_1 gen 5 slot, switching to the m2_2 gen 4 slot did the trick.

systemd-analyze:

╰─λ systemd-analyze
Startup finished in 11.685s (firmware) + 6.294s (loader) + 1.024s (kernel) + 2.559s (initrd) + 2.649s (userspace) = 24.213s
graphical.target reached after 2.649s in userspace.

I couldn’t run hdparm on nvme0, but could on nvme0n1. I tried to find equivalent to hdparm -t and hdparm -T with nvme-cli, but didn’t see anything obvious.

hdparm not working without nvme0n1

sudo hdparm -t /dev/nvme0:

[🔴] × sudo hdparm -t /dev/nvme0

/dev/nvme0:
BLKGETSIZE failed: Inappropriate ioctl for device
Timing buffered disk reads: read() failed: Invalid argument
BLKFLSBUF failed: Inappropriate ioctl for device

sudo hdparm -T /dev/nvme0:

[🔴] × sudo hdparm -T /dev/nvme0

/dev/nvme0:
lseek() failed: Illegal seek

I did already have Enhanced Mode Boost(auto) enabled, High-Efficiency Mode(auto) enabled, and Memory Context restore enabled in my BIOS. Without memory context restore I was getting very slow post times without it.

Pre-moving to gen 4 slot

sudo smartctl -a /dev/nvme0:

╰─λ sudo smartctl -a /dev/nvme0
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.12.4-zen1-1-zen] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       Samsung SSD 990 EVO 1TB
Serial Number:                      S7M3NL0X938323M
Firmware Version:                   0B2QKXJ7
PCI Vendor/Subsystem ID:            0x144d
IEEE OUI Identifier:                0x002538
Total NVM Capacity:                 1,000,204,886,016 [1.00 TB]
Unallocated NVM Capacity:           0
Controller ID:                      1
NVMe Version:                       2.0
Number of Namespaces:               1
Namespace 1 Size/Capacity:          1,000,204,886,016 [1.00 TB]
Namespace 1 Utilization:            318,743,506,944 [318 GB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            002538 2941a0bd4b
Local Time is:                      Tue Dec 17 11:01:29 2024 EST
Firmware Updates (0x16):            3 Slots, no Reset required
Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
Optional NVM Commands (0x00df):     Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp Verify
Log Page Attributes (0x2f):         S/H_per_NS Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg Log0_FISE_MI
Maximum Data Transfer Size:         128 Pages
Warning  Comp. Temp. Threshold:     85 Celsius
Critical Comp. Temp. Threshold:     85 Celsius

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
0 +     7.47W       -        -    0  0  0  0        0       0
1 +     7.47W       -        -    1  1  1  1      500     500
2 +     7.47W       -        -    2  2  2  2     1100    3600
3 -   0.0800W       -        -    3  3  3  3     3700    2400
4 -   0.0070W       -        -    4  4  4  4     3700   45000

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
0 +     512       0         0

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        30 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    0%
Data Units Read:                    2,226,912 [1.14 TB]
Data Units Written:                 1,239,431 [634 GB]
Host Read Commands:                 197,201,848
Host Write Commands:                13,585,210
Controller Busy Time:               32
Power Cycles:                       50
Power On Hours:                     38
Unsafe Shutdowns:                   16
Media and Data Integrity Errors:    0
Error Information Log Entries:      0
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Temperature Sensor 1:               43 Celsius
Temperature Sensor 2:               30 Celsius

Error Information (NVMe Log 0x01, 16 of 64 entries)
No Errors Logged

Self-test Log (NVMe Log 0x06)
Self-test status: No self-test in progress
No Self-tests Logged

sudo nvme smart-log /dev/nvme0:

╰─λ sudo nvme smart-log /dev/nvme0
Smart Log for NVME device:nvme0 namespace-id:ffffffff
critical_warning                        : 0
temperature                             : 89 °F (305 K)
available_spare                         : 100%
available_spare_threshold               : 10%
percentage_used                         : 0%
endurance group critical warning summary: 0
Data Units Read                         : 2228174 (1.14 TB)
Data Units Written                      : 1241045 (635.42 GB)
host_read_commands                      : 197218906
host_write_commands                     : 13621999
controller_busy_time                    : 32
power_cycles                            : 50
power_on_hours                          : 38
unsafe_shutdowns                        : 16
media_errors                            : 0
num_err_log_entries                     : 0
Warning Temperature Time                : 0
Critical Composite Temperature Time     : 0
Temperature Sensor 1                    : 113 °F (318 K)
Temperature Sensor 2                    : 89 °F (305 K)
Thermal Management T1 Trans Count       : 0
Thermal Management T2 Trans Count       : 0
Thermal Management T1 Total Time        : 0
Thermal Management T2 Total Time        : 0

sudo hdparm -Tt --direct /dev/nvme0n1:

╰─λ sudo hdparm -Tt --direct /dev/nvme0n1

/dev/nvme0n1:
Timing O_DIRECT cached reads:   11922 MB in  2.00 seconds = 5965.63 MB/sec
Timing O_DIRECT disk reads: 6214 MB in  3.00 seconds = 2071.29 MB/sec
Post-moving to gen 4 slot

sudo smartctl -a /dev/nvme0:

╰─λ sudo smartctl -a /dev/nvme0
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.12.4-zen1-1-zen] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       Samsung SSD 990 EVO 1TB
Serial Number:                      S7M3NL0X938323M
Firmware Version:                   0B2QKXJ7
PCI Vendor/Subsystem ID:            0x144d
IEEE OUI Identifier:                0x002538
Total NVM Capacity:                 1,000,204,886,016 [1.00 TB]
Unallocated NVM Capacity:           0
Controller ID:                      1
NVMe Version:                       2.0
Number of Namespaces:               1
Namespace 1 Size/Capacity:          1,000,204,886,016 [1.00 TB]
Namespace 1 Utilization:            318,930,087,936 [318 GB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            002538 2941a0bd4b
Local Time is:                      Tue Dec 17 18:11:19 2024 EST
Firmware Updates (0x16):            3 Slots, no Reset required
Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
Optional NVM Commands (0x00df):     Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp Verify
Log Page Attributes (0x2f):         S/H_per_NS Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg Log0_FISE_MI
Maximum Data Transfer Size:         128 Pages
Warning  Comp. Temp. Threshold:     85 Celsius
Critical Comp. Temp. Threshold:     85 Celsius

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
0 +     7.47W       -        -    0  0  0  0        0       0
1 +     7.47W       -        -    1  1  1  1      500     500
2 +     7.47W       -        -    2  2  2  2     1100    3600
3 -   0.0800W       -        -    3  3  3  3     3700    2400
4 -   0.0070W       -        -    4  4  4  4     3700   45000

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
0 +     512       0         0

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        32 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    0%
Data Units Read:                    2,492,190 [1.27 TB]
Data Units Written:                 1,245,019 [637 GB]
Host Read Commands:                 198,353,236
Host Write Commands:                13,749,847
Controller Busy Time:               32
Power Cycles:                       61
Power On Hours:                     41
Unsafe Shutdowns:                   20
Media and Data Integrity Errors:    0
Error Information Log Entries:      0
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Temperature Sensor 1:               49 Celsius
Temperature Sensor 2:               32 Celsius

Error Information (NVMe Log 0x01, 16 of 64 entries)
No Errors Logged

Self-test Log (NVMe Log 0x06)
Self-test status: No self-test in progress
No Self-tests Logged

sudo nvme smart-log /dev/nvme0:

╰─λ sudo nvme smart-log /dev/nvme0
Smart Log for NVME device:nvme0 namespace-id:ffffffff
critical_warning                        : 0
temperature                             : 89 °F (305 K)
available_spare                         : 100%
available_spare_threshold               : 10%
percentage_used                         : 0%
endurance group critical warning summary: 0
Data Units Read                         : 2492430 (1.28 TB)
Data Units Written                      : 1245044 (637.46 GB)
host_read_commands                      : 198363084
host_write_commands                     : 13750964
controller_busy_time                    : 32
power_cycles                            : 61
power_on_hours                          : 41
unsafe_shutdowns                        : 20
media_errors                            : 0
num_err_log_entries                     : 0
Warning Temperature Time                : 0
Critical Composite Temperature Time     : 0
Temperature Sensor 1                    : 120 °F (322 K)
Temperature Sensor 2                    : 89 °F (305 K)
Thermal Management T1 Trans Count       : 0
Thermal Management T2 Trans Count       : 0
Thermal Management T1 Total Time        : 0
Thermal Management T2 Total Time        : 0
╰─λ sudo hdparm -Tt --direct /dev/nvme0n1

/dev/nvme0n1:
Timing O_DIRECT cached reads:   11520 MB in  2.00 seconds = 5764.49 MB/sec
Timing O_DIRECT disk reads: 6182 MB in  3.00 seconds = 2059.98 MB/sec

Now I have one new problem, and one interesting observation.

New problem monitor never gets a signal after waking from sleep. PC powers on, but never get a signal on my monitor. Tried both BIOS(w/ USB wake) and OS wake BIOS settings. No change.

Observation I’m still not getting anywhere near my drives advertised read speeds.

I’ll continue to troubleshoot and report back anything interesting. Or if you have any other insights it would be appreciated. Thanks again for the suggestion on what turned out to probably be a a build mistake on my part.

Please mark the solution and open a new thread.

From template.

  • ONE issue per topic.
    :slight_smile:
1 Like

Sure, will do. :slight_smile:

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.