GRUB can't find the updated Mageia kernels.

[Sabungayam]

Here's are the conditions. I am NOT on that machine now so can't provide anything from it at the moment.

I have tried searching GRUB and have not found this situation so I apologize if I am still somehow making a copy of a post that has been made.

The machine has a DUAL BOOT of Mageia and another Linux distro. Normally, I would honestly use Mageia's GRUB because of the Control center making it pretty easy to make changes if you need to. I never have.

However this ARCH based distro uses BTRFS and has this back up thing setup. I was NOT sure if they way they set it that Mageia grub would find those if they were needed. Also, this is NOT my classic preplanned
dual boot. In such instance I would have installed Mageia first then installed the other 2nd. I just saw I had so much space left over and that other install is really for something specific that is difficult to setup in Mageia
and already setup out the box. (If you want to know, they are 1. ANBOX, 2. Winetricks and the Steam thing that I forget the name of that uses Winetricks.)

Otherwise I much prefer Mageia as my daily driver and it's just much more comfortable use for desktop. Anyway, I put Mageia on and since it was 2nd, I told it to install grub to the partition.

Well no problem initially. The other system grub saw it and booted it even with the really annoying parameters needed for the SCREEN on this BEAST of a unit. (Not on it now)

Then, update. New Kernel. With each successive new Kernel in Mageia updated I am getting a message that the link is invalid and that no such kernel etc exists?

As an example. Kernel 5.10.75 was installed and gave that message. I backtracked to Kernel 5.10.70 and it worked. Then there was a recent update which I have not done here yet. Probably should do that now.

The next kernel was installed and then... I can't use 5.10.70. Of course can't use 5.10.75. I am now using 5.10.62. SO it looks like the NEXT update will bump me down to the first kernel when I installed and after that. I won't have a bootable system.

Now to note and this may have something to do with that Grub, I have read somewhere I think, that there is now a special GRUB for BTRFS? I am absolutely unable to add grub options to Grub 41. Well, I can add them.

They do not work. In adding them I even used UUID to point to where Mageia is and though that failed. I was able to see that the GRUB OS detect used the exact same line and parameters to find and boot Mageia grub.

Once again the issue here seems that thought the kernels are installed Mageia grub keeps saying that that UUID location is incorrect?

Does anyone with more knowledge on this matter have any suggestions? More about how to get GRUB to find the Kernels or to just TELL GRUB where they are.

This is an EFI machine. Once again. Mageia GRUB is on the partition NOT in EFI.

Thank you in advance. If you need any logs or anything.

Please tell me and I'll be happy to provide. Please LEAVE DETAILED instructions on what I need to do to get you what you need to see.

Thank you.

[benmc]

can you give the output of, as root, from your Mageia:

Code: Select all

# update-grub2

and also the equivalent from your other system

this will determine if Mageia is detecting the installed kernels and making the required grub entries.
It will also show if the other grub is detecting the Mageia grub configuration file.

[sturmvogel]

I have a similar situation with a dualboot machine (if i understand your description right). The Mageia Grub is on the first SSD and the Tumbleweed Grub is on the second SSD. I'm using the Tumbleweed Grub to boot into Mageia (because the Mageia Grub is not working properly on this machine). Every time a new Kernel in Mageia is installed the Tumbleweed Grub doesn't point to the newest one. Thats why i have to update the Tumbleweed Grub. Either the way benmc is mentioning, or a little more complicated: Uncheck the box "Probe for other OS". Save. Check the box "Probe for other OS" again. Save. (In my case in Tumbleweed Grub, in your case in your other distros Grub). Everything works fine after that.

[Sabungayam]

Thanks for the replies. I am pretty certain but I will do as suggested, don't worry, that the ARCH GRUB is detecting Mageia. I boot from it and recall that kernel 5.10.70 was booting. Then update to Kernel 5.10.78 broke that and that 5.10.75 was also not booting. When 5.10.70 was booting fine as the highest kernel. At that point an update added 5.10.75. I just reverted to 5.10.70. So the other grub was detecting Magiea and booting it.

I will get the output from that grubs command and I will see what update grub output is in Mageia. I didn't try that. I of course always go into the other system and update it's Grub after Mageia adds a kernel. As stated I usually use Mageia as my daily driver. Much better experience on that machine.

