Linux efi not found

Error: «Failed to open \EFI\BOOT\grubx64.efi. » (Dual-Booting)

Today after I installed Ubuntu 16.04 via USB on my pre-installed Windows 8 machine, I was required to restart my computer. After doing so I wasn’t offered to select an OS, so after searching the internet, I came across Boot-Repair which I ran using the Try Ubuntu option in my Ubuntu installation USB. Following the boot repair I got a message saying,

If your computer directly reboots into Windows, try to change the boot order in your BIOS. If your BIOS does not allow to change the boot order, change the default boot entry of your Windows bootloader. For example, you can boot into Windows then type the following in an admin command prompt:

bcdedit /set path \EFI\ubuntu\shimx64.efi 

After I rebooted my PC, I am receiving the following error message for about 3 seconds, after which it boots automatically into Windows 8, without letting me access Ubuntu. Error received while booting after manufacturer’s logo, before grub:

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

So I tried the other solution of typing that command in the cmd, to which my surprise, worked, and I am now prompted a window (grub) to choose my OS each time I turn on my PC, but unfortunately, I still receive an error each time, that lasts about 3s, after which I can choose my OS (both are working just fine) and work normally. Do you have any suggestions to get rid of the error message each time I boot my PC?

Does the file . /EFi/BOOT/grubx64.efi actually exist? Mount the EFI partition in a live session and look. The normal place for grub is /EFI/ubuntu/grubx64.efi. Do you have an entry for it (efibootmgr -v)?

Please run the Boot Repair utility and select the «Create BootInfo Summary» option. (DO NOT click «Recommended Repair,» at least not yet!) When asked whether to upload the report, click «Yes,» and then post the URL provided here. This will give us more details about your configuration, which is required to base an answer on more than guesswork. Also, both the image links point to the same image. Please correct whichever one needs correcting (I suspect the first).

For some yet unknown reason; my QNAP does not want to boot from /EFI/Ubuntu so I had to move the files to /EFI/Boot.

Читайте также:  Astra linux default password

6 Answers 6

Finally managed to solve it.

For the rest, open the terminal

$ sudo bash $ cd /boot/efi/EFI $ sudo cp -p ubuntu/grubx64.efi Boot $ sudo touch ubuntu/grubx64.efi.gbr 

After that, I stopped seeing the error message and grub showed up normally (it did before, too, just after seeing that error message for 3s).

can you provide more details of how to go about this? do I boot from liveusb, which partition to mounts. thanks

After a Windows update I could no longer boot into Ubuntu: failed to open /EFI/ubuntu/grubx64.efi

I was able to boot using a Live Ubuntu USB, then:

# find the EFI partition sudo fdisk -l # mount EFI sudo mount /dev/ /mnt cp -p /cdrom/EFI/grubx64.efi /mnt/EFI/ubuntu 

I had to reboot and enable Secure Boot and that did the trick. This was dual booting 18.04 on a Lenovo Thinkpad t470 with Windows 10

Don’t try these present above. These are hard and may not work. I also ran into same problem so what I did was took a live USB of Ubuntu and pressed try Ubuntu. Then I went to terminal . There you press this following command .Internet is needed here.

First command: sudo add-apt-repository ppa:yannubuntu/boot-repair && sudo apt update

Second command : sudo apt-get install boot-repair && boot-repair

Then an app will be there. In that you press recommended fix. Then it will fix the grub and reinstall it .here too Internet is must. Then reboot and enjoy dualbooting.

You should probably fix the boot loader entry itself instead of copying files around. That’ll always break when upstream updates something. Try something like this instead:

efibootmgr --create --label Ubuntu --disk /dev/sda1 --loader "\EFI\ubuntu\grubx64.efi" 

Where /dev/sda1 corresponds to /boot/efi . For the curious, there’s more details in this guide.

You saved my day. I tried: 1. Boot-repair (recommended) 2. Copy manually file from /cdrom/ to mounted efi partition and this solution is the one I have my Ubuntu back (and also windows as I have dual-boot with 2 ssd). Thank you very much.

Is it possible to run this from within Windows? I have a savedefault in my grubconfig and after switching to Windows I’m now stuck in Windows.

Very similar error occurred with my Ubuntu 20.04 LTS (Focal Fossa) and my Windows 10 on the same SSD, after receiving the latest Windows 10 June 2020 update. The boot menu with grub was gone, the laptop only booted to Windows 10.

**This is how I solved: **I downloaded the Ubuntu ISO, burned to USB drive with Rufus, then booted up the laptop with this USB drive. I selected Try Ubuntu. Open terminal, then set the keyboard

I was not able to recover the grub using the boot-repair utility, because it complained about a missing EFI partition at the beginning of the disk, which was there indeed.

Читайте также:  Asus usb ac53 linux

**Finally this solution worked: ** Check the available partitions

