Remember when I showed you the kernel files we needed? That is in @/boot. The structure in Garuda is as follows:
/media/myviolinsings/406d8c92-eb3f-4642-8532-fe14c97261cd/@
/media/myviolinsings/406d8c92-eb3f-4642-8532-fe14c97261cd/@cache
/media/myviolinsings/406d8c92-eb3f-4642-8532-fe14c97261cd/@home
/media/myviolinsings/406d8c92-eb3f-4642-8532-fe14c97261cd/@log
/media/myviolinsings/406d8c92-eb3f-4642-8532-fe14c97261cd/@root
/media/myviolinsings/406d8c92-eb3f-4642-8532-fe14c97261cd/@srv
/media/myviolinsings/406d8c92-eb3f-4642-8532-fe14c97261cd/@tmp
the “@” has several files/folders:
\/media/myviolinsings/406d8c92-eb3f-4642-8532-fe14c97261cd/@/.snapshots
/media/myviolinsings/406d8c92-eb3f-4642-8532-fe14c97261cd/@/bin
/media/myviolinsings/406d8c92-eb3f-4642-8532-fe14c97261cd/@/boot
/media/myviolinsings/406d8c92-eb3f-4642-8532-fe14c97261cd/@/dev
/media/myviolinsings/406d8c92-eb3f-4642-8532-fe14c97261cd/@/etc
/media/myviolinsings/406d8c92-eb3f-4642-8532-fe14c97261cd/@/home
/media/myviolinsings/406d8c92-eb3f-4642-8532-fe14c97261cd/@/lib
/media/myviolinsings/406d8c92-eb3f-4642-8532-fe14c97261cd/@/lib64
/media/myviolinsings/406d8c92-eb3f-4642-8532-fe14c97261cd/@/media
/media/myviolinsings/406d8c92-eb3f-4642-8532-fe14c97261cd/@/mnt
/media/myviolinsings/406d8c92-eb3f-4642-8532-fe14c97261cd/@/opt
/media/myviolinsings/406d8c92-eb3f-4642-8532-fe14c97261cd/@/proc
/media/myviolinsings/406d8c92-eb3f-4642-8532-fe14c97261cd/@/root
/media/myviolinsings/406d8c92-eb3f-4642-8532-fe14c97261cd/@/run
/media/myviolinsings/406d8c92-eb3f-4642-8532-fe14c97261cd/@/sbin
/media/myviolinsings/406d8c92-eb3f-4642-8532-fe14c97261cd/@/srv
/media/myviolinsings/406d8c92-eb3f-4642-8532-fe14c97261cd/@/sys
/media/myviolinsings/406d8c92-eb3f-4642-8532-fe14c97261cd/@/tmp
/media/myviolinsings/406d8c92-eb3f-4642-8532-fe14c97261cd/@/usr
/media/myviolinsings/406d8c92-eb3f-4642-8532-fe14c97261cd/@/var
/media/myviolinsings/406d8c92-eb3f-4642-8532-fe14c97261cd/@/.garuda-tools
And the /boot folder has:
/media/myviolinsings/406d8c92-eb3f-4642-8532-fe14c97261cd/@/boot/efi
/media/myviolinsings/406d8c92-eb3f-4642-8532-fe14c97261cd/@/boot/grub
/media/myviolinsings/406d8c92-eb3f-4642-8532-fe14c97261cd/@/boot/memtest86+
/media/myviolinsings/406d8c92-eb3f-4642-8532-fe14c97261cd/@/boot/initramfs-linux-zen.img
/media/myviolinsings/406d8c92-eb3f-4642-8532-fe14c97261cd/@/boot/initramfs-linux-zen-fallback.img
/media/myviolinsings/406d8c92-eb3f-4642-8532-fe14c97261cd/@/boot/intel-ucode.img
/media/myviolinsings/406d8c92-eb3f-4642-8532-fe14c97261cd/@/boot/vmlinuz-linux-zen
So I assume the subvolumes these instructions refer to (the ones os-prober cannot find by such locations/names) are what we need to point to.
One forum the person had MX installed and added OpenSUSE (btrfs) and this was stated:
OK, so it seems that the solution layed out in https://askubuntu.com/questions/967172/grub2-does-not-detect-btrfs-partition/1032354#1032354 also works if "your currently booted OS" is NOT btrfs (but ext4 in my case).
Just do the following:
- mount the btrfs volume locally (eg in Dolphin, click on the respective partition)
- navigate to the mountpoint
- do
Code: Select all
sudo ln -s @/boot boot
sudo ln -s @/etc etc
And further explanation:
How to enable os-prober to detect btrfs installs with "/"-root on subvolumes...
For BTRFS installtions, where system root "/" files system is located on a btrfs-subvolume,
GRUB through update-grub ( => grub-mkconfig ) does have difficulties to generate
a GRUB menu entry for those other installations found on another partition.
update-grub is using os-prober. And os-prober does not have an indication
what subvolume "/"-root filesystem is located on.
In order to "help" os-prober to detect the GRUB-installtion on such btrfs-install
with subvolumes, some symlinks needs to be added to the "top id=5" subvolume.
The person decided to just go with chainloading as he did not want to run the script the helper created for him.
I am still not sure I understand where these symlinks are to be created, and if I can create them while I have MX booted.
Thanks,
Sheila