Like librewish wrote.
"you seems to have installed multiple systems in both uefi and bios mode
so either reinstall all in uefi or in legacy bios"
Install garuda in uefi.
1 Like
ok. i will do that when even manjaro's grub doesnt boot into garuda. for now ill let it be how it is.
1 Like
What is the difference between then and now? What changes have you made to your system?
(Things don't just "stop working" for no reason.)
2 Likes
It happened maybe after a grub or kernel upgrade. Definitely happened after a big update.
We should checkout whether this is a bug in packaging or other.
Please provide more info, booted your Garuda:
findmnt --real -A
grep "/" /etc/fstab
lsblk -f
grep -E "grub|btrfs| filesystem " /var/log/pacman.log | tail
pacman -Qs "grub|btrfs" | grep ^local
pacman -Q filesystem
3 Likes
findmnt --real -A ─╯
TARGET SOURCE FSTYPE OPTIONS
/ /dev/nvme0n1p5 ext4 rw,noatime
├─/run/user/1000/doc portal fuse.port rw,nosuid,nodev,relatime,user_id=1000,group_id=1000
├─/run/media/pupperemeritus/Seagate Expansion Drive
│ /dev/sdb1 fuseblk rw,nosuid,nodev,relatime,user_id=0,group_id=0,defau
├─/snap/core18/1932 /dev/loop1 squashfs ro,nodev,relatime
├─/snap/orchis-themes/1 /dev/loop2 squashfs ro,nodev,relatime
├─/snap/snapd/9721 /dev/loop0 squashfs ro,nodev,relatime
└─/snap/core20/634 /dev/loop3 squashfs ro,nodev,relatime
/etc/fstab: static file system information.
UUID=4f6fdcfa-53f2-4eaa-b404-0bd0bfa378cb / ext4 defaults,noatime 0 1
AME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINT
loop0 squash 4.0 0 100% /snap/snap
loop1 squash 4.0 0 100% /snap/core
loop2 squash 4.0 0 100% /snap/orch
loop3 squash 4.0 0 100% /snap/core
sda
├─sda1
│ ntfs 8C4A26974A267DD8
├─sda2
│ vfat FAT32 5C3E-EB55
├─sda3
│
├─sda4
│ ntfs 90A04131A0411EDA
├─sda5
│ ntfs Games 3E8A82A78A825AF3
├─sda6
│ ntfs Media 88A4A1CEA4A1BF56
└─sda7
ntfs Games 2 2E3AA7313AA6F54D
sdb
└─sdb1
ntfs Seagate Expansion Drive
B674C4EA74C4AF05 303.9G 84% /run/media
zram0 [SWAP]
zram1 [SWAP]
zram2 [SWAP]
zram3 [SWAP]
zram4 [SWAP]
zram5 [SWAP]
zram6 [SWAP]
zram7 [SWAP]
zram8 [SWAP]
zram9 [SWAP]
zram10
[SWAP]
zram11
[SWAP]
nvme0n1
│
├─nvme0n1p1
│
├─nvme0n1p2
│ ntfs New Volume 3A60BA9F60BA6175
├─nvme0n1p3
│ ext4 1.0 8f19169f-5841-4226-8eba-328ba3b01b83
├─nvme0n1p4
│ swap 1 ca128974-163e-48d5-869a-fde2f887a0bd [SWAP]
└─nvme0n1p5
ext4 1.0 4f6fdcfa-53f2-4eaa-b404-0bd0bfa378cb 87.4G 47% /
2020-11-24T11:56:02+0530] [ALPM-SCRIPTLET] If you think an error has occurred , please file a bug report at " https://github.com/Antynea/grub-btrfs "
[2020-11-24T11:56:03+0530] [ALPM-SCRIPTLET] /usr/bin/grub-probe: warning: unknown device type nvme0n1.
[2020-11-24T11:56:04+0530] [ALPM-SCRIPTLET] /etc/default/grub-btrfs/config.pacnew
[2020-11-24T11:56:49+0530] [ALPM-SCRIPTLET] /etc/default/grub-btrfs/config.pacnew
[2020-11-24T13:30:13+0530] [ALPM-SCRIPTLET] Generating grub configuration file ...
[2020-11-24T13:30:31+0530] [ALPM-SCRIPTLET] Root partition isn't a btrfs filesystem.
[2020-11-24T13:30:31+0530] [ALPM-SCRIPTLET] This script only supports snapshots of the btrfs filesystem.
[2020-11-24T13:30:31+0530] [ALPM-SCRIPTLET] If you think an error has occurred , please file a bug report at " https://github.com/Antynea/grub-btrfs "
[2020-11-24T13:30:31+0530] [ALPM-SCRIPTLET] /usr/bin/grub-probe: warning: unknown device type nvme0n1.
[2020-11-24T13:30:33+0530] [ALPM-SCRIPTLET] /etc/default/grub-btrfs/config.pacnew
local/btrfs-progs 5.9-1
local/garuda-boot-repair-git r19.582fff3-1 (garuda-git)
local/grub 2:2.04-8
local/grub-btrfs 4.7.1-1
local/grub-garuda 2.04-11
local/grub-theme-garuda r16.2df2516-1
local/python-markdown 3.3.3-1
local/update-grub 0.0.1-7
filesystem 2020.09.03-1
It seems you have not a btrfs partition scheme. Can Garuda tools do this? If so, I am amazed, although ... it fails 
Have you done a custom installation of Garuda? How?
If you had installed normally with Garuda ISO, I have to ask Garuda devs to checkout this case.
Maybe some issue with btrfs?
Anyway, post
cat /etc/fstab
2 Likes
Ha ha, you don't miss a thing @petsam . Nice to have you helping out again my friend.
This would appear to be one of those cases where "you broke it, you bought it" applies.
2 Likes
Just as a side note - one of my Garuda setups is running on ext4 - and was installed that way from the then current Garuda ISO. My current one is btrfs - and I fixed the propblem that caused me to switch to ext4 by instead disabling grub's os-prober...
i wasnt able to install bootloader when installing using btrfs. weird as it is but yeah. i had to change to ext4
UUID=4f6fdcfa-53f2-4eaa-b404-0bd0bfa378cb / ext4 defaults,noatime 0 1
UUID=ca128974-163e-48d5-869a-fde2f887a0bd swap swap defaults,noatime 0 0
You have done several system changes, though you don't explain from start which ones. It is very time consuming asking every possible change you might have done, one by one.
A swift guess would be you have to find out where is your $esp (efi) partition, mount it, install grub and, if it succeeds, add that partition to fstab.
There is one FAT (vfat) partition at /dev/sda2, but also an invisible partition at /dev/nvme0n1p1, which maybe an $esp.
Since you have decided to not use btrfs, I would suggest you uninstall grub-btrfs.
Nevertheless, your issue maybe totally unrelated, as there are messages about failed to discover nvme0n1 (grub-probe: warning: unknown device type nvme0n1.), which could also be just cosmetic.
So, you have to do some investigation and testing.
3 Likes
i reinstalled grub and regenerated the config file. reckon itll work now.
1 Like
Are your issues on different installations? One is btrfs and one ext4?
I am confused...
2 Likes
different installation.
1 Like
this thread is for my personal PC with ext4. one is my friend's PC. another my dad's pc.
1 Like
I think for clarities sake you should refrain from posting about ext4 boot issues in the future. The Devs have made it pretty clear that this is unsupported and you're on your own if you want to make major configuration changes such as this.
@petsam is one of the best and most experienced troubleshooters I've encountered on any Linux forum. If you've confused him, imagine how confused a complete Linux newbie would be trying to find help from old posts on the forum.
You have deviated from the install method on all the Garuda editions. Posts such as this are just about as helpful on our forum as posts from Linux users that are using Ubuntu. These types of posts only serve to confuse and bewilder newcomers trying to fix boot issues with newbies.
I am considering locking (or deleting) threads in the future that are about ext4 installation related boot issues. I will have to discuss this with other moderators because this is a total waste of forum support resources and only leads to confusion when searching boot issues.
Booting ext4 while possible with Garuda is unsupported. The Devs have made that crystal clear with posts related to installing on ext4 in the past.
Garuda runs btrfs and a modified grub to allow restoration of a broken system with timeshift from the grub boot menu. This is the main foundation of all editions of the distro. When you start cutting away at your foundation things tend to start crumbling and falling apart if you're not a very skilled craftsman.
4 Likes
OK, I admit I exaggerated a little bit
I liked that you were so polite in moderation. We have to switch roles in this forum.
Me bad cop, you good cop. 
4 Likes
You're not bad at all, but I notice with many native Greek speakers that online translators often have a hard time translating Greek to English.
I guess that's why English speakers say it's all Greek to me, when they're having a hard time understanding a Linux manpage. 
5 Likes
Ok. Cool. I'll not post issues pertaining to ext4. Only non file system related issues.
1 Like
That would be greatly appreciated, as we're trying to keep the advice consistent for the boot related issues on the forum.
Thanks for understanding. 
3 Likes