sudo fdisk -l Disk /dev/nvme0n1: 238,49 GiB, 256060514304 bytes, 500118192 sectors Disk model: INTEL SSDPEKKF256G7L 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: A1234567-6733-7263-BB45-5E83CFBE3430 Device Start End Sectors Size Type /dev/nvme0n1p1 2048 534527 532480 260M EFI System /dev/nvme0n1p2 534528 567295 32768 16M Microsoft reserved /dev/nvme0n1p3 567296 259842047 259274752 123,6G Microsoft basic data /dev/nvme0n1p4 498069504 500117503 2048000 1000M Windows recovery environment /dev/nvme0n1p5 259842048 481527807 221685760 105,7G Linux filesystem /dev/nvme0n1p6 481527808 498069503 16541696 7,9G Linux swap Partition table entries are not in disk order. 

Mount the EFI System partition, you may check what’s there:

sudo mount /dev/nvme0n1p1 /mnt/ sudo ls /mnt/EFI/ubuntu sudo stat /mnt/EFI/ubuntu/grubx64.efi File: /mnt/EFI/ubuntu/grubx64.efi Size: 1419128 Blocks: 2776 IO Block: 4096 regular file Device: 10301h/66305d Inode: 14 Links: 1 Access: (0700/-rwx------) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2020-06-25 02:00:00.000000000 +0200 Modify: 2020-06-25 19:24:06.000000000 +0200 Change: 2020-06-25 18:55:30.870000000 +0200 Birth: - 

Then copy over the correct grubx64.efi from the USB drive, as recommended by Matthew Hegarty and adrianTNT above.

cp -p /cdrom/EFI/grubx64.efi /mnt/EFI/ubuntu/ 

Then reboot, remove your USB and you should be fine. (At least I hope I’m fine. 🙂 )

Источник

No EFI System Partition option for Ubuntu 18.10

I’m trying to install Ubuntu 18.10 on a new not partitioned HDD (using a VMWare machine). I try with manual partitioning to create the EFI System Partition but there is no EFI System Partition option (or other option containing the EFI word). I tried with 100M, 300M, 500M, 512M sizes but no luck. What’s the solution for this? PS: the similar question related to Ubuntu 15.10 doesn’t help

hi. I’m a bit surprized by your wording here, maybe I’m missunderstanding, would you mind editing your post to go through what you expect, what unfortunately is the case instead and a picture of the screen you’re seeing durring what I assume is the install process from the Live CD? (if you choose «try ubuntu» instead of «install ubuntu» while booting you’ll be able to run the same install process from the desktop icon but also take screencap, with the screencap app and upload it here.)

Are you using USB installable stick for Ubuntu 18.10? You may refer Ubuntu 18.04.02 Bionic Beaver to prepare USB stick with UEFI (non CSM) and “Partition scheme” to “GPT”. Although this procedure is for Ubuntu 18.04, but you can use the same procedure to prepare USB bootable stick for Ubuntu 18.10.

As you imagine I try the installation process at PC boot time. I’m simply creating a VMWare machine with Ubuntu, nothing fancy besides the manual partitioning.

Читайте также:  Добавить модуль ядра linux

1 Answer 1

The EFI System Partition (ESP)

The requirements for the ESP partition are:

  1. It must be a primary partition (relevant only for MBR based partition table)
  2. It must be a FAT32 partition
  3. The boot flag must be set

Ubuntu 18.10 Installation Something Else option

Before we get to the Something else option and manual partition of the hard drive, we have to make sure the Live USB/DVD or the ISO (in case of virtual machines) boot in the UEFI mode and not the legacy BIOS mode. I will describe both below:

Live USB/DVD/ISO in BIOS Legacy Mode

The first clue that the computer booted in BIOS Legacy mode is from the Live USB/DVD/ISO boot screen. If you see:

enter image description here

Then you have booted in BIOS mode!

In this mode, the installer does not show an option to create an ESP partition. There is no ESP option because in this mode one does not need an ESP partition.

enter image description here

If you get this, cancel the installation and figure out how to boot from the Live USB/DVD/ISO in the UEFI mode. (More on this for virtual machines later in the answer.)

Live USB/DVD/ISO in UEFI Mode

When you boot the Live USB/DVD/ISO using the UEFI mode you will see:

enter image description here

As you see below in this mode, the installer will show an option to create an ESP partition:

Note: It may say EFI Boot Partiion in some version of Ubuntu instead of EFI System Partiion as it shows in the image below.

enter image description here

Once you select the right partition type you will see:

enter image description here

After you click the OK button above you will get:

enter image description here

Select UEFI boot in VMWare workstation

When you create the new VM and before you try to install Ubuntu, On VMware Workstation, go into VM > Settings > Options > Advanced, and check Boot with EFI instead of BIOS.

enter image description here

Select UEFI boot in QEMU Virtual Machine Manager

I assume you have qemu virtual machine already setup in an Ubuntu host machine. You need to install the virtual firmware for UEFI, ovmf in the host:

sudo apt install qemu ovmf

The next step must be done when you create a new virtual machine. Once the VM is created the boot option cannot be changed from BIOS to UEFI or vice versa. Check the box Customize configuration before install in Step 5:

enter image description here

In the Overview tab change the ‘Firmware’ field from BIOS to select the ‘UEFI x86_64’ option.

enter image description here

Then continue with the installation by clicking the green check mark at the top right ✅ Begin Installation

Customize configuration before install

Источник

Оцените статью
Adblock
detector