Unbootable after update

Issues & Assistance
1

Swapped over to Garuda dr490nized-gaming edition recently, haven't used Linux in years, so I don't remember a lot. It has been running great for the past couple of weeks. Lastnight, it said there was an update available, updated and on restart it stops at "Loading initial ramdisk...".

Attempting to boot from a snapshot gives me the following errors:

setfont: KDFONTOP: Function not implemented
ERROR: Root device mounted successfully, but /sbin/init does not exist.
Bailing out, you are on your own. Good luck.

sh: can't access tty; job control turned off

garuda-inxi:

System:
Kernel: 6.0.2-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-x86_64 lang=en_US keytable=us tz=UTC
misobasedir=garuda misolabel=GARUDA_DR460NIZEDGAMING_TALON quiet
systemd.show_status=1 ibt=off driver=nonfree nouveau.modeset=0
i915.modeset=1 radeon.modeset=1
Desktop: KDE Plasma v: 5.26.1 tk: Qt v: 5.15.6 info: latte-dock
wm: kwin_x11 vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop Mobo: ASUSTeK model: STRIX Z270G GAMING v: Rev 1.xx
serial: <superuser required> UEFI: American Megatrends v: 1009
date: 07/23/2017
CPU:
Info: model: Intel Core i7-7700K bits: 64 type: MT MCP arch: Kaby Lake
gen: core 7 level: v3 note: check built: 2018 process: Intel 14nm family: 6
model-id: 0x9E (158) stepping: 9 microcode: 0xF0
Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 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: 4313 high: 4505 min/max: 800/4500 scaling:
driver: intel_pstate governor: performance cores: 1: 4505 2: 4200 3: 4200
4: 4200 5: 4502 6: 4200 7: 4200 8: 4500 bogomips: 67200
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Vulnerabilities:
Type: itlb_multihit status: KVM: VMX unsupported
Type: l1tf mitigation: PTE Inversion
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
Type: retbleed mitigation: IBRS
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: IBRS, IBPB: conditional, RSB filling,
PBRSB-eIBRS: Not affected
Type: srbds mitigation: Microcode
Type: tsx_async_abort mitigation: TSX disabled
Graphics:
Device-1: NVIDIA GP102 [GeForce GTX 1080 Ti] vendor: eVga.com.
driver: nvidia v: 520.56.06 alternate: nouveau,nvidia_drm non-free: 515.xx+
status: current (as of 2022-10) arch: Pascal code: GP10x
process: TSMC 16nm built: 2016-21 pcie: gen: 3 speed: 8 GT/s lanes: 16
bus-ID: 01:00.0 chip-ID: 10de:1b06 class-ID: 0300
Device-2: Logitech C922 Pro Stream Webcam type: USB
driver: snd-usb-audio,uvcvideo bus-ID: 1-2:8 chip-ID: 046d:085c
class-ID: 0102 serial: <filter>
Display: x11 server: X.Org v: 21.1.4 with: Xwayland v: 22.1.3
compositor: kwin_x11 driver: X: loaded: nvidia unloaded: modesetting
alternate: fbdev,nouveau,nv,vesa gpu: nvidia display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 90 s-size: 542x301mm (21.34x11.85")
s-diag: 620mm (24.41")
Monitor-1: DP-4 res: 1920x1080 hz: 60 dpi: 90
size: 544x303mm (21.42x11.93") diag: 623mm (24.52") modes: N/A
OpenGL: renderer: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA
520.56.06 direct render: Yes
Audio:
Device-1: Intel 200 Series PCH HD Audio vendor: ASUSTeK
driver: snd_hda_intel bus-ID: 1-2:8 v: kernel bus-ID: 00:1f.3
chip-ID: 046d:085c chip-ID: 8086:a2f0 class-ID: 0102 serial: <filter>
class-ID: 0403
Device-2: NVIDIA GP102 HDMI Audio vendor: eVga.com. driver: snd_hda_intel
v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.1
chip-ID: 10de:10ef class-ID: 0403
Device-3: Logitech C922 Pro Stream Webcam type: USB
driver: snd-usb-audio,uvcvideo
Sound API: ALSA v: k6.0.2-zen1-1-zen running: yes
Sound Server-1: PulseAudio v: 16.1 running: no
Sound Server-2: PipeWire v: 0.3.59 running: yes
Network:
Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: kernel
port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15b8 class-ID: 0200
IF: enp0s31f6 state: down mac: <filter>
Device-2: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter
vendor: ASUSTeK driver: ath10k_pci v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 bus-ID: 04:00.0 chip-ID: 168c:003e class-ID: 0280 temp: 53.0 C
IF: wlp4s0 state: up mac: <filter>
Bluetooth:
Device-1: ASUSTek Qualcomm Bluetooth 4.1 type: USB driver: btusb v: 0.8
bus-ID: 1-7:5 chip-ID: 0b05:1825 class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:
Local Storage: total: 580.36 GiB used: 0 KiB (0.0%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 960 EVO
500GB size: 465.76 GiB block-size: physical: 512 B logical: 512 B
speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> rev: 3B7QCXE7
temp: 32.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 type: USB vendor: SanDisk model: USB 3.2Gen1
size: 114.6 GiB block-size: physical: 512 B logical: 512 B type: N/A
serial: <filter> rev: 1.00 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
Message: No partition data found.
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 15.56 GiB used: 1.6 GiB (10.3%)
priority: 100 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 40.0 C mobo: N/A gpu: nvidia temp: 27 C
Fan Speeds (RPM): cpu: 1040 gpu: nvidia fan: 0%
Info:
Processes: 229 Uptime: 8m wakeups: 1 Memory: 15.56 GiB used: 3.85 GiB
(24.7%) Init: systemd v: 251 default: graphical tool: systemctl
Compilers: gcc: 12.2.0 Packages: pm: pacman pkgs: 1842 libs: 504
tools: octopi,paru Shell: fish v: 3.5.1 default: Bash v: 5.1.16
running-in: konsole inxi: 3.3.22
warning: database file for 'garuda' does not exist (use '-Sy' to download)
warning: database file for 'core' does not exist (use '-Sy' to download)
warning: database file for 'extra' does not exist (use '-Sy' to download)
warning: database file for 'community' does not exist (use '-Sy' to download)
warning: database file for 'multilib' does not exist (use '-Sy' to download)
warning: database file for 'chaotic-aur' does not exist (use '-Sy' to download)
Garuda (2.6.8-1):
System install date:     2023-02-11
Last full system update: 2023-02-11 ↻
Is partially upgraded:   No
Relevant software:       NetworkManager
Windows dual boot:       <superuser required>
Snapshots:               Snapper
Failed units:
McFly: Importing shell history for the first time. This may take a minute or two...done.
2

That’s weird, someone else got this same issue trying to restore a snapshot earlier in another thread: System won't boot and snapshots not working

Give the alternative snapshot restoration described in that thread a shot (list bootable snapshots from TTY with sudo snapper-tools list, choose a snapshot and restore with sudo snapper-tools restore [number of snapshot]). Don’t forget to reboot after restoring the snapshot.

What was your method used for updating?

4 Likes
3

That worked, thank you! Tried 4 different snapshots before it booted. Apparently the update that broke it was to Nvidia drivers. What do I need to do to prevent that?

Also, when I updated lastnight, it was via a notification in the gui. What's the preferred method?

4

The recommended way to update is to run garuda-update in the terminal. This is a script maintained by the Garuda devs, which includes special considerations like custom hotfixes and mirrorlist maintenance. Check it out: Garuda Update | Garuda Linux wiki

A kernel update breaking the Nvidia drivers is fairly common, unfortunately. There isn’t much you can do but use a different kernel for a little while until an upstream fix comes down; I’d give it a week and check again.

The standard intervention is to temporarily switch to the LTS kernel. First bring your system fully up to date with the garuda-update command, then install the new kernel and headers, and optionally the nvidia-lts driver package as well.

sudo pacman -S linux-lts linux-lts-headers nvidia-lts

Then reboot, and on the advanced boot options menu of the Grub screen you can select the LTS kernel to boot to. This will allow you to keep your system up to date until whatever driver issue broke your system in the update is fixed.

3 Likes
5

Thank you for all of your help, updated via garuda-update, rebooted, and everything is running well now.

6

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