Dual boot broken - Windows and Garuda

I was unable to boot directly through Garuda option in grub
So I was used to boot via snapshots
But now it's also showing the same issue

Loading Snapshot: 2021-82-28 08:01:37 timeshift  btrfs/snapshots/2021-02-28_08-81-36/@
Loading Kernel: vmlinuz-linux-tkg-bmq
error: file '/timeshift-btrfs/snapshots/2021-02-28_08-01  36/@/boot/vmlinuz-linux-tkg-bmq' not found.
Loading Microcode & Initramfs: intel-ucode.ing initramfs-linux-tkg-bm-fallback. img ...
error: you need to load the kernel first.

Press any key to continue...

I had done that. But I was facing the same issue. Even I asked in pm in forums to r3st0ck3r but he didn't replied. So I left it that way as I was busy. Now even the snapshots aren't working

If I live boot Garuda and install again on the same partition for eg sda11. Will my all files and settings in Garuda will be affected?
Can it work out this way?

Well, I would suggest reinstalling in this case.

Yeah, but you can do one thing, you can copy files to other drive in live boot.


On a rolling distro, it pays to have a bulletproof backup strategy.

If you don't have one - get one and save stress.


There is a bug in some utility that produces a wrong file path.
I suppose it's because of the different shell. It probably needs to run as designed (in Bash) properly.
@dr460nf1r3 @librewish @TNE ? grub-btrfs, or some hook needs secure wrapping or some modification for pipes?


Probably grub and os prober

They needs to patched to allow booting

Either he is running other os grub

Or he has not done

 mkinitcpio -P 

Makes me question just how many OSs/Distributions are in-play?


I received an update of os-prober in my Arch system. Maybe related?


This seems like it could possibly resemble your issue:

You could try editing the snapshot boot entry to boot to your system files directly as described in the post above.


Dual boot
Only Windows and Garuda

Use Garuda ISO to chroot to your system and run again updates, kernels and grub, using garuda-chroot

sudo pacman -Syu

If during updates there is no mkinitcpio kernels creation, do it manually

sudo mkinitcpio -P
sudo update-grub

Exit and reboot to check.


After this booting issue, the windows was also broken, I recovered it and after that when I checked Grub configuration there was no Garuda, but it showed Garuda in the menu.
Can this fix up the grub?

This is really confusing. I can't understand which is which.
Give more details and provide system info and logs.
If you have other Linux installed, boot to that and provide

inxi -Fxxxza
sudo fdisk -l
sudo parted -l
sudo os-prober

Remnants of previous distro 'tests', perhaps? We have no idea what has been done, at present.

1 Like

Before this issue I was on dual boot with Garuda and Win
I have no other Linux distro installed as of now
Downloading the latest Garuda iso

Previously 6-8 months back I was on Manjaro I had cleared all its data before installing Garuda

Had to check @EvilSeal, just to eliminate. :slightly_smiling_face:

The sda11 is what made me wonder. That's not an, um, typical arrangement unless one is booting multiples.

Next question: What is the reason you have your partitions extended that far? What does your partition table look like?

Time for answers, or then you will be alone with your problem .