help recovering boot menu on triple boot witn neon, Win10, old Mate?

[jlittle]

+1 for oshunluvr's approach. Saves much time and effort in the long run if one has more. I do it now with a btrfs subvolume, rather than a separate partition, but that's just the btrfs way.

Also, from your posts, running sudo apt autoremove on the install where all those kernels were found would free up a lot of space.

Sent from my Vodafone Smart ultra 6 using Tapatalk

[oshunluvr]

I do it now with a btrfs subvolume, rather than a separate partition, but that's just the btrfs way.

Me too obviously, but I figured people might be getting tired of my BTRFS preaching

[Qqmike]

I have run boot-repair several times. I've looked at the output and can find no hint at what needs to be done.

From the output of Boot-Repair:

=================== Suggested repair
The default repair of the Boot-Repair utility would reinstall the grub-efi-amd64-signed of sda6, using the following options:        sda1/boot/efi,

If you selected that to be done (by Boot-Repair), that should have re-installed GRUB-EFI from your Neon (sda6) to the ESP (sda1), and so should have worked, in theory. (I do believe that Neon has some nuances wrt GRUB, but I am not familiar with NEON.)

According to efibootmgr, NEON was controlling the booting (Neon 0003 first, then your sda7 ubuntu 0000):

=================== efibootmgr -v
BootCurrent: 0003
Timeout: 1 seconds
[B]BootOrder: 0003[/B],[COLOR=#0000ff]0000[/COLOR],0002,0001,0004
[COLOR=#0000cd]Boot0000* ubuntu[/COLOR]        HD(1,GPT,c4a55e10-15c5-4c30-9945-69564a591914,0x800,0x82000)/File(EFIUBUNTUSHIMX64.EFI)
Boot0001* Windows Boot Manager  HD(1,GPT,c4a55e10-15c5-4c30-9945-69564a591914,0x800,0x82000)/File(EFIMICROSOFTBOOTBOOTMGFW.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.}....................
Boot0002* usb   HD(1,GPT,c4a55e10-15c5-4c30-9945-69564a591914,0x800,0x82000)/File(EFIBOOTBOOTX64.EFI)
[B]Boot0003* neon[/B]  HD(1,GPT,c4a55e10-15c5-4c30-9945-69564a591914,0x800,0x82000)/File(EFINEONSHIMX64.EFI)
Boot0004* Hard Drive    BBS(HD,,0x0)..GO..NO........o.H.F.S.5.1.2.G.3.9.M.N.D.-.3.5.1.0.A....................A...........................>..Gd-.;.A..MQ..L.J.F.6.6.5.N.1.6.1.5.5.1.6.0.6.P. .J. . ........BO

So, you could have reinstalled GRUB from either NEON (preserving the status quo and having NEON's GRUB control the booting), or re-install GRUB from the sda7 OS. When you installed 19.04 fresh, it naturally, automatically took over the booting (i.e., its GRUB was installed to the proper ubuntu directory in the sda1 ESP).

(To do a reinstall of GRUB, you should be able to use Boot-Repair, following their suggested repair; or that how-to you linked to; or my how-to on it (using chrooting):
Re-install GRUB2 from Live DVD/USB flash drive
https://www.kubuntuforums.net/showth...l=1#post374017

[pwrcul]

Thanks re future boot issues repair

From the output of Boot-Repair:

=================== Suggested repair
The default repair of the Boot-Repair utility would reinstall the grub-efi-amd64-signed of sda6, using the following options:        sda1/boot/efi,

If you selected that to be done (by Boot-Repair), that should have re-installed GRUB-EFI from your Neon (sda6) to the ESP (sda1), and so should have worked, in theory. (I do believe that Neon has some nuances wrt GRUB, but I am not familiar with NEON.)

According to efibootmgr, NEON was controlling the booting (Neon 0003 first, then your sda7 ubuntu 0000):

=================== efibootmgr -v
BootCurrent: 0003
Timeout: 1 seconds
[B]BootOrder: 0003[/B],[COLOR=#0000ff]0000[/COLOR],0002,0001,0004
[COLOR=#0000cd]Boot0000* ubuntu[/COLOR]        HD(1,GPT,c4a55e10-15c5-4c30-9945-69564a591914,0x800,0x82000)/File(EFIUBUNTUSHIMX64.EFI)
Boot0001* Windows Boot Manager  HD(1,GPT,c4a55e10-15c5-4c30-9945-69564a591914,0x800,0x82000)/File(EFIMICROSOFTBOOTBOOTMGFW.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.}......
Boot0002* usb   HD(1,GPT,c4a55e10-15c5-4c30-9945-69564a591914,0x800,0x82000)/File(EFIBOOTBOOTX64.EFI)
[B]Boot0003* neon[/B]  HD(1,GPT,c4a55e10-15c5-4c30-9945-69564a591914,0x800,0x82000)/File(EFINEONSHIMX64.EFI)
Boot0004* Hard Drive    BBS(HD,,0x0)..GO..NO...o.H.F.S.5.1.2.G.3.9.M.N.D.-.3.5.1.0.A......A......>..Gd-.;.A..MQ..L.J.F.6.6.5.N.1.6.1.5.5.1.6.0.6.P. .J. . ......BO

So, you could have reinstalled GRUB from either NEON (preserving the status quo and having NEON's GRUB control the booting), or re-install GRUB from the sda7 OS. When you installed 19.04 fresh, it naturally, automatically took over the booting (i.e., its GRUB was installed to the proper ubuntu directory in the sda1 ESP).

(To do a reinstall of GRUB, you should be able to use Boot-Repair, following their suggested repair; or that how-to you linked to; or my how-to on it (using chrooting):
Re-install GRUB2 from Live DVD/USB flash drive
https://www.kubuntuforums.net/showth...l=1#post374017

Thanks for the explanation.
I bookmarked it for the chance I need it sometime in future.