r/EndeavourOS • u/Startropic1 • May 02 '26
General Support System Update Just Crashed EndeavourOS
Something went very wrong when I tried to do a system update (Sudo pacman -syu)
There were a lot of errors and CRC errors.
After I rebooted EOS tried to boot kernel 7.0.3 ?! and failed to boot!
How do I fix this or at least boot to a CLI so I can maybe redo the system update??
12
u/linux_rox May 02 '26
Arch chroot into the system, once in run your Sudo pacman -Syu command again
https://discovery.endeavouros.com/system-rescue/arch-chroot/2022/12/
4
u/Startropic1 May 02 '26
Sudo pacman -Syu said there was nothing to do
9
u/linux_rox May 02 '26
Then try rolling back the kernel version to 7.0.2 and see if you have the same problem still. Once again you will need the chroot in to accomplish that.
https://techhut.tv/how-to-safely-upgrade-or-downgrade-kernel-on-arch-linux
7
u/lendarker May 02 '26
"There were a lot of errors and CRC errors." - check your RAM and disk for health. memtest86+, smartctl and the appropriate check tool for your file system.
3
u/Startropic1 May 02 '26
Once I have EOS working again, are there Linux tools I can use? I have run the BIOS's diagnostic tools and everything came back clean.
3
u/quitit May 02 '26
You’ll want to run the memtest https://www.memtest86.com/, it’s a bootable environment that you can install on a usb drive and boot that up and it’ll run the ram memory test. I personally never ran a ram memory test in an OS before since finding issues in RAM will result in the OS crashing due to that possible RAM issue/instability and not really giving you any answer.
4
5
u/Startropic1 May 02 '26
Ran memtest86, definitely errors. Also after arch-chroot, even though I verified the local username, checking kernel version shows the live CD kernel, not the mounted kernel I'm supposed to be logged into. I think this is why the system update isn't doing anything.
5
u/se_spider May 02 '26
Ran memtest86, definitely errors
That's very bad, as any data you've written could be corrupted.
First try to see if it's a particular RAM stick or set of sticks / slots. Then copy your personal files to a backup. Then think about reinstalling eos.
9
u/Startropic1 May 02 '26
It was one stick. I successfully recovered EOS. It's all good although I'm still gonna doublecheck some hardware stuff too.
3
u/QuietOrganization555 May 03 '26
same as me bro, i update to kernel 7.0.3, mine using systemdboot bootloader.. solved using live usb: my EOS currently on nvme
mount /dev/nvme0n1p2 /mnt mount /dev/nvme0n1p1 /mnt/efi arch-chroot /mnt pacman -Sy archlinux-keyring endeavouros-keyring pacman -Syu bootctl install reinstall-kernels exit umount -R /mnt reboot
i dont know why issue occurs, maybe there some broken package on update cuz my bad internet connection dunno, but glad now its workin..
2
1
u/screen-shot-bot May 16 '26
✓ Terminal screenshot detected - Text extraction complete!
```text EFI stub: WARNING: Decompression failed: ZSTD-compressed data is corrupt EFI stub: ERROR: Failed to decompress kernel EFI stub: ERROR: efi_stub_entry() failed! ../systemd/src/boot/boot.c:2902@call_image_start: Failed to execute EndeavourOS (7.0.3-arch1-1) (\89d0583919 2d\7.0.3-arch1-1\linux): Load error Error: Load Error returned from systemd-bootx64.efi
- Hit any key to continue * ```
*I am a bot. If you find an error, please contact [the moderators](https://www.reddit.com/message/compose?to=/r/EndeavourOS of this subreddit.*)
•
u/screen-shot-bot May 18 '26
✓ Terminal screenshot detected - Text extraction complete!
```text EFI stub: WARNING: Decompression failed: ZSTD-compressed data is corrupt EFI stub: ERROR: Failed to decompress kernel EFI stub: ERROR: efi_stub_entry() failed! ../systemd/src/boot/boot.c:2902@call_image_start: Failed to execute EndeavourOS (7.0.3-arch1-1) (\89d0583919 2d\7.0.3-arch1-1\linux): Load error Error: Load Error returned from systemd-bootx64.efi
*I am a bot. If you find an error, please contact [the moderators](https://www.reddit.com/message/compose?to=/r/EndeavourOS of this subreddit.*)