Grub rescue issue can't solve

Issues & Assistance Unsupported hardware | Dual boot
22

And this time be sure to setup your snapshots to perform system recoveries with.

1 Like
23

now i had to install garuda linux again ?? :smiling_face_with_tear::smiling_face_with_tear:

24

ok i will do that

25

Before reinstalling give a chance to the suggestion given by @PerfMonk

1 Like
26

@SGS said that even i fixed the boot issue maybe something else is broken

27

and i didn't understand the solution that u r taking about

28

It was simply
btrfs check --init-extent-tree

1 Like
29

Tried that also

30

So quick question
I guess i need 500 mb hidden partition right?? for bios recovery and bios stuff

31

Garuda use 260 MB its enough for 4 DE's :slight_smile:

1 Like
32

I actually don't have that partition in the first place even for windows so i have to do one or two or stay with not doing anything?

33

Another thing
After installing garuda
Windows doesn't appear in grub in booting why?

34

Try

sudo update-grub

Post output as text, please.

35

Didn't make any thing still win 10 doesn't show in grub menu

36

Post output from

efibootmgr

please.

Post also

37

Efi variables is not supported on my system

38

Didn't work sorry

39

This would help

3 Likes
40

A few hints from the Arch wiki.
According to
https://wiki.archlinux.org/title/GRUB#Detecting_other_operating_systems
you should mount the partitions from which the other systems boot before running the update-grub -> os-prober.
To be honest, this was necessary for me only for other linux distro's, never for Windows, but you can try. For a quick and dirty test, you could simply mount the windows partition opening it from the file manager (if it works, you can mount it automatically e.g. with an entry in the fstab).

https://wiki.archlinux.org/title/GRUB#Windows_installed_in_UEFI/GPT_mode
or
https://wiki.archlinux.org/title/GRUB#Windows_installed_in_BIOS/MBR_mode
Here there are some hints to do it manually in /boot/grub/grub.cfg instead of relying on update-grub.
I think this is definitely not applicable in our case, but maybe could be used in the /etc/grub.d/40_custom.

In addition to the second hint for the manual entry in /etc/grub.d/40_custom:
https://wiki.debian.org/DualBoot/Windows10
which I think is applicable if windows was installed in Legacy mode, and Garuda then in UEFI mode.

3 Likes
41

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.