Installing for i386-pc platform.
grub-install: warning: File system `fat' doesn't support embedding.
grub-install: error: filesystem `btrfs' doesn't support blocklists.
Could you plz post the command line you issued right above this:
You say you tried to reinstall GRUB but you don’t mention what command you issued.
I see GRUB is trying to install i386 platform (BIOS LEGACY support) but your inxi says your partition table is GPT, therefore you should install x64efi GRUB, not i386.
My other question would be “Are you dual-booting Windows?”
Yes i actually dual booted it but it was running fine before. I actually was doing a separate garuda install on a external SSD for a separate use case but i had not paid attention to the install option and it messed my efi on my device. After removing the external i booted into my normal install and it keeps me throwing into windows. I went to bios to check and i now see that on the UEFI option for OS manager Garuda is gone. I went to Windows to check efi but now i only see a grubx64.efi present instead of the Garuda folder inside the EFI folder. I restarted to boot from efi file and i can actually use grub to come into linux and it works but my menu is gone from UEFI OS boot manager so what should i do?
Ok hang on I have stuff for this I've being doing it at least 25 times in the last 2 month. Let me check my notes for the exact steps... I'll be back, he said.
Ok so the bellow steps will reinstall GRUB and recreate the OS boot option in UEFI.
A few caveats though:
I am NEVER tried while dual-booting Windows. I've read it should work but I cannot confirm this 100%.
You might need to adjust a few parms in the steps to match your configuration, I can help nailing them down but I'm not familiar reading INXI and am not fully confident I will have it right.
To reinstall GRUB UEFI and re-instate the Garuda Boot Option in boot menu:
Boot into the Garuda Live ISO and open a Terminal to issue:
sudo mount /dev/nvme0n1p5 /mnt
sudo mount --rbind /dev /mnt/@/dev
sudo mount --rbind /proc /mnt/@/proc
sudo mount --rbind /sys /mnt/@/sys
sudo chroot /mnt/@
mount /dev/nvme0n1p5 /
mount /dev/nvme0n1p2 /boot/efi (X = EFI partition)
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id="Garuda"
umount /boot/efi
umount /
exit
exit
What these commands do is mount your Garuda root in order to bind DEV-SYS-PROC which allow reinstalling GRUB. It then mounts your EFI partition which allows GRUB to redirect it's installation files and Boot Menu configuration into.
It also specifies the LABEL you want to see in UEFI Menu, frankly you can put whatever you want there (bootloader-id).
It also tags your Garuda as the FIRST boot option to boot into. This is by design when installing GRUB UEFI.
Now I need help identifying your actual Garuda Root disk partition number and your EFI partition number, I will re-read your INXI in case I find something obvious to me....
Ok, so your disk is /dev/nvme0n1
Your EFI partition is /dev/nvme0n1p2
Where is your Garuda installed? /dev/nvme0n1p1?
I never trusted doing it in the same OS I was booted into. That doesn't mean it won't work, it just mean I never wanted to try it in case it would break, so I cannot answer that question. My understanding is when the EFI partition is mounted it's sort of hidden so I never wanted to play with that.
partha@partha in ~
λ grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=garuda
Installing for x86_64-efi platform.
grub-install: warning: disk does not exist, so falling back to partition device /dev/nvme0n1p2.
grub-install: warning: disk does not exist, so falling back to partition device /dev/nvme0n1p2.
grub-install: warning: disk does not exist, so falling back to partition device /dev/nvme0n1p2.
grub-install: error: disk `hostdisk//dev/nvme0n1p2' not found.