To the other reply. Yes, similar setup as yours but not Tumbleweed. It is Arch based Garuda Linux. This is indeed Mageia I'm in now, but I won't get to that machine for a couple hours as I'm at work.

I'll post that info from them both when I get to it.

[Sabungayam]

I have a similar situation with a dualboot machine (if i understand your description right). The Mageia Grub is on the first SSD and the Tumbleweed Grub is on the second SSD. I'm using the Tumbleweed Grub to boot into Mageia (because the Mageia Grub is not working properly on this machine). Every time a new Kernel in Mageia is installed the Tumbleweed Grub doesn't point to the newest one. Thats why i have to update the Tumbleweed Grub. Either the way benmc is mentioning, or a little more complicated: Uncheck the box "Probe for other OS". Save. Check the box "Probe for other OS" again. Save. (In my case in Tumbleweed Grub, in your case in your other distros Grub). Everything works fine after that.

Yes, I did forget that SuSE uses BTRFS too. DO you know if that is a special GRUB 2 for BTRFS? I read that somewhere. I will also check out your instructions. Sounds interesting. I did 'try' somewhat what you suggested.
I went into Mageia. I then updated then went back into Garuda. Then updated Garuda Grub but had not turned off the OS probe. Let's see if that works. If you've ever messed with ARCH, you know usually the only way to do things there is command line. So usually it's the 'update grub' command. Garuda does have a GUI that will do it too sorta.

WIll post back findings later in a few hours. Thanks for the suggestions.

[Sabungayam]

This is the output here in Mageia

Code: Select all

update-grub2
Generating grub configuration file ...
Found theme: /boot/grub2/themes/maggy/theme.txt
Found linux image: /boot/vmlinuz-5.10.78-desktop-1.mga8
Found initrd image: /boot/initrd-5.10.78-desktop-1.mga8.img
Found linux image: /boot/vmlinuz-5.10.75-desktop-1.mga8
Found initrd image: /boot/initrd-5.10.75-desktop-1.mga8.img
Found linux image: /boot/vmlinuz-5.10.70-desktop-1.mga8
Found initrd image: /boot/initrd-5.10.70-desktop-1.mga8.img
Found linux image: /boot/vmlinuz-5.10.62-desktop-1.mga8
Found initrd image: /boot/initrd-5.10.62-desktop-1.mga8.img
Found linux image: /boot/vmlinuz-5.10.16-desktop-1.mga8
Found initrd image: /boot/initrd-5.10.16-desktop-1.mga8.img
Found linux image: /boot/vmlinuz-desktop
Found initrd image: /boot/initrd-desktop.img
Found Windows Boot Manager on /dev/nvme0n1p1@/EFI/Microsoft/Boot/bootmgfw.efi
Found Garuda Linux on /dev/sda2
Adding boot menu entry for UEFI Firmware Settings ...
done


[sturmvogel]

If you do the same command on your Garuda Linux, than it should be possible to chose in your EFI BIOS which Bootloader to use first (EFI Boot Order).

[Sabungayam]

Garuda output

Code: Select all

update-grub
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/garuda-dr460nized/theme.txt
Found linux image: /boot/vmlinuz-linux-zen
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux-zen.img
Found fallback initrd image(s) in /boot:  intel-ucode.img initramfs-linux-zen-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Found Windows Boot Manager on /dev/nvme0n1p1@/efi/Microsoft/Boot/bootmgfw.efi
Found Garuda Linux on /dev/sda2
Found Mageia 8 (8) on /dev/sda3
Adding boot menu entry for UEFI Firmware Settings ...
Detecting snapshots ...
Info: Separate boot partition not detected
Found snapshot: 2021-11-20 15:52:56 | timeshift-btrfs/snapshots/2021-11-20_15-52-56/@
Found snapshot: 2021-11-20 12:59:50 | timeshift-btrfs/snapshots/2021-11-20_12-59-49/@
Found snapshot: 2021-11-14 01:19:27 | timeshift-btrfs/snapshots/2021-11-14_01-19-26/@
Found snapshot: 2021-11-02 19:13:38 | timeshift-btrfs/snapshots/2021-11-02_19-13-38/@
Found snapshot: 2021-11-02 19:03:32 | timeshift-btrfs/snapshots/2021-11-02_19-03-31/@
Found 5 snapshot(s)
Unmount /tmp/grub-btrfs.dl8w4BfWWS .. Success
Found memtest86+ image: /boot/memtest86+/memtest.bin
done

