Boot stuck on linux-zen

[waduhektemp]

A few days ago my pc has been unable to boot to OS. Its currently getting stuck on

Loading Linux linux-zen
Loading initial ramdisk

Yesterday i was able to get into the OS by using a snapshot but that has sinse stopped working. Now im getting the following error when clicking on a snapshot. (below)

Error: file '/@/boot/intel-ucode.img^/@/boot/initramfs-linux-zen.img' not found. (hopefully no typos as i had to type this myself)

Does anyone have any ideas on how i can fix this? if anyone has any ideas please let me know. Warning i am still new to Linux i switched over about 2 months ago.

Also if this means anything im duel booting windows 10 and it works perfectly fine.

[filo]

Hi there, welcome.
This is the reference tutorial in this case.
Most likely you can start directory with the chroot from live USB andupdate.

Computer doesn’t boot, boots to a black screen, or stops at a message

While there are many potential reasons why your installation doesn’t boot to a desktop, the primary reason is that the graphics drivers haven’t loaded correctly so your login/display manager (DM) doesn’t start. This is why you get a “black screen” or stuck at an [ OK ] Started some service message. The normal reason for this is that you have the incorrect driver version for the kernel. This can happens when the mirror you are updating from is not fully synchronised, or times out, and so y…

[tbg]

Windows may have messed up your boot.

Try:

Grub fails after update

chroot steps in garuda linux from live garuda usb sudo mkdir /mnt sudo mount /dev/sdxy /mnt sudo garuda-chroot /mnt/@ now you should be chrooted in garuda if the system is installed in legacy bios then do the following in the chroot grub-install /dev/sda if its installed on efi first mount the efi partition ie fat32 partition from inside the chroot mount /dev/sdxy /boot/efi then grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=garuda --recheck then updat…

or:

How to chroot Garuda Linux

From Grub fails after update - #3 by librewish Some unlucky times that your system is not bootable and the only advised option is to use chroot from a Live ISO to repair the installed system (for example, to (re)install the bootloader), here is the suggested method: steps required to chroot to your installed Garuda installation (btrfs) Boot to a Garuda usb Live ISO Start a terminal and Find your installed system (btrfs) partition, you need the /dev/<something> part. lsblk -f Warning: Remem…

or:

The easier way to chroot is to boot into a Garuda live USB and do a grub repair from within Garuda Assistant. Then run grub-update.

---

---

You may also want to reinstall the Zen kernel from the chroot:

pacman -Syu linux-zen linux-zen-headers

[waduhektemp]

when attempting sudo media/mnt I get File exists. Should I overwrite that? If so how should I do that?

When trying number 2 i get
sudogrub-probe: error cannot find grub device for /dev/sdc1. check your device.map

[filo]

Since you're doing this from the live USB, with connectivity, it would be great if you could paste here the full input / output, to get the complete picture.

[waduhektemp]

When opening Chroot i get this error PrivateBin

at the bottom is when i type the following

sudo mkdir /mnt
sudo mount /dev/sdxy /mnt
sudo garuda-chroot /mnt/@

for - How to chroot Garuda Linux

One issue im having is im not sure how to find the device that holds MBR

[filo]

Instead of using the chroot button, which is probably generating that error, try to follow carefully the tutorial "how to chroot garuda linux".
Boot from the live USB and open a terminal (do not use the chroot button).
sudo mkdir /mnt/broken
Otherwise /mnt alone already exists.
Do not use /dev/sdxy, that's only an example.
Check your disk with lsblk -f as instructed in the guide to identify the system partition to mount.
There are also indications to verify if your system is in UEFI or legacy mode.

Edit: looking more carefully into your privatebin, I think the chroot actually worked! You didn't need the additional commands to do it manually.
See that you were root # in your installed system partition /dev/nvme1n1p2
Do that again and proceed with the suggestions in the previous posts.

[waduhektemp]

Sorry for the late reply but sadly this did not work. At this point im thinking about resetting my PC. Just one question if you don't mind, is their a way to gain access to the root folder so i can transfer the contents to another drive?

[BluishHumility]

@waduhektemp

is their a way to gain access to the root folder so i can transfer the contents to another drive?

Chroot provides this access. It changes the root the shell is working in to the device you specified. Once here, you should be able to access any part of the system you like.

[waduhektemp]

I did get an error when attempting pacman -Syu reinstall grub-efi-amd64 I have an intel cpu so i also changed it to intel64 but no change.

PrivateBin

