Snapshot - Switch Root Failing

Hello, I noticed today when tying to use a snapshot Switch root was failing to start. This is less of a how to fix. More of a pointing it out. But if there is a solution that would be great too.

  Kernel: 6.6.7-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1 clocksource: tsc
    available: hpet,acpi_pm parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=2c314f01-6930-43e5-ae20-9cbddce1a512 rw rootflags=subvol=@ nvidia-drm.modeset=1
    rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3
  Desktop: KDE Plasma v: 5.27.10 tk: Qt v: 5.15.11 wm: kwin_x11 vt: 2 dm: SDDM
    Distro: Garuda Linux base: Arch Linux
  Type: Desktop Mobo: ASUSTeK model: PRIME X570-PRO v: Rev X.0x serial: <superuser required>
    UEFI: American Megatrends v: 4802 date: 06/15/2023
  Info: model: AMD Ryzen 7 3700X bits: 64 type: MT MCP arch: Zen 2 gen: 3 level: v3 note: check
    built: 2020-22 process: TSMC n7 (7nm) family: 0x17 (23) model-id: 0x71 (113) stepping: 0
    microcode: 0x8701030
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache: L1: 512 KiB
    desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB L3: 32 MiB desc: 2x16 MiB
  Speed (MHz): avg: 4034 high: 4329 min/max: 2200/4426 boost: enabled scaling:
    driver: acpi-cpufreq governor: performance cores: 1: 3600 2: 3600 3: 4152 4: 3600 5: 4329 6: 4230
    7: 4323 8: 4320 9: 4322 10: 3600 11: 3600 12: 4302 13: 4324 14: 4325 15: 3600 16: 4325
    bogomips: 115198
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities: <filter>
  Device-1: NVIDIA GM204 [GeForce GTX 980] vendor: Gigabyte driver: nvidia v: 545.29.06
    alternate: nouveau,nvidia_drm non-free: 545.xx+ status: current (as of 2023-10; EOL~2026-12-xx)
    arch: Maxwell code: GMxxx process: TSMC 28nm built: 2014-2019 pcie: gen: 3 speed: 8 GT/s
    lanes: 16 ports: active: none off: DP-2 empty: DP-1, DP-3, DVI-I-1, HDMI-A-1 bus-ID: 0a:00.0
    chip-ID: 10de:13c0 class-ID: 0300
  Display: x11 server: X.Org v: 21.1.10 with: Xwayland v: 23.2.3 compositor: kwin_x11 driver: X:
    loaded: nvidia gpu: nvidia,nvidia-nvswitch display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3440x1440 s-dpi: 109 s-size: 802x333mm (31.57x13.11") s-diag: 868mm (34.19")
  Monitor-1: DP-2 note: disabled model: LG (GoldStar) ULTRAGEAR serial: <filter> built: 2020
    res: 3440x1440 dpi: 109 gamma: 1.2 size: 800x335mm (31.5x13.19") diag: 867mm (34.1") modes:
    max: 3440x1440 min: 640x480
  API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2 drv: swrast gbm:
    drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia inactive: wayland,device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 545.29.06 glx-v: 1.4
    direct-render: yes renderer: NVIDIA GeForce GTX 980/PCIe/SSE2 memory: 3.91 GiB
  API: Vulkan Message: No Vulkan data available.
  Device-1: NVIDIA GM204 High Definition Audio vendor: Gigabyte driver: snd_hda_intel v: kernel
    pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 0a:00.1 chip-ID: 10de:0fbb class-ID: 0403
  Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie:
    gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 0c:00.4 chip-ID: 1022:1487 class-ID: 0403
  Device-3: Texas Instruments PCM2900C Audio CODEC driver: hid-generic,snd-usb-audio,usbhid
    type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-2:3 chip-ID: 08bb:29c0
    class-ID: 0300
  API: ALSA v: k6.6.7-zen1-1-zen status: kernel-api with: aoss type: oss-emulator tools: N/A
  Server-1: PipeWire v: 1.0.0 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
  Device-1: Intel Wireless 7260 driver: iwlwifi v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
    bus-ID: 05:00.0 chip-ID: 8086:08b1 class-ID: 0280
  IF: wlp5s0 state: up mac: <filter>
  Device-2: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 06:00.0 chip-ID: 8086:1539 class-ID: 0200
  IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-1: Intel Bluetooth wireless interface driver: btusb v:
 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-6:5 chip-ID: 8087:07dc class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 4.0 lmp-v: 6 status:
    discoverable: no pairing: no class-ID: 7c0104
  Local Storage: total: 4.68 TiB used: 2.83 TiB (60.4%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:4 vendor: Western Digital model: WD BLACK SN770 2TB
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD
    serial: <filter> fw-rev: 731100WD temp: 52.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: HP model: SSD EX920 1TB size: 953.87 GiB block-size:
    physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 32A0T2IA temp: 41.9 C scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 vendor: OCZ model: VERTEX3 size: 111.79 GiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s tech: SSD serial: <filter> fw-rev: 2.22
    scheme: GPT
  ID-4: /dev/sdb maj-min: 8:16 vendor: Western Digital model: WD20EZAZ-00L9GB0 size: 1.82 TiB
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 5400 serial: <filter>
    fw-rev: 0A80 scheme: GPT
  ID-1: / raw-size: 1.64 TiB size: 1.64 TiB (100.00%) used: 736.29 GiB (43.8%) fs: btrfs
    dev: /dev/nvme0n1p13 maj-min: 259:11
  ID-2: /boot/efi raw-size: 498 MiB size: 497 MiB (99.80%) used: 346.1 MiB (69.6%) fs: vfat
    dev: /dev/nvme0n1p1 maj-min: 259:5
  ID-3: /home raw-size: 1.64 TiB size: 1.64 TiB (100.00%) used: 736.29 GiB (43.8%) fs: btrfs
    dev: /dev/nvme0n1p13 maj-min: 259:11
  ID-4: /var/log raw-size: 1.64 TiB size: 1.64 TiB (100.00%) used: 736.29 GiB (43.8%) fs: btrfs
    dev: /dev/nvme0n1p13 maj-min: 259:11
  ID-5: /var/tmp raw-size: 1.64 TiB size: 1.64 TiB (100.00%) used: 736.29 GiB (43.8%) fs: btrfs
    dev: /dev/nvme0n1p13 maj-min: 259:11
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 15.52 GiB used: 307 MiB (1.9%) priority: 100 comp: zstd
    avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 16 dev: /dev/zram0
  ID-2: swap-2 type: partition size: 9.79 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/nvme0n1p4
    maj-min: 259:8
  System Temperatures: cpu: 44.0 C mobo: 37.0 C gpu: nvidia temp: 40 C
  Fan Speeds (rpm): fan-1: 779 fan-2: 1834 fan-3: 774 fan-4: 750 fan-5: 0 fan-6: 0 fan-7: 0
    gpu: nvidia fan: 20%
  Processes: 480 Uptime: 1m wakeups: 0 Memory: total: 16 GiB available: 15.52 GiB
  used: 4.57 GiB (29.4%) Init: systemd v: 255 default: graphical tool: systemctl Compilers:
  gcc: 13.2.1 alt: 12 clang: 16.0.6 Packages: pm: pacman pkgs: 2380 libs: 613
  tools: octopi,pamac,paru Client: shell wrapper v: 5.2.21-release inxi: 3.3.31
Garuda (2.6.21-1):
  System install date:     2023-10-09
  Last full system update: 2023-12-18
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut nvidia-dkms
  Windows dual boot:       Probably (Run as root to verify)
  Failed units:            fancontrol.service vpn-unlimited-daemon.service 

Can you be more specific about what you are doing with the snapshot?

When booting at the grub menu, pick snapshots, find the one you want to use. for me it was the pre vulkan update. pick either of the two options to boot from an you get the error. When choosing the same snapshot from the garuda desktop with snapshot assistant it rolls back just fine. So its something when rolling back from the grub menu.

Hmm, that’s a weird one. Any hardware changes since those snapshots were taken?

Have you tried booting the snapshot with the fallback initramfs?


No changes, and it happens on both options here, no matter the snapshot.

but work fine if you do it from here,

I’m not to knowledgeable with snappers code to really know inner workings to diagnose it better sadly

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