However in Garuda's Grub.config:

Code: Select all

menuentry 'Mageia 8 (8) (on /dev/sda3)' --class mageia --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-1e9b30cb-b17c-4508-b15d-81ae3721a228' {
   insmod part_gpt
   insmod ext2
   set root='hd0,gpt3'
   if [ x$feature_platform_search_hint = xy ]; then
     search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3  1e9b30cb-b17c-4508-b15d-81ae3721a228
   else
     search --no-floppy --fs-uuid --set=root 1e9b30cb-b17c-4508-b15d-81ae3721a228
   fi
   linux /boot/vmlinuz-5.10.78-desktop-1.mga8 root=UUID=1e9b30cb-b17c-4508-b15d-81ae3721a228 ro splash quiet noiswmd resume=UUID=0ca0caec-3b79-4aa5-9096-09054eef76cd audit=0 video=eDP-1:800x1280 drm.edid_firmware=eDP-1:edid/gpdwinmax.bin fbcon=rotate:1 vga=791
   initrd /boot/initrd-5.10.78-desktop-1.mga8.img
}
submenu 'Advanced options for Mageia 8 (8) (on /dev/sda3)' $menuentry_id_option 'osprober-gnulinux-advanced-1e9b30cb-b17c-4508-b15d-81ae3721a228' {
   menuentry 'Mageia (on /dev/sda3)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-5.10.78-desktop-1.mga8--1e9b30cb-b17c-4508-b15d-81ae3721a228' {
      insmod part_gpt
      insmod ext2
      set root='hd0,gpt3'
      if [ x$feature_platform_search_hint = xy ]; then
        search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3  1e9b30cb-b17c-4508-b15d-81ae3721a228
      else
        search --no-floppy --fs-uuid --set=root 1e9b30cb-b17c-4508-b15d-81ae3721a228
      fi
      linux /boot/vmlinuz-5.10.78-desktop-1.mga8 root=UUID=1e9b30cb-b17c-4508-b15d-81ae3721a228 ro splash quiet noiswmd resume=UUID=0ca0caec-3b79-4aa5-9096-09054eef76cd audit=0 video=eDP-1:800x1280 drm.edid_firmware=eDP-1:edid/gpdwinmax.bin fbcon=rotate:1 vga=791
      initrd /boot/initrd-5.10.78-desktop-1.mga8.img
   }
   menuentry 'Mageia (5.10.78-desktop-1.mga8) 8 (on /dev/sda3)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-5.10.78-desktop-1.mga8--1e9b30cb-b17c-4508-b15d-81ae3721a228' {
      insmod part_gpt
      insmod ext2
      set root='hd0,gpt3'
      if [ x$feature_platform_search_hint = xy ]; then
        search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3  1e9b30cb-b17c-4508-b15d-81ae3721a228
      else
        search --no-floppy --fs-uuid --set=root 1e9b30cb-b17c-4508-b15d-81ae3721a228
      fi
      linux /boot/vmlinuz-5.10.78-desktop-1.mga8 root=UUID=1e9b30cb-b17c-4508-b15d-81ae3721a228 ro splash quiet noiswmd resume=UUID=0ca0caec-3b79-4aa5-9096-09054eef76cd audit=0 video=eDP-1:800x1280 drm.edid_firmware=eDP-1:edid/gpdwinmax.bin fbcon=rotate:1 vga=791
      initrd /boot/initrd-5.10.78-desktop-1.mga8.img
   }
   menuentry 'Mageia (5.10.78-desktop-1.mga8) 8 (recovery mode) (on /dev/sda3)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-5.10.78-desktop-1.mga8--1e9b30cb-b17c-4508-b15d-81ae3721a228' {
      insmod part_gpt
      insmod ext2
      set root='hd0,gpt3'
      if [ x$feature_platform_search_hint = xy ]; then
        search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3  1e9b30cb-b17c-4508-b15d-81ae3721a228
      else
        search --no-floppy --fs-uuid --set=root 1e9b30cb-b17c-4508-b15d-81ae3721a228
      fi
      linux /boot/vmlinuz-5.10.78-desktop-1.mga8 root=UUID=1e9b30cb-b17c-4508-b15d-81ae3721a228 ro failsafe
      initrd /boot/initrd-5.10.78-desktop-1.mga8.img
   }
   menuentry 'Mageia (5.10.75-desktop-1.mga8) 8 (on /dev/sda3)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-5.10.75-desktop-1.mga8--1e9b30cb-b17c-4508-b15d-81ae3721a228' {
      insmod part_gpt
      insmod ext2
      set root='hd0,gpt3'
      if [ x$feature_platform_search_hint = xy ]; then
        search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3  1e9b30cb-b17c-4508-b15d-81ae3721a228
      else
        search --no-floppy --fs-uuid --set=root 1e9b30cb-b17c-4508-b15d-81ae3721a228
      fi
      linux /boot/vmlinuz-5.10.75-desktop-1.mga8 root=UUID=1e9b30cb-b17c-4508-b15d-81ae3721a228 ro splash quiet noiswmd resume=UUID=0ca0caec-3b79-4aa5-9096-09054eef76cd audit=0 video=eDP-1:800x1280 drm.edid_firmware=eDP-1:edid/gpdwinmax.bin fbcon=rotate:1 vga=791
      initrd /boot/initrd-5.10.75-desktop-1.mga8.img
   }
   menuentry 'Mageia (5.10.75-desktop-1.mga8) 8 (recovery mode) (on /dev/sda3)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-5.10.75-desktop-1.mga8--1e9b30cb-b17c-4508-b15d-81ae3721a228' {
      insmod part_gpt
      insmod ext2
      set root='hd0,gpt3'
      if [ x$feature_platform_search_hint = xy ]; then
        search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3  1e9b30cb-b17c-4508-b15d-81ae3721a228
      else
        search --no-floppy --fs-uuid --set=root 1e9b30cb-b17c-4508-b15d-81ae3721a228
      fi
      linux /boot/vmlinuz-5.10.75-desktop-1.mga8 root=UUID=1e9b30cb-b17c-4508-b15d-81ae3721a228 ro failsafe
      initrd /boot/initrd-5.10.75-desktop-1.mga8.img
   }
   menuentry 'Mageia (5.10.70-desktop-1.mga8) 8 (on /dev/sda3)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-5.10.70-desktop-1.mga8--1e9b30cb-b17c-4508-b15d-81ae3721a228' {
      insmod part_gpt
      insmod ext2
      set root='hd0,gpt3'
      if [ x$feature_platform_search_hint = xy ]; then
        search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3  1e9b30cb-b17c-4508-b15d-81ae3721a228
      else
        search --no-floppy --fs-uuid --set=root 1e9b30cb-b17c-4508-b15d-81ae3721a228
      fi
      linux /boot/vmlinuz-5.10.70-desktop-1.mga8 root=UUID=1e9b30cb-b17c-4508-b15d-81ae3721a228 ro splash quiet noiswmd resume=UUID=0ca0caec-3b79-4aa5-9096-09054eef76cd audit=0 video=eDP-1:800x1280 drm.edid_firmware=eDP-1:edid/gpdwinmax.bin fbcon=rotate:1 vga=791
      initrd /boot/initrd-5.10.70-desktop-1.mga8.img
   }
   menuentry 'Mageia (5.10.70-desktop-1.mga8) 8 (recovery mode) (on /dev/sda3)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-5.10.70-desktop-1.mga8--1e9b30cb-b17c-4508-b15d-81ae3721a228' {
      insmod part_gpt
      insmod ext2
      set root='hd0,gpt3'
      if [ x$feature_platform_search_hint = xy ]; then
        search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3  1e9b30cb-b17c-4508-b15d-81ae3721a228
      else
        search --no-floppy --fs-uuid --set=root 1e9b30cb-b17c-4508-b15d-81ae3721a228
      fi
      linux /boot/vmlinuz-5.10.70-desktop-1.mga8 root=UUID=1e9b30cb-b17c-4508-b15d-81ae3721a228 ro failsafe
      initrd /boot/initrd-5.10.70-desktop-1.mga8.img
   }
   menuentry 'Mageia (5.10.62-desktop-1.mga8) 8 (on /dev/sda3)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-5.10.62-desktop-1.mga8--1e9b30cb-b17c-4508-b15d-81ae3721a228' {
      insmod part_gpt
      insmod ext2
      set root='hd0,gpt3'
      if [ x$feature_platform_search_hint = xy ]; then
        search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3  1e9b30cb-b17c-4508-b15d-81ae3721a228
      else
        search --no-floppy --fs-uuid --set=root 1e9b30cb-b17c-4508-b15d-81ae3721a228
      fi
      linux /boot/vmlinuz-5.10.62-desktop-1.mga8 root=UUID=1e9b30cb-b17c-4508-b15d-81ae3721a228 ro splash quiet noiswmd resume=UUID=0ca0caec-3b79-4aa5-9096-09054eef76cd audit=0 video=eDP-1:800x1280 drm.edid_firmware=eDP-1:edid/gpdwinmax.bin fbcon=rotate:1 vga=791
      initrd /boot/initrd-5.10.62-desktop-1.mga8.img
   }
   menuentry 'Mageia (5.10.62-desktop-1.mga8) 8 (recovery mode) (on /dev/sda3)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-5.10.62-desktop-1.mga8--1e9b30cb-b17c-4508-b15d-81ae3721a228' {
      insmod part_gpt
      insmod ext2
      set root='hd0,gpt3'
      if [ x$feature_platform_search_hint = xy ]; then
        search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3  1e9b30cb-b17c-4508-b15d-81ae3721a228
      else
        search --no-floppy --fs-uuid --set=root 1e9b30cb-b17c-4508-b15d-81ae3721a228
      fi
      linux /boot/vmlinuz-5.10.62-desktop-1.mga8 root=UUID=1e9b30cb-b17c-4508-b15d-81ae3721a228 ro failsafe
      initrd /boot/initrd-5.10.62-desktop-1.mga8.img
   }
   menuentry 'Mageia (5.10.16-desktop-1.mga8) 8 (on /dev/sda3)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-5.10.16-desktop-1.mga8--1e9b30cb-b17c-4508-b15d-81ae3721a228' {
      insmod part_gpt
      insmod ext2
      set root='hd0,gpt3'
      if [ x$feature_platform_search_hint = xy ]; then
        search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3  1e9b30cb-b17c-4508-b15d-81ae3721a228
      else
        search --no-floppy --fs-uuid --set=root 1e9b30cb-b17c-4508-b15d-81ae3721a228
      fi
      linux /boot/vmlinuz-5.10.16-desktop-1.mga8 root=UUID=1e9b30cb-b17c-4508-b15d-81ae3721a228 ro splash quiet noiswmd resume=UUID=0ca0caec-3b79-4aa5-9096-09054eef76cd audit=0 video=eDP-1:800x1280 drm.edid_firmware=eDP-1:edid/gpdwinmax.bin fbcon=rotate:1 vga=791
      initrd /boot/initrd-5.10.16-desktop-1.mga8.img
   }
   menuentry 'Mageia (5.10.16-desktop-1.mga8) 8 (recovery mode) (on /dev/sda3)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-5.10.16-desktop-1.mga8--1e9b30cb-b17c-4508-b15d-81ae3721a228' {
      insmod part_gpt
      insmod ext2
      set root='hd0,gpt3'
      if [ x$feature_platform_search_hint = xy ]; then
        search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3  1e9b30cb-b17c-4508-b15d-81ae3721a228
      else
        search --no-floppy --fs-uuid --set=root 1e9b30cb-b17c-4508-b15d-81ae3721a228
      fi
      linux /boot/vmlinuz-5.10.16-desktop-1.mga8 root=UUID=1e9b30cb-b17c-4508-b15d-81ae3721a228 ro failsafe
      initrd /boot/initrd-5.10.16-desktop-1.mga8.img
   }
   menuentry 'Mageia (desktop) 8 (on /dev/sda3)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-desktop--1e9b30cb-b17c-4508-b15d-81ae3721a228' {
      insmod part_gpt
      insmod ext2
      set root='hd0,gpt3'
      if [ x$feature_platform_search_hint = xy ]; then
        search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3  1e9b30cb-b17c-4508-b15d-81ae3721a228
      else
        search --no-floppy --fs-uuid --set=root 1e9b30cb-b17c-4508-b15d-81ae3721a228
      fi
      linux /boot/vmlinuz-desktop root=UUID=1e9b30cb-b17c-4508-b15d-81ae3721a228 ro splash quiet noiswmd resume=UUID=0ca0caec-3b79-4aa5-9096-09054eef76cd audit=0 video=eDP-1:800x1280 drm.edid_firmware=eDP-1:edid/gpdwinmax.bin fbcon=rotate:1 vga=791
      initrd /boot/initrd-desktop.img
   }
   menuentry 'Mageia (desktop) 8 (recovery mode) (on /dev/sda3)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-desktop--1e9b30cb-b17c-4508-b15d-81ae3721a228' {
      insmod part_gpt
      insmod ext2
      set root='hd0,gpt3'
      if [ x$feature_platform_search_hint = xy ]; then
        search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3  1e9b30cb-b17c-4508-b15d-81ae3721a228
      else
        search --no-floppy --fs-uuid --set=root 1e9b30cb-b17c-4508-b15d-81ae3721a228
      fi
      linux /boot/vmlinuz-desktop root=UUID=1e9b30cb-b17c-4508-b15d-81ae3721a228 ro failsafe
      initrd /boot/initrd-desktop.img
   }
}

