Can't boot, errors after system update

Hi Everyone!

I did a system update this afternoon. Restarted after it was finished and below are photos of the last three screens I see before the system comes to a screeching halt. I'm not including the garuda-inxi output because I'm not able to access the system. I would just like to know if this seems like something I could recover from or if in your opinion the system is "fried" and I need to reinstall. Please share your thoughts. Thank you so much.
I just got blocked from sharing the images of the screen because I'm a new user. How should I proceed?

Use last working snapshot. restore the snapshot, use garuda wiki for details.

No pictures please :wink: we trust you :slight_smile:

2 Likes

Using snapshots (recent as well as older) yields the same (no good) result every time.
I was able to put a picture of my screen through OCR and here's what I'm getting whether I use a snapshot or Garuda Linux on boot screen.

6.231180] Initramfs unpacking failed: ZSTD-compressed data is corrupt 6.589080) Kernel panic not syncing: VFS: Unable to mount root fs on unknown-block (0,0) 6.5891011 CPU: 2 PID: 1 Comm: swapper/0 Not tainted 6.3.8-zen1-1-zen #1 3fdd516a5c30eb0549d707f a2967c4993d4fde4e

[ 6.589122) Hardware name: System manufacturer System Product Name/SABERTOOTH P67, BIOS 3602 11/0

1/2012

6.5891401 Call Trace:

6.589147] <TASK>

dump_stack_lul+0x47/0x60 panic+0x34a/0x350

mount_block_root+0x21f/0x2b0

prepare_namespace+0xf0/0x170

kernel_init_freeable+0x30a/0x370

6.589210] ? _pfx_kernel_init+0x10/0x10

6.589153]

[

6.589165]

[

6.589176]

[

6.589188)

[

6.589197]

[

6.5892221

[

6.589231]

[

6.589244]

[

[

kernel_init+0x1a/0x1c0

ret_from_fork+0x2c/0x50

</TASK>

6.589286] Kernel Offset: 0xe00000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000 -Oxffffffffbfffffff)

·

6.589315] ---[ end Kernel panic not syncing: UFS: Unable to mount root fs on unknown-block (0,

0) ]

Any idea what may have gone wrong with the update based on the above?


Post always your terminal in- and output as text like
~~~
garuda-inxi
System:
Kernel: 5.18.15-zen1-2-zen arch: x86_64 bits: 64 compiler: gcc v: 12.1.1
parameters:
~~~

looks like

garuda-inxi
System:
  Kernel: 5.18.15-zen1-2-zen arch: x86_64 bits: 64 compiler: gcc v: 12.1.1
    parameters:

in forum.

I have edited your post.

It seems that many things could be involved.
Please try to boot with a live ISO and then either with garuda-welcome (chroot button) or per chroot instructions refresh your system again with garuda-update in terminal. Also repair grub!

1 Like

Thank you for your help! Now that I can access the terminal, here is the garuda-inxi output:

