My computer doesn't boot. I format my Toshiba laptop with a bootable USB drive. I make this my_partitions, and when i restart the computer after the installation, my computer does not boot. Then i run boot-repair and finishes with this message. I reboot ant nothing happens. I review some questions before, but could't find anything yet. Can someone help me please?
2 Answers
There is a blog post discussing this at http://adityagilra.blogspot.com/2014/11/fixing-ubuntu-boot-problems-with-boot.html
"""You can now reboot your computer. Please do not forget to make your BIOS boot on sda1/EFI/ubuntu/grubx64.efi file!""" I think they just mean that: enable UEFI and set the boot order to first boot HDD in the BIOS.
But you can check using efibootmgr:
I installed efibootmgr using synaptic. (see http://ubuntuforums.org/showthread.php?t=2023086)
(If you're not root, use
sudo efibootmgr -vcan become root bysudo su -) root@ubuntu:~# efibootmgr -v BootOrder: 0000,0000,0000,0000 Boot0000* ubuntu HD(1,22,2faf1,d6f60eae-849f-43e3-836c-2280067f3161)File(\EFI\ubuntu\shimx64.efi)
According to What is the difference between grubx64 and shimx64? shimx64.efi is for Secure Boot.
As noted at the Arch Boot Process:
A boot entry could simply be a disk. In this case the firmware looks for an EFI system partition on that disk and tries to find a EFI application in the fallback boot path \EFI\BOOT\BOOTX64.EFI (BOOTIA32.EFI on IA32 (32-bit) EFI systems). This is how UEFI bootable removable media work.
Honestly, the warning message should probably be removed from that boot-repair utility, altho I'm not so sure it's well-maintained.
- 249
This becomes much clearer if you look at the current boot order with $ efibootmgr -v (abridged output from my memory):
Currently: BootOrder0001
BootOrder0000 linpus lite
BootOrder0001 linpus lite
BootOrder0002 ubuntu (this one has the path mentioned in the warning)
What they mean with this cryptic reminder is to change the boot order in the BIOS. I recently did a boot-repair via USB stick ubuntu live, like you, but I was then stuck in a "boot, vendor logo, restart" loop – until I've made that BIOS change.
- 117