### END /etc/grub.d/30_os-prober ###

Sorry, bit much there but this is the thing.that UUID is correct.

Now that I am here on this Machine I will post the exact message it gives. It seems to me from this that Garuda Grub is seeing all he kernels.

[Sabungayam]

If you do the same command on your Garuda Linux, than it should be possible to chose in your EFI BIOS which Bootloader to use first (EFI Boot Order).

Mageia's grub is on the partition. Not in EFI. EFI will still see it? I thought it could not?

[Sabungayam]

This what I get as the error booting any kernel above 5.10.62.

Before it booted 5.10.70 fine as it was top of he list. Then 5.10.75 was added and I had to go into advanced to select 5.10.70.

Now 5.10.78 is added with last update and 5.10.70 won't boot and I'm down 1 to 5.10.62. Sadly on this hardware 5.10.62 has some regressions. Poorer battery. HDMI sometimes just cuts out. Then blinks back on. Depends on what it's connected to.

Code: Select all

[      0.978687]  pci 0000:00:07.0: DPC: RP PIO log size 0 is invalid
/init: line 153: /user/lib/systemd-udevd: Too many levels of symbolic links
failed to send request to update environment: No such file or directory




So, this is what is you get with all the other kernels except 5.10.62.

Anyone have an idea what that means? How to fix or adjust it? Off hand without knowing too much about Grub 2, it looks as if it doesn't like the number of links to kernels?