╭─garuda@garuda in ~ as 🧙
╰─λ garuda-inxi
System:
Kernel: 6.2.13-zen-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.2.1
parameters: BOOT_IMAGE=/boot/vmlinuz-x86_64 lang=en_US keytable=us tz=UTC
misobasedir=garuda root=miso:LABEL=GARUDA_DR460NIZEDGAMING_RAPTOR quiet
systemd.show_status=1 ibt=off driver=free nouveau.modeset=1
i915.modeset=1 radeon.modeset=1
Desktop: KDE Plasma v: 5.27.4 tk: Qt v: 5.15.9 wm: kwin_x11 vt: 1 dm: SDDM
Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop Mobo: ASUSTeK model: SABERTOOTH P67 v: Rev 1.xx
serial: <superuser required> UEFI: American Megatrends v: 3602
date: 11/01/2012
CPU:
Info: model: Intel Core i5-2400 bits: 64 type: MCP arch: Sandy Bridge
gen: core 2 level: v2 built: 2010-12 process: Intel 32nm family: 6
model-id: 0x2A (42) stepping: 7 microcode: 0x2F
Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 256 KiB
desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB L3: 6 MiB
desc: 1x6 MiB
Speed (MHz): avg: 3310 high: 3375 min/max: 1600/3400 scaling:
driver: intel_cpufreq governor: performance cores: 1: 3311 2: 3375 3: 3243
4: 3311 bogomips: 24880
Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Vulnerabilities: <filter>
Graphics:
Device-1: AMD Hawaii XT / Grenada [Radeon R9 290X/390X] vendor: ASUSTeK
driver: radeon v: kernel alternate: amdgpu arch: GCN-2 code: Sea Islands
process: GF/TSMC 16-28nm built: 2013-17 pcie: gen: 2 speed: 5 GT/s
lanes: 16 link-max: gen: 3 speed: 8 GT/s ports: active: DP-1
empty: DVI-D-1,DVI-D-2,HDMI-A-1 bus-ID: 01:00.0 chip-ID: 1002:67b0
class-ID: 0300 temp: 49.0 C
Device-2: Logitech Camera (Notebooks Pro) type: USB
driver: snd-usb-audio,uvcvideo bus-ID: 1-1.8:4 chip-ID: 046d:08c3
class-ID: 0102
Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.1.1
compositor: kwin_x11 driver: X: loaded: radeon unloaded: modesetting
alternate: fbdev,vesa dri: radeonsi gpu: radeon display-ID: :0 screens: 1
Screen-1: 0 s-res: 3840x2160 s-dpi: 96 s-size: 1016x571mm (40.00x22.48")
s-diag: 1165mm (45.88")
Monitor-1: DP-1 mapped: DisplayPort-0 model: ViewSonic VP3256-4K
serial: <filter> built: 2021 res: 3840x2160 hz: 60 dpi: 140 gamma: 1.2
size: 697x392mm (27.44x15.43") diag: 800mm (31.5") ratio: 16:9 modes:
max: 3840x2160 min: 720x400
API: OpenGL v: 4.5 Mesa 23.0.3 renderer: HAWAII ( LLVM 15.0.7 DRM 2.50
6.2.13-zen-1-zen) direct-render: Yes
Audio:
Device-1: Intel 6 Series/C200 Series Family High Definition Audio
vendor: ASUSTeK driver: snd_hda_intel v: kernel bus-ID: 1-1.7.2:6
chip-ID: 05fc:0231 bus-ID: 00:1b.0 class-ID: 0300 chip-ID: 8086:1c20
serial: <filter> class-ID: 0403
Device-2: AMD Hawaii HDMI Audio [Radeon R9 290/290X / 390/390X]
vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: gen: 2 speed: 5 GT/s
lanes: 16 link-max: gen: 3 speed: 8 GT/s bus-ID: 01:00.1
chip-ID: 1002:aac8 class-ID: 0403
Device-3: Harman JBL Pebbles type: USB
driver: hid-generic,snd-usb-audio,usbhid
Device-4: Logitech Camera (Notebooks Pro) type: USB
driver: snd-usb-audio,uvcvideo bus-ID: 1-1.8:4 chip-ID: 046d:08c3
class-ID: 0102
API: ALSA v: k6.2.13-zen-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 0.3.70 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: Intel 82579V Gigabit Network vendor: ASUSTeK P8P67 Deluxe
driver: e1000e v: kernel port: f040 bus-ID: 00:19.0 chip-ID: 8086:1503
class-ID: 0200
IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
Local Storage: total: 989.45 GiB used: 0 KiB (0.0%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Crucial model: CT1000MX500SSD1
size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
type: SSD serial: <filter> rev: 043 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 type: USB vendor: PNY model: USB 3.0 FD
size: 57.94 GiB block-size: physical: 512 B logical: 512 B type: N/A
serial: <filter> rev: PMAP 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: 7.73 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 53.0 C mobo: N/A gpu: radeon temp: 49.0 C
Fan Speeds (RPM): N/A
Info:
Processes: 200 Uptime: 2m wakeups: 0 Memory: 7.73 GiB used: 2.01 GiB (26.1%)
Init: systemd v: 253 default: graphical tool: systemctl Compilers:
gcc: 12.2.1 Packages: pm: pacman pkgs: 1821 libs: 519 tools: octopi,paru
Shell: fish v: 3.6.1 default: Bash v: 5.1.16 running-in: konsole
inxi: 3.3.26
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.16-1):
System install date:     2023-06-19
Last full system update: 2023-06-19 ↻
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       <superuser required>
Failed units:

Post always your terminal in- and output as text like
~~~
garuda-inxi
System:
Kernel: 5.18.15-zen1-2-zen arch: x86_64 bits: 64 compiler: gcc v: 12.1.1
parameters:
~~~

looks like

garuda-inxi
System:
  Kernel: 5.18.15-zen1-2-zen arch: x86_64 bits: 64 compiler: gcc v: 12.1.1
    parameters:

in forum.

Should the garuda-update command be run after clicking the Chroot button on Garuda Welcome screen here:

Blockquote
==> Mounting (Garuda_Linux) [/dev/mapper/luks-728eca4c-c2b7-4415-8903-64fa4824923b]
--> mount: [/mnt]
--> mount: [/mnt/boot/efi]
[root@garuda-dr460nized-gaming /]#

Blockquote

Or do the chroot instructions need to be followed step by step first? Does repair grub! need to be done at the end if things don't work or does it need to be done regardless?
Thank you again.

Internet connection work?
I think best is to fix first the grub and then update your system with gruda-update in terminal.

:hand_with_index_finger_and_thumb_crossed:

And please, format later your posts.

1 Like

Yes. Internet connection works. What is the terminal command to repair grub and should it be run under chroot?

And please,

Got it. I'll follow the chroot instructions. Also, what am I missing regarding the format of my posts? Please advise as I'm sort of new here because my Garuda install has been running and updating without any issues whatsoever for about 1.5 years so I haven't been participating in the forum . Is there a post formatting button somewhere I'm supposed to be using on every reply?
Thanks so much.

Just use three ~ in first and last line :slight_smile: not blockquote.

Post always your terminal in- and output as text like
~~~
garuda-inxi
System:
Kernel: 5.18.15-zen1-2-zen arch: x86_64 bits: 64 compiler: gcc v: 12.1.1
parameters:
~~~

looks like

garuda-inxi
System:
  Kernel: 5.18.15-zen1-2-zen arch: x86_64 bits: 64 compiler: gcc v: 12.1.1
    parameters:

in forum.

This means that you already chrooted, with the button I guess, so there is no need to follow the instructions to chroot manually.
Now just try:

garuda-update

If not updated by the garuda-update, I'd also reinstall the kernel

pacman -S linux-zen linux-zen-headers

(when you're in chroot you're root, so sudo is not necessary)
which will also regenerate the initramfs, which seemed to be corrupted in the error message you posted.

2 Likes

Hi filo,
When the system is booted with a live ISO and I run garuda-update in the terminal it will try to update the system that's running from the USB drive correct? Is there a way to run garuda-update on the system present on the HD which got corrupted after latest update I did on Monday and that's currently not bootable?
Thank you.

That's exactly the purpose of the chroot action: you boot from a live ISO but then you ch(ange )root, and the root becomes the partition that you mounted and chrooted into. So, after chrooting, evrything you do is done on the installed system, even if it is unbootable.

4 Likes

I was able to chroot into the installed system from the live ISO. I did "garuda-update" and I also did "pacman -S linux-zen linux-zen-headers".Grub was reinstalled too with no errors reported. Restarted. Back to the original error:

Initramfs unpacking failed: ZSTD-compressed data is corrupt 6.589080) Kernel panic not syncing: VFS: Unable to mount root fs on unknown-block (0,0) 6.5891011 CPU: 2 PID: 1 Comm: swapper

Is there anything else that you know of that I could try at this point?

I really don't know, unfortunately.
My last idea would be to check if you have a file system problem tring a

sudo btrfs check /dev/sda1

and, in case of errors,

sudo btrfs check --repair /dev/sda1

changing /dev/sda1 with your root partition.

1 Like

btrfs check of the root partition results in "no error found". We may have reached the end of the road with troubleshooting? Do you think I should give up and reinstall at this point?

I notice this is the Gaming ISO on a very recently installed system. Might the problems some others have recently had even booting that ISO somehow have a bearing on this? :man_shrugging:

I wonder whether the normal d460nized ISO with the LTS kernel @dr460nf1r3 outputted might provide different results? Or even the LTS kernel, period.

2 Likes

bro try using lts kernel for me it worked