Cannot boot Ubuntu 18.04 LTS partition or Grub bootloader

[yeedyourlasthaw]

I was dumb and removed Ubuntu 16.04 without correctly removing the grub bootloader first. My Windows 10 is EFI.
After I removed Ubuntu I have not been able to boot my newly partitioned Ubuntu 18.04 lts and grub bootloader does not pop up anymore.

Additionally I have somehow got an old fedora boot that I can still see in bios, I think I have really messed things up at this point (I am clearly a noob).

Please let me know if there is any info I can provide for you to better help me with this issue, any help would be appreciated greatly.

[oldfred]

May be best to see details, use ppa version with your live installer (2nd option) or any working install, not older Boot-Repair ISO:
Please copy & paste link to the Boot-info summary report ( do not post report), the auto fix sometimes can create more issues.
https://help.ubuntu.com/community/Boot-Repair &
https://sourceforge.net/p/boot-repair/home/Home/

Did you install in UEFI boot mode?
You can use efibootmgr to remove UEFI boot entries. And remove folders in ESP - efi system partition for old installs.
Your new install should have added a new UEFI ubuntu entry, but you now may have old ones also.
Report above will show this which shows all your UEFI boot menu entries:
sudo efibootmgr -v

[yeedyourlasthaw]

Did you install in UEFI boot mode?
You can use efibootmgr to remove UEFI boot entries. And remove folders in ESP - efi system partition for old installs.
Your new install should have added a new UEFI ubuntu entry, but you now may have old ones also.
Report above will show this which shows all your UEFI boot menu entries:
sudo efibootmgr -v

I did install UEFI boot mode. Excuse my lack of knowledge but I do not think I can use teh efibootmgr without access to my Ubuntu partition right?

When I go to the bios and try to boot Ubuntu, it either boots Windows 10 instead, or some old version of Fedora that I thought I removed a while back.

[oldfred]

You can run Boot-Repair from Live installer.
And you can run efibootmgr from live installer.
Boot-Repair actually runs efbootmgr -v as part of report to see what entries you have.

[yeedyourlasthaw]

Thank you I will try this.

Just for reference, I ran sudo fdisk -l and got the following.

ubuntu@ubuntu:~$ sudo fdisk -l
Disk /dev/loop0: 1.8 GiB, 1905045504 bytes, 3720792 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop1: 91 MiB, 95408128 bytes, 186344 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop2: 34.6 MiB, 36216832 bytes, 70736 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop3: 140.7 MiB, 147496960 bytes, 288080 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop4: 2.3 MiB, 2355200 bytes, 4600 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop5: 13 MiB, 13619200 bytes, 26600 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop6: 14.5 MiB, 15208448 bytes, 29704 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop7: 3.7 MiB, 3878912 bytes, 7576 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x080ab78e

Device     Boot      Start        End    Sectors   Size Id Type
/dev/sda1             2048    1026047    1024000   500M  7 HPFS/NTFS/exFAT
/dev/sda2          1026048 1260310436 1259284389 600.5G  7 HPFS/NTFS/exFAT
/dev/sda3       1260310528 1261314047    1003520   490M 27 Hidden NTFS WinRE
/dev/sda4       1261316094 1953523711  692207618 330.1G  5 Extended
/dev/sda5  *    1261316096 1262364671    1048576   512M ef EFI (FAT-12/16/32)
/dev/sda6       1262366720 1953523711  691156992 329.6G 83 Linux

Partition 4 does not start on physical sector boundary.


Disk /dev/sdb: 28 GiB, 30016659456 bytes, 58626288 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 2AF2F925-7EEE-4A64-9778-035F012145EA

Device     Start    End Sectors  Size Type
/dev/sdb1   2048 411647  409600  200M EFI System


Disk /dev/sdc: 28.7 GiB, 30752636928 bytes, 60063744 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xccd4ebea

Device     Boot Start      End  Sectors  Size Id Type
/dev/sdc1  *       63 60063743 60063681 28.7G  c W95 FAT32 (LBA)

I will continue with the boot repair process.

[yeedyourlasthaw]

You can run Boot-Repair from Live installer.
And you can run efibootmgr from live installer.
Boot-Repair actually runs efbootmgr -v as part of report to see what entries you have.

I tried all of the above and still I cannot boot into Ubuntu.

Is it possible that having an SSD and HDD is causing this?

Here is the output to efibootmgr -v

