You can see whether Boot Repair is working by attempting to boot after it's done. You've done that, and it's not working in your case. That's not to say it's necessarily Boot Repair's fault, though; a lot of things that Boot Repair cannot control, or even detect, can affect the boot process. I have some specific comments on your setup (some of which aren't boot-related per se), based on your second Boot Repair output:
- You have four NTFS partitions, but it appears you have no Windows installation. (One of these four NTFS partitions is a Windows recovery partition, though.) It's possible that the Boot Repair output is missing the evidence of a bootable Windows partition; but if not, either you've accidentally trashed your Windows installation or you deliberately deleted it. If the former, you should stop fiddling with Ubuntu and fix Windows before proceeding. If the latter, you should not be using NTFS on a Linux-only installation, for numerous reasons. Unless you've got data on those NTFS partitions that you want to preserve, you're best off deleting them and continuing with Linux-native filesystems.
- You're using BIOS/CSM/legacy mode on a computer that almost certainly uses an EFI/UEFI. Using the CSM creates all sorts of problems, as detailed on this page of mine. In particular given your symptoms, you sometimes need to play games with partition table details when booting an EFI-based computer from a GPT disk in BIOS/CSM/legacy mode. There's a significant chance that this is why your computer won't boot with your current installation. You're probably better off disabling the CSM and doing an EFI-mode install.
- It's possible that a leftover NVRAM entry from your Windows installation is blocking a BIOS-mode boot of your Ubuntu. You might be able to fix this by adjusting the boot priority settings in your firmware setup tool, but precise details of how to do this vary from one system to another, so I can't provide detailed instructions. Performing a fresh EFI-mode install of Ubuntu should override any leftover Windows NVRAM entries, which of course is another reason to do a fresh EFI-mode install of Ubuntu.
- If you do have a Windows installation, it must necessarily be in EFI/UEFI mode. Mixing an EFI-mode Windows installation with a BIOS-mode Ubuntu installation is a recipe for frustration. Thus, if Boot Repair has missed a Windows installation, my general recommendation to install Ubuntu in EFI mode becomes a very strong recommendation.
- Your disk is not big enough to need GPT. Given the presence of occasional quirks of BIOS-mode booting from GPT disks, you're probably better off switching from GPT to MBR if you want to stick with BIOS-mode booting. This can be done non-destructively with
gdisk
, as described here; however, there are caveats, and you'll need to re-install GRUB. Unless you need to preserve those NTFS partitions, you're probably better off wiping the disk clean and starting with a fresh MBR.
Overall, your best bet is to start clean:
- If your NTFS partitions hold files you want to preserve, back them up to an external medium.
- Wipe the hard disk with
sudo sgdisk -Z /dev/sda
. This command is destructive!
- Disable the CSM in your firmware.
- Boot the Ubuntu installer. It should boot in EFI/UEFI mode, as indicated by the presence of a directory called
/sys/firmware/efi
. (You can look for this directory by booting to "try before installing" mode and using a Terminal or file manager. If the directory is present, you can run the installer from the same boot.)
- Install Ubuntu. Use default partitioning or the "Something Else" option, as you see fit. If the latter, I recommend the following partitions:
- A ~550MiB EFI System Partition (ESP)
- A partition a little bigger than your RAM for swap space
- A 20-30MiB Linux root (
/
) partition
- The rest of your disk as a
/home
partition
- Note that there's seldom a need in Linux for multiple data partitions
After you install Ubuntu, the system should boot normally. There are multiple questions and answers here about installing Ubuntu in EFI mode, as well as information and tutorials elsewhere. For more information, check out:
I strongly recommend you read these pages before posting back with more problems; you'll be in a much better position to understand what's going on, and therefore to post a question that will produce a useful response, after you read the preceding pages. Ideally, you'll learn enough that you'll be able to solve your problem yourself.