[sturmvogel]

I don't know if your high amount of kernels is the reason for this. But you could remove at least

Code: Select all

5.10.16-desktop-1.mga8.img


and try again. Update Grub after the removal. See if you can boot in a "higher" kernel then. If yes, you can repeat this procedure with removal of the oldest kernel and Grub update until you can boot the newest on. It's only a wild guess from my side...

[doktor5000]

To prevent that issue in general, simply set up a chainload for e.g. your Mageia bootloader. That way you don't have to update the grub entries from the other bootloader as soon as you have a kernel update or if any of the options changes in your Mageia install.
See e.g. viewtopic.php?f=8&t=11755&p=68548

[Sabungayam]

I don't know if your high amount of kernels is the reason for this. But you could remove at least

Code: Select all

5.10.16-desktop-1.mga8.img


and try again. Update Grub after the removal. See if you can boot in a "higher" kernel then. If yes, you can repeat this procedure with removal of the oldest kernel and Grub update until you can boot the newest on. It's only a wild guess from my side...

I had that idea, but was concerned it might cause other issues. How might I remove the kernels? Using Control Center or other means?

[Sabungayam]

To prevent that issue in general, simply set up a chainload for e.g. your Mageia bootloader. That way you don't have to update the grub entries from the other bootloader as soon as you have a kernel update or if any of the options changes in your Mageia install.
See e.g. viewtopic.php?f=8&t=11755&p=68548

