No luck… No errors but when I run the last command (configfile /boot/grub/grub.cfg, I also tried /boot/grub2/grub.cfg). The search command takes a while with no --set but finishes instantly with it. A quick LS shows that the directory did not change
Edit: I’m not allowed to make another post for 14hr because of the new user restriction, so I’m going to edit this.
Edit2: At this point is there any way to just make garuda snapshots available from opensuse’s grub and then circumvent this bug altogether?
Edit3: Or perhaps replace garuda grub with normal grub?
Edit4:
I did find the partition, it listed it just fine when I ran the command search.fs_label suse. It just wouldn’t mount with search.fs_label suse --set root. As I stated before, doing ls (hd0,msdos3) (the suse partition) gives me /@. In /@ I find /@/boot. In /boot all I find is the grub2 folder, while when I mount the drive in garuda I could see all the vmlinuz_linux files and stuff, but not in grub.
When I installed suse the second time to see if a corrupted suse was the problem it repalced garuda-grub with its own grub2. From this grub2 I was able to boot suse fine and garuda if I modified the .cfg to add /@ to the beginning of the directories. The problem occured when I did /grub-install /dev/sde in garuda to replace the suse grub with garuda grub. If all else fails I could go into my suse usb and chroot into the suse installation to run /grub-install. From there I could follow your suggestions. If nothing else works I might try this tomorrow, but I would like to nail this bug so no one else has it (I may replace suse with manjaro or pop later on so I want garuda’s grub to work properly).
If you don’t find Suse partition at grub terminal, then is probably
Your drive is like (hd0,msdos3). Try other available numbers with ls.
ls (hd0,msdos3)
ls (hd0,msdos1)
ls (hd2,msdos3)
ls (hd2,msdos1)
ls (hd2,msdos2)
to see contents.
If you manage to boot to Suse (but then we would know what was the problem and fix it), install grub and update (with os-prober enabled). Even if Garuda is not properly set, you can use /boot/grub/custom.cfg with configfile, which will use garuda grub.cfg and whatever this has (snapshots).
You can, but I doubt (or don’t know) if it succeeds with garuda grub/btrfs, which is patched.
I got tired of this, so I went ahead and chrooted into opensuse and installed grub. Garuda and OpenSuse working fine (I had to add /@ in front of the lines for garuda). I now have another question. Garuda takes qutie a while to boot, around 2 minutes to get to log in screen and then another 3-5 minutes for KDE to start. OpenSuse boots in 30 seconds with 15 seconds for KDE. Not to mention that opensuse is snappy right after boot, garuda is not for a while. Sure I installed a few programs in garuda but still opensuse is by no means a light OS, it has most of the programs that came with garuda (garuda was slow even at the start) like libreoffice, okular, etc.
Anyway back to grub.
So I copy the garuda.cfg and put it in /boot/grub/custom.cfg for opensuse?
if [ "${ENABLE_SNAPD}" = 1 ]; then
depends+=('snapd' 'snapd-glib')
define_meson+=' -Denable-snap=true'
provides+=('pamac-snap-plugin')
conflicts+=('pamac-snap-plugin')
But I have snap disabled in the settings…
Anyway I tried your solution for grub
With no luck, maybe I did something wrong but using the menu entry would just take me back to the main page (I think there was an error message, but I forgot it, so I will try it again later).
Sorry, there was no error message. I remembered wrong. Your fix didn't work either. I ran the commands in grub CLI and once again the problem was in setting the root. The search command runs just fine without --set=root but fails when I add it back in (finishes instantly, root did not change at all).
Nope, no feedback whatsoever. I just know it didn’t work properly because without --set the command took ~15-30 seconds but with --set it was basically instant.
Late to this thread - but what about putting rEFInd in the mix? Let each system generate its OWN grub, with os-prober disabled (preferably), and choose the grub you wish to boot from.
Of course, I'm just too lazy to fight with grub when it won't work right
