[SOLVED] 2 SSDs each with EFI boot - 4 OS installs - why internal doesn't boot first?

colorpurple21859 · 02-06-2024, 07:51 PM

If you disable os-prober you will loose the neon entries.

To put a working manjaro entry ahead of the bad ones edit the 40_custom.save to this:

Code:

#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
menuentry "Manjaro bootloader (on /dev/sda1)" {
	insmod part_gpt
	insmod fat
	set root='hd0,gpt1'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1  89E2-26CF
	else
	  search --no-floppy --fs-uuid --set=root 89E2-26CF
	fi
	chainloader /EFI/Manjaro/grubx64.efi
}

Then rename the file to 30_custom.save:

Code:

sudo mv /etc/grub.d/40_custom.save /etc/grub.d/30_custom.save

and run update-grub

Nishtya · 02-06-2024, 08:19 PM

I am supposed to replace the manjaro part with above but retain the windows part to new 30 custom? and enable it but disable 40.save? It is too much for me to follow. How many steps, what order, I am trying. Just need a good cleanup looks like and figure out what's wrong with neon now.

When trying out new distros I am spending all my time fixing the booting messes and not actually using the distros, very frustrating.

colorpurple21859 · 02-06-2024, 08:26 PM

Delete the windows entry replace the manjaro part, there will be no 40_custom.save after running the mv command.

What happened with neon, if you ran updates on neon that contained kernel upgrades will have to run update-grub in ubuntu.

Nishtya · 02-06-2024, 08:45 PM

All done as requested. Same behavior:

2 manjaros in ubuntu's grub menu - first one doesn't work. The last one does. what about 40_custom? I don't know anymore if it is enabled or disabled. What else can cause two manjaros? And a slightly detoured neon?

updated-grub. I see neon has 3 kernels to choose from but
choosing neon in the BIOS boot order brings up the ubuntu grub menu where neon is bootable from (it isn't from UEFI firmware settings choice?)

You want output of something let me know. All I can think of is make sure 40 non .save is disabled.

colorpurple21859 · 02-06-2024, 08:58 PM

I forgot 40_custom.save was disabled. Enable 30_custom.save:

Code:

sudo chmod +x /etc/grub.d/30_custom.save
sudo update-grub

Code:

choosing neon in the BIOS boot order brings up the ubuntu grub

You have stumbled across the crux of multibooting different ubuntu based distros, they all tend to use /EFI/ubuntu folder for the bootloader so they over write each other on installation.
A work around for neon is to add a menuentry to 30_custom.save to call neons grub menu.:

Code:

menuentry "KDE neon 5.27 (22.04) (on /dev/sda4)" --class neon --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-cf79ff43-f465-470d-87ab-b2f2768d6738' {
	insmod part_gpt
	insmod ext2
	set root='hd0,gpt4'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt4 --hint-efi=hd0,gpt4 --hint-baremetal=ahci0,gpt4  cf79ff43-f465-470d-87ab-b2f2768d6738
	else
	  search --no-floppy --fs-uuid --set=root cf79ff43-f465-470d-87ab-b2f2768d6738
	fi
	configfile /boot/grub/grub.cfg
}

Nishtya · 02-06-2024, 09:22 PM

Quote:

Originally Posted by colorpurple21859

I forgot 40_custom.save was disabled. Enable 30_custom.save:

Code:

sudo chmod +x /etc/grub.d/30_custom.save
sudo update-grub

[/CODE]

Did the above. I now have 3 manjaros: in second place of grub menu is the chainloader. It boots. In 3rd place is the sdb1 that cannot load kernel. In 7th spot is another chainload that boots.

I have not even looked at the neon issue. My manjaros are multiplying like tribbles instead of going away. Is there a way to show which ones are enabled/disabled?

colorpurple21859 · 02-06-2024, 09:48 PM

The last one is from 40_custom, the first one is from 30_custom, the ones in between are from os-prober. If you add the neon entry to 30_custom and it works to your liking, 30_os-prober can be disabled to clean up the ubuntu grub menu.