ubuntu@ubuntu:~$ efibootmgr 
BootCurrent: 0011
Timeout: 1 seconds
BootOrder: 0000,0003,000C,000E,0006,000A,0009,0008,0010,0011
Boot0000* ubuntu
Boot0003* Windows Boot Manager
Boot0006* Fedora
Boot0008* Fedora
Boot0009* UEFI OS
Boot000A* UEFI OS
Boot000C* Hard Drive 
Boot000E* UEFI OS
Boot0010* ubuntu
Boot0011* UEFI: SanDisk
ubuntu@ubuntu:~$ efibootmgr -v
BootCurrent: 0011
Timeout: 1 seconds
BootOrder: 0000,0003,000C,000E,0006,000A,0009,0008,0010,0011
Boot0000* ubuntu    VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0003* Windows Boot Manager    HD(1,GPT,ced22be2-d879-482c-8267-c3a6e955d146,0x800,0x64000)/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.}....................
Boot0006* Fedora    HD(1,GPT,ced22be2-d879-482c-8267-c3a6e955d146,0x800,0x64000)/File(\EFI\FEDORA\shim.efi)
Boot0008* Fedora    HD(1,GPT,ced22be2-d879-482c-8267-c3a6e955d146,0x800,0x64000)/File(\EFI\fedora\shim.efi)
Boot0009* UEFI OS    VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot000A* UEFI OS    HD(1,GPT,ced22be2-d879-482c-8267-c3a6e955d146,0x800,0x64000)/File(\EFI\BOOT\BOOTX64.EFI)
Boot000C* Hard Drive     BBS(HD,,0x0)..GO..NO........O.T.O.S.H.I.B.A. .D.T.0.1.A.B.A.1.0.0.V.................>..Gd-.;.A..MQ..L. . . . . . . . . . .Z. .2.5.9.V.J.X.S.N........BO..NO........O.K.I.N.G.S.T.O.N. .S.S.2.0.0.S.3.3.0.G.................>..Gd-.;.A..MQ..L.0.5.2.0.B.6.2.7.4.3.6.0.A.4.5.7. . . . ........BO..NOq.......O.S.a.n.D.i.s.k.................>..Gd-.;.A..MQ..L.4.C.5.3.0.0.0.0.0.1.0.5.2.3.1.1.2.3.6.5........BO
Boot000E* UEFI OS    VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0010* ubuntu    VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0011* UEFI: SanDisk    PciRoot(0x0)/Pci(0x14,0x0)/USB(15,0)/HD(1,MBR,0xccd4ebea,0x3f,0x3947fc1)..BO

When I went to bios I tried booting and it returns:

Failed to open \EFI\BOOT\grubx64.efi _ Not Found
Failed to load Image \EFI\BOOT\grubx64.efi: Not Found
start_image() returned Not Found

[jeremy31]

The file should be in \EFI\ubuntu

[yeedyourlasthaw]

Thanks, but how do I find that file? From bios?

[Dennis N]

Please post boot info summary as suggested earlier in post 2. Things are not clear from the given information.
For example:

Boot0000* ubuntu    VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)

doesn't look like UEFI boot manager entry for a UEFI install. Maybe this is a CSM entry? Since there is no path defined to a UEFI grub boot loader as in your Fedora entries, what does this point to? Boot info summary may help us understand how this is working.

Your sda is MSDOS partitioned. You should use GPT for UEFI installations.

[yeedyourlasthaw]

Please post boot info summary as suggested earlier in post 2. Things are not clear from the given information.

Are you referring to the efibootmgr -v?

ubuntu@ubuntu:~$ efibootmgr -vBootCurrent: 0011
Timeout: 1 seconds
BootOrder: 0000,0003,000C,000E,0006,000A,0009,0008,0010,0011
Boot0000* ubuntu    VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0003* Windows Boot Manager    HD(1,GPT,ced22be2-d879-482c-8267-c3a6e955d146,0x800,0x64000)/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.}....................
Boot0006* Fedora    HD(1,GPT,ced22be2-d879-482c-8267-c3a6e955d146,0x800,0x64000)/File(\EFI\FEDORA\shim.efi)
Boot0008* Fedora    HD(1,GPT,ced22be2-d879-482c-8267-c3a6e955d146,0x800,0x64000)/File(\EFI\fedora\shim.efi)
Boot0009* UEFI OS    VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot000A* UEFI OS    HD(1,GPT,ced22be2-d879-482c-8267-c3a6e955d146,0x800,0x64000)/File(\EFI\BOOT\BOOTX64.EFI)
Boot000C* Hard Drive     BBS(HD,,0x0)..GO..NO........O.T.O.S.H.I.B.A. .D.T.0.1.A.B.A.1.0.0.V.................>..Gd-.;.A..MQ..L. . . . . . . . . . .Z. .2.5.9.V.J.X.S.N........BO..NO........O.K.I.N.G.S.T.O.N. .S.S.2.0.0.S.3.3.0.G.................>..Gd-.;.A..MQ..L.0.5.2.0.B.6.2.7.4.3.6.0.A.4.5.7. . . . ........BO..NOq.......O.S.a.n.D.i.s.k.................>..Gd-.;.A..MQ..L.4.C.5.3.0.0.0.0.0.1.0.5.2.3.1.1.2.3.6.5........BO
Boot000E* UEFI OS    VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0010* ubuntu    VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb) 
Boot0011* UEFI: SanDisk    PciRoot(0x0)/Pci(0x14,0x0)/USB(15,0)/HD(1,MBR,0xccd4ebea,0x3f,0x3947fc1)..BO