Kernel 6.12.9, Unable to mount root fs on "/dev/nvme0n1p1"

I have checked How to search for solutions the right way | Garuda Linux wiki
I have checked FAQ and Tutorials Table of Contents

My question, how can I determine which kernel module/s are at fault for the inability to find root fs post update? … bootlog=on in grub seems to make no detailed log of the failed boot.

I cannot 'tell ’ if it’s the btrfs ID that’s changed for fstab, or if it’s the nvme kernel module which is no longer working… or something else. Those seem the two most likely causes.

How should I proceed from here with getting patched to 6.12.9 while avoiding this storage/root-fs based kernel-panic?

Hardware/Configuration details below:

Here is the output from garuda-inxi:

System:
Kernel: 6.12.8-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=87fb27c6-bb8d-4f0c-83d0-8d732ed299d0 rw rootflags=subvol=@
quiet loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.2.5 tk: Qt v: N/A info: frameworks v: 6.10.0
wm: kwin_wayland with: krunner vt: 1 dm: SDDM Distro: Garuda
base: Arch Linux
Machine:
Type: Desktop Mobo: Gigabyte model: Z170MX-Gaming 5 v: x.x
serial: <superuser required> uuid: <superuser required>
UEFI-[Legacy]: American Megatrends v: F22f date: 03/09/2018
CPU:
Info: model: Intel Core i7-6700K bits: 64 type: MT MCP arch: Skylake-S
gen: core 6 level: v3 note: check built: 2015 process: Intel 14nm family: 6
model-id: 0x5E (94) stepping: 3 microcode: 0xF0
Topology: cpus: 1x dies: 1 clusters: 4 cores: 4 threads: 8 tpc: 2
smt: enabled cache: L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB
desc: 4x256 KiB L3: 8 MiB desc: 1x8 MiB
Speed (MHz): avg: 1700 min/max: 800/4200 scaling: driver: intel_pstate
governor: powersave cores: 1: 1700 2: 1700 3: 1700 4: 1700 5: 1700 6: 1700
7: 1700 8: 1700 bogomips: 63999
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA AD106 [GeForce RTX 4060 Ti] vendor: ZOTAC driver: nvidia
v: 565.77 alternate: nouveau,nvidia_drm non-free: 550/565.xx+
status: current (as of 2025-01) arch: Lovelace code: AD1xx
process: TSMC n4 (5nm) built: 2022+ pcie: gen: 2 speed: 5 GT/s lanes: 8
link-max: gen: 4 speed: 16 GT/s ports: active: none off: DP-1,DP-2
empty: DP-3,HDMI-A-1 bus-ID: 01:00.0 chip-ID: 10de:2803 class-ID: 0300
Device-2: AVerMedia Live Streamer CAM 313 driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-2:2
chip-ID: 07ca:313a class-ID: 0102 serial: <filter>
Display: wayland server: X.org v: 1.21.1.15 with: Xwayland v: 24.1.4
compositor: kwin_wayland driver: X: loaded: nvidia unloaded: modesetting
alternate: fbdev,nouveau,nv,vesa gpu: nvidia,nvidia-nvswitch
d-rect: 4720x2160 display-ID: 0
Monitor-1: DP-1 pos: bottom-l model: Sceptre O34 built: 2024 res:
mode: 3440x1440 hz: 60 scale: 100% (1) dpi: 110 gamma: 1.2
size: 797x334mm (31.38x13.15") diag: 864mm (34") modes: max: 3440x1440
min: 640x480
Monitor-2: DP-2 pos: top-right model: Mitsubishi MEUSLCD5 serial: <filter>
built: 2004 res: mode: 1280x720 hz: 60 scale: 100% (1) gamma: 1.2 size: N/A
modes: max: 1280x720 min: 640x480
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 4060 Ti/PCIe/SSE2
memory: 15.62 GiB display-ID: :1.0
API: Vulkan v: 1.4.303 layers: 11 device: 0 type: discrete-gpu name: NVIDIA
GeForce RTX 4060 Ti driver: N/A device-ID: 10de:2803
surfaces: xcb,xlib,wayland
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: corectrl, nvidia-settings,
nvidia-smi wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: Gigabyte
driver: snd_hda_intel v: kernel alternate: snd_soc_avs bus-ID: 00:1f.3
chip-ID: 8086:a170 class-ID: 0403
Device-2: NVIDIA AD106M High Definition Audio vendor: ZOTAC
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 8
link-max: gen: 4 speed: 16 GT/s bus-ID: 01:00.1 chip-ID: 10de:22bd
class-ID: 0403
Device-3: C-Media USB Audio Device
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
lanes: 1 mode: 1.1 bus-ID: 1-14:6 chip-ID: 0d8c:0012 class-ID: 0300
Device-4: AVerMedia Live Streamer CAM 313 driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-2:2
chip-ID: 07ca:313a class-ID: 0102 serial: <filter>
API: ALSA v: k6.12.8-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: Qualcomm Atheros Killer E220x Gigabit Ethernet vendor: Gigabyte
driver: alx v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: d000
bus-ID: 03:00.0 chip-ID: 1969:e091 class-ID: 0200
IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IF-ID-1: docker0 state: up speed: 10000 Mbps duplex: unknown mac: <filter>
IF-ID-2: vethf24f958 state: up speed: 10000 Mbps duplex: full
mac: <filter>
Info: services: NetworkManager, smbd, sshd, systemd-timesyncd
Drives:
Local Storage: total: 931.51 GiB used: 862.33 GiB (92.6%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 980 PRO 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: 5B2QGXA7 temp: 36.9 C
scheme: MBR
Partition:
ID-1: / raw-size: 931.51 GiB size: 931.51 GiB (100.00%)
used: 862.33 GiB (92.6%) fs: btrfs dev: /dev/nvme0n1p1 maj-min: 259:1
ID-2: /home raw-size: 931.51 GiB size: 931.51 GiB (100.00%)
used: 862.33 GiB (92.6%) fs: btrfs dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /var/log raw-size: 931.51 GiB size: 931.51 GiB (100.00%)
used: 862.33 GiB (92.6%) fs: btrfs dev: /dev/nvme0n1p1 maj-min: 259:1
ID-4: /var/tmp raw-size: 931.51 GiB size: 931.51 GiB (100.00%)
used: 862.33 GiB (92.6%) fs: btrfs dev: /dev/nvme0n1p1 maj-min: 259:1
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 31.3 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 max-streams: 8
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 32.0 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 32 GiB available: 31.3 GiB used: 7.58 GiB (24.2%)
Processes: 333 Power: uptime: 13m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.47 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 2142 libs: 590 tools: octopi,paru Compilers:
clang: 19.1.7 gcc: 14.2.1 alt: 13 Shell: garuda-inxi default: Bash v: 5.2.37
running-in: konsole inxi: 3.3.37
Garuda (2.6.26-1.1):
System install date:     2024-10-06
Last full system update: 2025-01-13
Is partially upgraded:   Yes
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       <superuser required>
Failed units:

Here is smartctl for that nvme device, already current firmware:

=== START OF INFORMATION SECTION ===
Model Number:                       Samsung SSD 980 PRO 1TB
Serial Number:                      ##########
Firmware Version:                   5B2QGXA7
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:                      6
NVMe Version:                       1.3
Number of Namespaces:               1
Namespace 1 Size/Capacity:          1,000,204,886,016 [1.00 TB]
Namespace 1 Utilization:            922,090,106,880 [922 GB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            002538 b831a5d98d
Local Time is:                      Sat Jan 18 12:58:06 2025 PST

Here is the abbreviated dmidecode:

SMBIOS 3.0.0 present.
Table at 0x5F59D000.

Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: American Megatrends Inc.
Version: F22f
Release Date: 03/09/2018
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 16 MB
Characteristics:
PCI is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
BIOS ROM is socketed
EDD is supported
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
ACPI is supported
USB legacy is supported
BIOS boot specification is supported
Targeted content distribution is supported
UEFI is supported
BIOS Revision: 5.12

Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: Z170MX-Gaming 5
Version: Default string
Serial Number: Default string
UUID: 038d0240-045c-0553-f206-af0700080009
Wake-up Type: Power Switch
SKU Number: Default string
Family: Default string

Loaded modules:

Module                  Size  Used by
xt_nat                 16384  1
xt_tcpudp              20480  0
veth                   40960  0
xt_conntrack           12288  1
nft_chain_nat          12288  3
xt_MASQUERADE          16384  2
nf_nat                 65536  3 xt_nat,nft_chain_nat,xt_MASQUERADE
bridge                483328  0
stp                    12288  1 bridge
llc                    16384  2 bridge,stp
nf_conntrack_netlink    65536  0
nf_conntrack          212992  5 xt_conntrack,nf_nat,xt_nat,nf_conntrack_netlink,xt_MASQUERADE
nf_defrag_ipv6         24576  1 nf_conntrack
nf_defrag_ipv4         12288  1 nf_conntrack
xfrm_user              69632  1
xfrm_algo              16384  1 xfrm_user
xt_addrtype            12288  2
nft_compat             24576  6
nf_tables             409600  103 nft_compat,nft_chain_nat
snd_seq_dummy          12288  0
snd_hrtimer            12288  1
snd_seq               139264  7 snd_seq_dummy
overlay               245760  1
qrtr                   57344  2
rfkill                 40960  2
intel_rapl_msr         20480  0
intel_rapl_common      57344  1 intel_rapl_msr
intel_tcc_cooling      12288  0
x86_pkg_temp_thermal    16384  0
intel_powerclamp       20480  0
snd_soc_avs           245760  0
uvcvideo              180224  0
videobuf2_vmalloc      20480  1 uvcvideo
snd_soc_hda_codec      28672  1 snd_soc_avs
coretemp               20480  0
snd_hda_ext_core       36864  2 snd_soc_avs,snd_soc_hda_codec
uvc                    12288  1 uvcvideo
iTCO_wdt               16384  0
snd_hda_codec_realtek   233472  1
videobuf2_memops       16384  1 videobuf2_vmalloc
snd_soc_core          471040  2 snd_soc_avs,snd_soc_hda_codec
kvm_intel             446464  0
snd_hda_codec_generic   131072  1 snd_hda_codec_realtek
videobuf2_v4l2         45056  1 uvcvideo
intel_pmc_bxt          16384  1 iTCO_wdt
ee1004                 16384  0
iTCO_vendor_support    12288  1 iTCO_wdt
snd_hda_scodec_component    20480  1 snd_hda_codec_realtek
videobuf2_common       98304  4 videobuf2_vmalloc,videobuf2_v4l2,uvcvideo,videobuf2_memops
snd_compress           28672  2 snd_soc_avs,snd_soc_core
kvm                  1470464  1 kvm_intel
ac97_bus               12288  1 snd_soc_core
videodev              405504  2 videobuf2_v4l2,uvcvideo
snd_hda_codec_hdmi    106496  1
snd_pcm_dmaengine      16384  1 snd_soc_core
rapl                   20480  0
snd_usb_audio         577536  2
intel_cstate           20480  0
snd_usbmidi_lib        53248  1 snd_usb_audio
snd_ump                40960  1 snd_usb_audio
snd_hda_intel          69632  2
snd_rawmidi            57344  2 snd_usbmidi_lib,snd_ump
snd_intel_dspcfg       45056  2 snd_soc_avs,snd_hda_intel
snd_intel_sdw_acpi     16384  1 snd_intel_dspcfg
intel_wmi_thunderbolt    16384  0
snd_hda_codec         229376  6 snd_hda_codec_generic,snd_soc_avs,snd_hda_codec_hdmi,snd_soc_hda_codec,snd_hda_intel,snd_hda_codec_realtek
mxm_wmi                12288  0
intel_uncore          274432  0
i2c_i801               40960  0
snd_hda_core          151552  8 snd_hda_codec_generic,snd_soc_avs,snd_hda_codec_hdmi,snd_soc_hda_codec,snd_hda_intel,snd_hda_ext_core,snd_hda_codec,snd_hda_codec_realtek
snd_hwdep              20480  2 snd_usb_audio,snd_hda_codec
snd_seq_device         16384  3 snd_seq,snd_ump,snd_rawmidi
alx                    69632  0
i2c_smbus              20480  1 i2c_i801
snd_pcm               221184  9 snd_soc_avs,snd_hda_codec_hdmi,snd_hda_intel,snd_usb_audio,snd_hda_codec,snd_compress,snd_soc_core,snd_hda_core,snd_pcm_dmaengine
mdio                   12288  1 alx
i2c_mux                16384  1 i2c_i801
snd_timer              57344  3 snd_seq,snd_hrtimer,snd_pcm
snd                   163840  26 snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_usb_audio,snd_usbmidi_lib,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_compress,snd_soc_core,snd_ump,snd_pcm,snd_rawmidi
mc                     98304  5 videodev,snd_usb_audio,videobuf2_v4l2,uvcvideo,videobuf2_common
soundcore              16384  1 snd
joydev                 24576  0
mousedev               24576  0
intel_pmc_core        126976  0
intel_vsec             20480  1 intel_pmc_core
pmt_telemetry          16384  1 intel_pmc_core
pmt_class              16384  1 pmt_telemetry
acpi_pad              184320  0
mac_hid                12288  0
loop                   40960  0
dm_mod                229376  0
nfnetlink              20480  5 nft_compat,nf_conntrack_netlink,nf_tables
zram                   57344  1
842_decompress         16384  1 zram
842_compress           24576  1 zram
lz4hc_compress         20480  1 zram
lz4_compress           24576  1 zram
ip_tables              36864  0
x_tables               65536  7 xt_conntrack,nft_compat,xt_tcpudp,xt_addrtype,xt_nat,ip_tables,xt_MASQUERADE
vboxnetflt             40960  0
vboxnetadp             32768  0
vboxdrv               700416  2 vboxnetadp,vboxnetflt
uinput                 24576  0
nvidia_uvm           3932160  6
nvidia_drm            139264  144
drm_ttm_helper         16384  1 nvidia_drm
ttm                   114688  1 drm_ttm_helper
nvidia_modeset       1671168  59 nvidia_drm
crct10dif_pclmul       12288  1
crc32_pclmul           12288  0
polyval_clmulni        12288  0
polyval_generic        12288  1 polyval_clmulni
ghash_clmulni_intel    16384  0
hid_generic            12288  0
sha512_ssse3           53248  0
sha256_ssse3           40960  1
usbhid                 90112  0
sha1_ssse3             32768  0
nvme                   69632  1
aesni_intel           126976  0
gf128mul               20480  2 polyval_generic,aesni_intel
crypto_simd            16384  1 aesni_intel
nvme_core             262144  2 nvme
cryptd                 32768  2 crypto_simd,ghash_clmulni_intel
nvme_auth              24576  1 nvme_core
nvidia              77508608  1034 nvidia_uvm,nvidia_modeset
btrfs                2273280  1
blake2b_generic        24576  0
libcrc32c              12288  4 nf_conntrack,nf_nat,btrfs,nf_tables
crc32c_generic         12288  0
crc32c_intel           16384  2
xor                    20480  1 btrfs
raid6_pq              122880  1 btrfs
video                  81920  1 nvidia_modeset
wmi                    32768  3 video,intel_wmi_thunderbolt,mxm_wmi
i2c_dev                28672  0
sg                     53248  0
crypto_user            16384  0

… and the error itself, after applying the 6.12.9 kernel and headers update.:

List of all partitions:
No filesystem could mount root, tried:
  fuseblk

Kernel panic - not syncing: VFS: Unable to mount root fs on "/dev/nvme0n1p1"

No response…
… most likely conclusion:
I’m an idiot, and am looking for an exit to the paper bag.
… can wait for 6.12.10, or switch away from zen… fair enough.

Would be nice to have a specific approach though.
Yes, will break it again… reboot, check the existing fstab entries with a boot disk… etc.

And yes… I can build 6.12.9 manually, excluding nvme, nvme-core, nvme-auth … ‘hoping’ that’s the issue… and moving to Intel drivers after that.
Just a little surprised I guess.

Fix this first, please.

2 Likes
╰─λ checkupdates
linux-zen 6.12.9.zen1-1 -> 6.12.10.zen1-1
linux-zen-headers 6.12.9.zen1-1 -> 6.12.10.zen1-1
2 Likes

I understand that you have to point this out… but it is reporting that way because I upgraded everything ‘around’ those two packages as a diagnostic step to help confirm it was in fact the kernel update (and nothing else) causing the problem.

Shouldn’t I -expect- the partial upgrade message having followed that course?

(yes, I’m aware of consequences, and the delta-packages wasn’t particularly important … but I see that target moves ‘quickly’ … with another 20 or so packages today)

In any event… I believe your response is suggesting we ‘need a stable foundation’ before continuing troubleshooting. Fair enough.
Though, your response did not address the question of how to identify/confirm which aspect of the kernel or kernel module was at fault.

I appreciate your efforts, and I really love the OS… but this seems unhelpful.

I may continue with the idea of compiling 6.12.9 …(10) myself… and try to compile with the older modules. … and do a diff while I’m at it, once I confirm what’s breaking things.

Have confirmed, same issue with:

linux-xen-6.12.10.zen1-1
linux-xen-headers-6.12.10.zen1-1

… I will look into it more.
Thank you again for your response.

For everyone’s benefit, here is the specific error on screen with 6.12.10-zen1-1
I’ll continue on this tomorrow morning.

Install lts kernel (over pacman)
take a look in the grub.cfg file. Same root UUIDs ?

2 Likes

This is not helpful - please post the SMART values ​​of the nvme.

The fstab is not read at this point.

The nvme modules are loading and in my opinion there is no indication that they are not working.


You have the problem with 2 kernel versions, do you get an error message when updating the kernel?
If you have the same issue with the LTS kernel (as @gampel suggested), then it looks more like the initramfs is not being built for the kernel (or is missing). Check this out.

3 Likes

This topic can be closed for now.
I did not have time to dig into the modules or initramfs problems, though I can confirm initramfs was build successfully. Continued to be the case that ‘block’ device seemed unavailable to the system following the kernel update.

I can confirm the same issue occurred with both 6.12.9 and 6.12.10, across lts, mainline, and zen.

Ultimeately, DD’d the NVME to an SSD and confirmed problem was effectively resolved. Clean installed to the NVME, and upon update to 6.12.9 or above - encountered the same issue.

Thank @nepti, your points were well taken - and I can confirm the ‘values’ for the smartdata were fine. I was just trying to give an initial synopsis of the working environment, and will remember to include the sexy bits next time. Your point about fstab and initramfs were helpful in thinking about the problem.

Didn’t have time to push further, and already falling behind on rolling updates.
So I just kept the SSD install, DD’d back to the nvme, cleaned up btrfs, and linked my /home in fstab to the UUID of the previous nvme /home btrfs subvolume.

Has been running fine, and the difference in performance for the things I care about is barely noticeable. Snapshots are still happy.

I’ll try switching back at some future release date.

I just wanted to circle back and thank folks for their input, and give some conclusion to this specific thread.

(Edit: One last thing I wanted to mention, and thank you lot for - this is still by far the easiest distribution I’ve used for a desktop. The BTRFS snapshots supported directly in grub was wonderful, refreshing, and painless. This enabled faster iteration on testing and possible solutions. I’ve never been ‘happier’ with a linux desktop distribution, which I’m certain would offend some of my SUSE friends. Garuda has been user friendly, performative, current, ‘as secure as others’, and has been broadly very stable for a rolling distribution. Well done.)

1 Like

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