No boot after Boot-Repair-Disk

[gold_finger]

I guess that LL, like Windows, wants to 'rule the roost'. My bad.

Yes, LL does like to "rule the roost" -- not "your bad" though.  Here is Jerry's post explaining why he tweaked grub that way:  https://www.freecinema2022.gq/forums/index...31#msg2431.

I don't always pick the best way to do something. I only try to share, to the best of my ability, what has worked for me in the past.

There was nothing wrong with your post.  I just didn't want fbr to think that only one of the two ways installs code to the MBR.  Also, since Boot-Repair runs the fix automatically and he has more than one distro installed, I had a feeling that it might not pick the correct Root partition to point to when repairing.  (I don't know what it does in that situation -- maybe it just picks the first Root partition it finds?)

Running Boot-Repair from a live session did not help, ....

The reason I ran Boot-Repair in the first place was that it puts sda5 at the top of the list and also defaults to that. I now have LL in sda11 on top, but that is a minor thing.

If you want to change boot order, easiest way would probably be to follow N4RPS's recommendation and install Grub Customizer to your LL installation.

Just out of curiosity, can you post back with the output of this command to show your partition structure on the HDD?

Code:

sudo parted -l

(Command ends with a lowercase letter "L", not a number 1.)

I'm wondering if your sda5 is the first Linux root partition on the drive like I speculated above (regarding Boot-Repair behavior).

Apparently LL is different from many other distros when it comes to booting.

Yes, see link above for explanation.


P.s.  Stupid me just realized (after the fact) that I had the mount line in step #3 wrong.  Had "sudo mount /dev/sdX /mnt" when it should have been "sudo mount /dev/sdaX /mnt".  Obviously fbr was smart enough to catch that on his own -- good job fbr!