Nishtya · 02-07-2024, 08:39 AM

Well I disabled 40_custom and it did clear out that third/last manjaro entry. Now I just need to get rid of the sdb1 that doesn't work. In the meantime I looked at neon in the BIOS setup screen for boot sequence. Attached result of "view". It is not identifying as ubuntu like mint did, it has it own name. can't figure why it won't boot from F12 and choosing it, brings me to ubuntu's grub menu instead. I don't want to chainload it from kubuntu because I grow more disenchanted with that snap firefox by the day. And kubuntu I am tempted to just straight out install mint over it. Mint will take over and maybe straighten this all out without intervention. I can dream, can't I?

colorpurple21859 · 02-07-2024, 09:18 AM

Yes it has it own name but references the Ubuntu directory on efi partition . To fix, boot into neon

Code:

sudo grub-install --no-uefi-secure-boot
sudo efibootmgr  -o 0001 0000 0002 0004 0005

This only works if secure boot is disabled in the bios.

Nishtya · 02-07-2024, 09:54 AM

OMG - I have lost all the efi options except ubuntu. Windows, everything poof. Oh my how to refresh that? I can't boot everything from an install I will be removing. That could be really bad. Please advise?

colorpurple21859 · 02-07-2024, 12:08 PM

Code:

Post the output of sudo efibootmgr -v

Nishtya · 02-07-2024, 12:13 PM

Quote:

Originally Posted by colorpurple21859

Code:

Post the output of sudo efibootmgr -v

I got to windows by re-enabling 40custom that has the windows boot in it/ But all I have is grub menu to boot anything. It is the only thing showing in bios setup boot

Code:

BootCurrent: 0001
Timeout: 2 seconds
BootOrder: 0001
Boot0000* Windows Boot Manager  HD(1,GPT,3de1a57a-f04e-4771-b896-09c935589e6b,0x800,0x113000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...,................
Boot0001* ubuntu        HD(1,GPT,3de1a57a-f04e-4771-b896-09c935589e6b,0x800,0x113000)/File(\EFI\ubuntu\shimx64.efi)
Boot0002* neon  HD(1,GPT,3de1a57a-f04e-4771-b896-09c935589e6b,0x800,0x113000)/File(\EFI\neon\grubx64.efi)
Boot0004* Manjaro       HD(1,GPT,3de1a57a-f04e-4771-b896-09c935589e6b,0x800,0x113000)/File(\EFI\Manjaro\grubx64.efi)

colorpurple21859 · 02-07-2024, 12:18 PM

Efibootmgr is still showing the bio’s firmware entries, if you disabled secure boot, you may have to renable or change some other bios setting.

Nishtya · 02-07-2024, 12:31 PM

Secure boot has never been turned on. After all but ubuntu disappeared I did go in there to the boot sequence tab and restored to saved customer setting but there is no change, it only shows ubuntu. Could I use those strings from efibootmgr above to try to repopulate, there is an add button? If I try just one at a time, not windows, either neon or manjaro?

well I was able to add neon into boot sequence. But manjaro didn't work -boots to a grub rescue prompt. I don't know where to start with windows what to enter. I remember something when everything was working it was just pointing at a script.

I am marking this solved in that I managed to repopulate bios setup boot sequence and all of them can boot from a one-time boot choice or out of ubuntu's grub. I was stumped with the second manjaro that they had to show me to chainload a working one into. I resorted to the grub customizer tool. Myself, I would only use it as a last resort.

Takeaways: 1)the buntu family EFI booting scheme has got to be cleaned up if they want clients to actually try one of their other offerings on the same machine as a current buntu cousin. 2)UEFI I feel is making things more complicated in multiboot situations and some BIOS like mine may not behave as expected when booting external devices. If it is a removable and bootable, this is going to boot it by default and good luck with that. Dell Inspiron 5566, circa 2016 or so.

Thanks for all the help

colorpurple21859 · 02-07-2024, 06:05 PM

you're welcome.