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?
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:
~~~
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!
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:
~~~
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.
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 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:
~~~
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.
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.
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?
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?
I wonder whether the normal d460nized ISO with the LTS kernel @dr460nf1r3 outputted might provide different results? Or even the LTS kernel, period.
we trust you 