That was my original idea. This is "THAT" Wonky machine you helped me with that needs the custom EDID. I therefore wanted to chainload Mageia's grub as it has those parameters passed within it. Fortunately and somehow unless all grub2s do this, Garuda's grub seems to pass that parameter and it has not been an issue.

Most of what I will paste here from my /etc/grub.d/40_custom is just what I found online as it was/is on how to chainload.
None of it worked and you will see some attempts I made or tried from further reading but they do not work either and since it booted from Garuda I gave up as I was getting nowhere.

An interesting point I observe from the basic ones done as found on various articles is that each time the message I am getting is that it can't 'find' anything in EFI?

I thought chainload is for booting a grub on a partition? Some other reading I found an article where the person also could not get it to work because grub2 seems to still be looking for something in EFI.

If you have some suggestions of parameters I should change to get the chainload to work, it would be welcome. Thank you.
I will have a look now at the article link you have provided. Thank you.

Ah, actually before submitting this I have looked at that link you posted.

2 words:

OVER my HEAD!

Oh NO!! Sorry 3 words.

My 40_custom:

Code: Select all

menuentry "Chainload Mageia grub in /dev/sda3" {
        set root=(hd0,3)
        chainloader +1
}

menuentry "Magiea" --class gnu-linux --class gnu --class os {
        set root=(hd0,part_gpt3)
        configfile /1e9b30cb-b17c-4508-b15d-81ae3721a228/boot/grub2/grub.cfg
}