Im going back and retrying the very first solution posted here sudo reflector -a6 -f5 --save /etc/pacman.d/mirrorlist im getting a repeating error PrivateBin

as well as sudo dkms autoinstall I don't remember if i got this the first time i tried

PrivateBin

[filo]

@waduhektemp

pacman -Syu reinstall grub-efi-amd64

Where did you get this? This is wrong.
Once again, try to stick to the tutorial. It worked for so many people…

Select the proper $esp partition (you may check your /etc/fstab if you are not sure) and mount it inside chroot

mount /dev/nvme0n1p4 /boot/efi

Then install grub bootloader and update grub

grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=garuda --recheck
update-grub

Do not forget to exit chroot normally, before you close the terminal

Exit the chroot session

[waduhektemp]

I tried doing this yesterday but it did not solve the issue. I redid it today so i could grab the logs.

PrivateBin

[filo]

OK. So the grub installation and update-grub were succesful.
I guess you tried to reboot and got the same error?

Installing for x86_64-efi platform.
Installation finished. No error reported.
Generating grub configuration file …
Found theme: /usr/share/grub/themes/garuda-dr460nized/theme.txt
Found linux image: /boot/vmlinuz-linux-zen
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux-zen.img
Found fallback initrd image(s) in /boot: intel-ucode.img initramfs-linux-zen-fallback.img
Found linux image: /boot/vmlinuz-linux
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux.img
Found fallback initrd image(s) in /boot: intel-ucode.img initramfs-linux-fallback.img
…

I’ve also put in bold the files which were not found.
Don’t care about this. It is related to the USB drive itself…

grub-probe: error: cannot find a GRUB drive for /dev/sdc1. Check your device.map.

Now you could try chrooting again and

pacman -Syu linux-zen linux-zen-headers

[filo]

If the suggestion above still does not work, I have another idea.
Your error message is:

Error: file ‘/@/boot/intel-ucode.img^/@/boot/initramfs-linux-zen.img’ not found

While in the update-grub output I can see:

Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux-zen.img

You see, there is a ^ instead of a space.
I’ve found something similar here:

Grub-mkconfig generates wrong lines for other linux os

Hi everyone inxi -Faz System: Kernel: 5.15.12-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0 parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=6f58aafa-9f36-4ae5-940b-ca0f2c54cd24 rw rootflags=subvol=@ splash rd.udev.log_priority=3 vt.global_cursor_default=0 systemd.unified_cgroup_hierarchy=1 loglevel=3 Desktop: KDE Plasma 5.23.4 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux Machine: Type: Desktop System: HP product: HP Z4…

Maybe, you could

sudo micro /boot/grub/grub.cfg

search that string and replace the ^ with a space.
If it works, this could be overwritten by the next update-grub, but we’ll see that later…
The solution should be the one in the link above:

sudo micro /etc/grub.d/30_os-prober 

replace in line 213

LINITRD="`echo ${LINUX} | cut -d ':' -f 5`"

with

LINITRD="`echo ${LINUX} | cut -d ':' -f 5 | tr '^' ' '`"

and finally

sudo update-grub

[tbg]

From your log:

Error! Your kernel headers for kernel 5.15.5-zen1-1-zen cannot be found at /usr/lib/modules/5.15.5-zen1-1-zen/build or /usr/lib/modules/5.15.5-zen1-1-zen/source.
Please install the linux-headers-5.15.5-zen1-1-zen package or use the --kernelsourcedir option to tell DKMS where it’s located.

@tbg

You may also want to reinstall the Zen kernel from the chroot:

pacman -Syu linux-zen linux-zen-headers

Reinstall zen kernel &headers.

[waduhektemp]

this is the output from
pacman -Syu linux-zen linux-zen-headers

PrivateBin

trying the rest rn

[tbg]

@waduhektemp

this is the output from
pacman -Syu linux-zen linux-zen-headers

Encrypted, requires password^^^

[waduhektemp]

@filo

ucode.img^

I don’t believe i put one, Well i have zero clue what the password is

Ill post an updated one in a few minutes

[waduhektemp]

Grub.cfg doesnt have intel-ucode.img^. I replace the text in in 213 then tried updating.

I cant seem to find a way of copying the grub.cfg

[filo]

I don't see anything wrong in the linux-zen and headers installation.
There are some errors for the snapshot part, but I think that's normal in the chroot.
I'd reconsider the other solution above on the ^ problem...
A PrivateBin more could be for /boot/grub/grub.cfg