menuentry "Mageia8" --class gnu-linux --class gnu --class os {
        set root=(hd0,3)
        configfile /81373c83-9fd8-0048-a11b-2deda4d065be/boot/grub2/grub.cfg
}

/boot/grubmenuentry "Mangeia /dev/sda3" {
        multiboot (hd0,3) /1e9b30cb-b17c-4508-b15d-81ae3721a228/boot/grub2/grub.cfg

}

menuentry "Chainloader" {
    insmod part_gpt
   insmod ext2
    insmod chain
    set root=(hd0,3)
    chainloader +1
}


I can see where actually I have ended up with some of what was mentioned in that link you gave. I just don't know what I'm doing.

1. This is an EFI machine.

2. Both Linux are on the same drive. (Just because it shows another drive with Windoz. Drive has issues. Needs replacing. Then there won't be any Windoz.)

3. The Mageia Grub is supposed to be on GPT partition 3... OH NO. Common error?

Please verify. Grub starts counting at partition 0. Right? My Mageia is on sda3. So have I shot myself in the foot because I should put:

Code: Select all

menuentry "Chainload Mageia grub in /dev/sda3" {
        set root=(hd0,2)
        chainloader +1


Is that so?

[sturmvogel]

Please try to put this into your /etc/grub.de/40_custom file:

Code: Select all

menuentry "mga8_chainload" {
     insmod part_gpt
     insmod ext2
     set root='hd0,gpt3'
     search --no-floppy --fs-uuid --set=root 1e9b30cb-b17c-4508-b15d-81ae3721a228
     configfile /boot/grub2/grub.cfg
}


or

Code: Select all

menuentry "mga8_chainload" {
     insmod part_gpt
     insmod ext2
     search --no-floppy --fs-uuid --set=root 1e9b30cb-b17c-4508-b15d-81ae3721a228
     configfile /boot/grub2/grub.cfg
}


After that do an grub2-mkconfig, or rebuild the bootloader via the Garuda equivalent of control center. You can check if the rebuild was succesfull if you look into your /boot/grub2/grub.cfg. At the line were your 40_custom is called, the content from it should show up.


And please tell us what you mean with

None of it worked

Didn't the menu entry show up. Was there an error message or something like that? What else?

How might I remove the kernels? Using Control Center or other means?

Yes. In MCC set the second column search filter to "installed", type "kernel" into the search field and tick the oldest kernel to remove.
https://wiki.mageia.org/en/Install_and_remove_software_for_beginners#Searching_Applications_with_MCC.27s_Software_Manager

[Sabungayam]

@ sturmvogel

First thank you for your quick reply. That's, a little different some of the commands there. I didn't see such on my Goggling and I was confused with it from the post in the forum.

Thank you very much. Once again, not on the machine at this moment. I will try them when I get home.

Sorry, I wasn't very specific about "NOT WORKING".

Except some wild tries I had. The basic parameters I had found online searching would return a comment:

No such EFI file or location

Not exactly that as I'm not on the machine. It was just complaining about lack of EFI something then it says hit any key which would take me back out to regular grub menu. Some of my wild attempts would simply turn black a moment then also dump me back to grub menu.

Mostly "NOT WORKING" I am referring to for me, cryptic puzzling comments about something lacking in EFI. Didn't know why Grub was wanting that.

I will try to add what you posted here this evening to my 40_custom.

Thank you very much. Report back the results.

[Sabungayam]

Here's what happened:

GREAT!!! Got Mageia's grub!

Mageia's grub will not boot any kernel in the list.

Very puzzling.

My first message/error:

Code: Select all

error: sparse file not allowed.
Press any key to continue...


Which I thought would take me back out to grub menu.

Instead I am back to this. It goes right to this.

Code: Select all

[      0.978687]  pci 0000:00:07.0: DPC: RP PIO log size 0 is invalid
/init: line 153: /user/lib/systemd-udevd: Too many levels of symbolic links
failed to send request to update environment: No such file or directory


From Garuda Grub I can still boot kernel 5.10.62. I can't from Mageia grub.

Not sure where to look next on this.

[sturmvogel]

Could you please post the content from following Mageia files:

/boot/grub2/grub.conf
/etc/default/grub

[Sabungayam]

I will login and do that this evening.

I sadly will have to "UP" the weirdness meter today.

Right here on my work machine, didn't use it yesterday. I used another PC. I have Mageia 8. I updated it.

Code: Select all

5.10.78-desktop-1.mga8


This morning turned it on, and Mageia is the main. It's GRUB is in command here.

I got EXACTLY the same problem. That message about too many links and nothing located where it says.

I will therefore also post from this machine when I have a moment.

I was running

Code: Select all

5.10.75-desktop-1.mga8


Now it can not boot and neither can the top kernel.

I am now here down to:

Code: Select all

5.10.70-desktop-1.mga8


[Sabungayam]

From this machine here at work with Mageia on it.

Code: Select all

[peppermint@localhost ~]$ cat /boot/grub2/grub.conf
cat: /boot/grub2/grub.conf: No such file or directory
[peppermint@localhost ~]$ cat /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="splash quiet noiswmd resume=UUID=d2b92597-b850-413a-8738-c907d5d631a5 audit=0 vga=788"
GRUB_DEFAULT=saved
GRUB_DISABLE_OS_PROBER=false
GRUB_DISABLE_RECOVERY=false
GRUB_DISABLE_SUBMENU=n
GRUB_DISTRIBUTOR=Mageia
GRUB_ENABLE_CRYPTODISK=y
GRUB_GFXMODE=1024x768x32
GRUB_GFXPAYLOAD_LINUX=auto
GRUB_SAVEDEFAULT=true
GRUB_TERMINAL_OUTPUT=gfxterm
GRUB_THEME=/boot/grub2/themes/maggy/theme.txt
GRUB_TIMEOUT=18
[peppermint@localhost




It seems something is missing.

Code: Select all

/boot/grub2/grub.conf

I took a look in the file manager. Indeed, not here.

[sturmvogel]

If you have this problem on several machines, you should maybe create a bug report.
https://wiki.mageia.org/en/How_to_report_a_bug_properly

https://bugs.mageia.org/

But I would first try to remove the oldest kernel ( as mentioned above) and look if the problem persists.

[Sabungayam]

I will try that. Due to a meeting this evening I haven't had a chance to do anything. Even get that 'cat' from the other machine.

It's just that this morning the same issue popped up on my work machine with Mageia as well. It was not there prior to the update.

I had updated it 2 days ago but this was my first turning it on this morning.

Yes, I will try removing the kernel suggested and see how that effects things.

However, the file you asked for the contents of, "grub.conf" should it not have been there? It's missing and I'll check that on the other machine.

IN addition another laptop with Mageia which has not yet been updated. I will check there to see if that file is there before the update.

[sturmvogel]

If it is an old machine (upgraded Mageia/other OS several times) it is possible that the legacy grub was used. That means it is /boot/grub/ instead of /boot/grub2/. But im not 100% sure about that.

Sorry that i can not help you further with that. If it would be my machine i would try stuff which i found when googling your error messages like "error: sparse file not allowed" and "user/lib/systemd-udevd: Too many levels of symbolic links failed to send request to update environment: No such file or directory".
But this could be risky because you could screw your installation finaly. In my case i have my data partition on a seperate harddisk and this is synched to two other HDDs in other machines from time to time. Also on all machines i have my /home on a seperate partition. So not much what could happen if i had to reinstall the main OS. But as i don't know your setups and conditions...and so on.

[doktor5000]

It seems something is missing.

Code: Select all

/boot/grub2/grub.conf

It's grub.cfg not .conf

[doktor5000]

Could you please post the content from following Mageia files:

/boot/grub2/grub.conf
/etc/default/grub

In that case the file is there. On another machine now. I can post that when I get to the problem child at home.

Thanks for that information.