Installed Ubuntu 17.04 and now can't boot at all: Failed to open EFIBootgrubx64.efi - Not found
up vote
4
down vote
favorite
I installed Ubuntu 17.04 from a USB on my Acer Spin 5 which came with Windows 10. I made the choice of removing Win10 because earlier when I Dual-booted Ubuntu and Windows 10 I was not able to boot into Ubuntu after a Windows update.
Now when I start my computer it says
Default boot device missing or boot failed. Insert recovery media and hit any key, Then select "boot manager" to choose a new boot device or to boot recovery media
If entering this I only get the choice of booting with Windows Boot Manager which takes me back to this screen again, I'm also able to use my live-USB with Ubuntu and either load into Ubuntu live or install directly, both this options brings me back to the "Default boot device..." after a reboot. I've also tried boot repair with the following commands
sudo add-apt-repository ppa:yannubuntu/boot-repair && sudo apt-get update
sudo apt-get install -y boot-repair && boot-repair
But now after reboot I get
Failed to open EFIBootgrubx64.efi - Not found
Failed to load image EFIgrubx64.efi: Not found
start_image() returned Not found
Failed to open "EFIBOOTMicrosoftgrubx64.efi - Not found
Failed to load image EFIMicrosoftBOOTgrubx64.efi Not found
start_image() returned Not found
How do I solve this problem with not being able to get into Ubuntu?
Boot repair summary
How do I know which partition is my main partition?
Running
sudo fdisk -l
gives
Disk /dev/loop0: 1.5 GiB, 1553670144 bytes, 3034512 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: 238.5 GiB, 256060514304 bytes, 500118192 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: gpt
Disk identifier: F2E8B05E-6E0D-493F-9FF1-9F5D1195680B
Device Start End Sectors Size Type
/dev/sda1 2048 1050623 1048576 512M EFI System
/dev/sda2 1050624 500117503 499066880 238G Linux filesystem
Disk /dev/sdb: 3.7 GiB, 4002910208 bytes, 7818184 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: 0x1b571474
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 0 3142655 3142656 1.5G 0 Empty
/dev/sdb2 3118960 3123567 4608 2.3M ef EFI (FAT-12/16/32)
boot grub2 uefi acer
edited Nov 17 at 9:37
Zanna
48.9k13123234
asked Apr 25 '17 at 17:39
Littunen
2616
add a comment |
up vote
4
down vote
favorite
I installed Ubuntu 17.04 from a USB on my Acer Spin 5 which came with Windows 10. I made the choice of removing Win10 because earlier when I Dual-booted Ubuntu and Windows 10 I was not able to boot into Ubuntu after a Windows update.
Now when I start my computer it says
Default boot device missing or boot failed. Insert recovery media and hit any key, Then select "boot manager" to choose a new boot device or to boot recovery media
If entering this I only get the choice of booting with Windows Boot Manager which takes me back to this screen again, I'm also able to use my live-USB with Ubuntu and either load into Ubuntu live or install directly, both this options brings me back to the "Default boot device..." after a reboot. I've also tried boot repair with the following commands
sudo add-apt-repository ppa:yannubuntu/boot-repair && sudo apt-get update
sudo apt-get install -y boot-repair && boot-repair
But now after reboot I get
Failed to open EFIBootgrubx64.efi - Not found
Failed to load image EFIgrubx64.efi: Not found
start_image() returned Not found
Failed to open "EFIBOOTMicrosoftgrubx64.efi - Not found
Failed to load image EFIMicrosoftBOOTgrubx64.efi Not found
start_image() returned Not found
How do I solve this problem with not being able to get into Ubuntu?
Boot repair summary
How do I know which partition is my main partition?
Running
sudo fdisk -l
gives
Disk /dev/loop0: 1.5 GiB, 1553670144 bytes, 3034512 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: 238.5 GiB, 256060514304 bytes, 500118192 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: gpt
Disk identifier: F2E8B05E-6E0D-493F-9FF1-9F5D1195680B
Device Start End Sectors Size Type
/dev/sda1 2048 1050623 1048576 512M EFI System
/dev/sda2 1050624 500117503 499066880 238G Linux filesystem
Disk /dev/sdb: 3.7 GiB, 4002910208 bytes, 7818184 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: 0x1b571474
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 0 3142655 3142656 1.5G 0 Empty
/dev/sdb2 3118960 3123567 4608 2.3M ef EFI (FAT-12/16/32)
boot grub2 uefi acer
edited Nov 17 at 9:37
Zanna
48.9k13123234
asked Apr 25 '17 at 17:39
Littunen
2616
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.
– Rod Smith
Apr 26 '17 at 13:45
Edited the post, I have already used the "Recommended Repair" at this time
– Littunen
Apr 26 '17 at 14:19
Every Acer we have seen needs you to enable a UEFI Supervisory password and from within UEFI drill down to the grub/ubuntu .efi boot files in the ESP and enable trust. Details on password & trust setting: askubuntu.com/questions/597213/…
– oldfred
Apr 26 '17 at 14:47
This seems to be the solution @oldfred, I can now boot into Ubuntu. Do you mind putting it as an answer?
– Littunen
Apr 26 '17 at 17:03
add a comment |
up vote
4
down vote
favorite
up vote
4
down vote
favorite
I installed Ubuntu 17.04 from a USB on my Acer Spin 5 which came with Windows 10. I made the choice of removing Win10 because earlier when I Dual-booted Ubuntu and Windows 10 I was not able to boot into Ubuntu after a Windows update.
Now when I start my computer it says
Default boot device missing or boot failed. Insert recovery media and hit any key, Then select "boot manager" to choose a new boot device or to boot recovery media
If entering this I only get the choice of booting with Windows Boot Manager which takes me back to this screen again, I'm also able to use my live-USB with Ubuntu and either load into Ubuntu live or install directly, both this options brings me back to the "Default boot device..." after a reboot. I've also tried boot repair with the following commands
sudo add-apt-repository ppa:yannubuntu/boot-repair && sudo apt-get update
sudo apt-get install -y boot-repair && boot-repair
But now after reboot I get
Failed to open EFIBootgrubx64.efi - Not found
Failed to load image EFIgrubx64.efi: Not found
start_image() returned Not found
Failed to open "EFIBOOTMicrosoftgrubx64.efi - Not found
Failed to load image EFIMicrosoftBOOTgrubx64.efi Not found
start_image() returned Not found
How do I solve this problem with not being able to get into Ubuntu?
Boot repair summary
How do I know which partition is my main partition?
Running
sudo fdisk -l
gives
Disk /dev/loop0: 1.5 GiB, 1553670144 bytes, 3034512 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: 238.5 GiB, 256060514304 bytes, 500118192 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: gpt
Disk identifier: F2E8B05E-6E0D-493F-9FF1-9F5D1195680B
Device Start End Sectors Size Type
/dev/sda1 2048 1050623 1048576 512M EFI System
/dev/sda2 1050624 500117503 499066880 238G Linux filesystem
Disk /dev/sdb: 3.7 GiB, 4002910208 bytes, 7818184 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: 0x1b571474
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 0 3142655 3142656 1.5G 0 Empty
/dev/sdb2 3118960 3123567 4608 2.3M ef EFI (FAT-12/16/32)
boot grub2 uefi acer
edited Nov 17 at 9:37
Zanna
48.9k13123234
asked Apr 25 '17 at 17:39
Littunen
2616
I installed Ubuntu 17.04 from a USB on my Acer Spin 5 which came with Windows 10. I made the choice of removing Win10 because earlier when I Dual-booted Ubuntu and Windows 10 I was not able to boot into Ubuntu after a Windows update.
Now when I start my computer it says
Default boot device missing or boot failed. Insert recovery media and hit any key, Then select "boot manager" to choose a new boot device or to boot recovery media
If entering this I only get the choice of booting with Windows Boot Manager which takes me back to this screen again, I'm also able to use my live-USB with Ubuntu and either load into Ubuntu live or install directly, both this options brings me back to the "Default boot device..." after a reboot. I've also tried boot repair with the following commands
sudo add-apt-repository ppa:yannubuntu/boot-repair && sudo apt-get update
sudo apt-get install -y boot-repair && boot-repair
But now after reboot I get
Failed to open EFIBootgrubx64.efi - Not found
Failed to load image EFIgrubx64.efi: Not found
start_image() returned Not found
Failed to open "EFIBOOTMicrosoftgrubx64.efi - Not found
Failed to load image EFIMicrosoftBOOTgrubx64.efi Not found
start_image() returned Not found
How do I solve this problem with not being able to get into Ubuntu?
Boot repair summary
How do I know which partition is my main partition?
Running
sudo fdisk -l
gives
Disk /dev/loop0: 1.5 GiB, 1553670144 bytes, 3034512 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: 238.5 GiB, 256060514304 bytes, 500118192 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: gpt
Disk identifier: F2E8B05E-6E0D-493F-9FF1-9F5D1195680B
Device Start End Sectors Size Type
/dev/sda1 2048 1050623 1048576 512M EFI System
/dev/sda2 1050624 500117503 499066880 238G Linux filesystem
Disk /dev/sdb: 3.7 GiB, 4002910208 bytes, 7818184 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: 0x1b571474
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 0 3142655 3142656 1.5G 0 Empty
/dev/sdb2 3118960 3123567 4608 2.3M ef EFI (FAT-12/16/32)
boot grub2 uefi acer
boot grub2 uefi acer
edited Nov 17 at 9:37
Zanna
48.9k13123234
asked Apr 25 '17 at 17:39
Littunen
2616
edited Nov 17 at 9:37
Zanna
48.9k13123234
asked Apr 25 '17 at 17:39
Littunen
2616
edited Nov 17 at 9:37
Zanna
48.9k13123234
edited Nov 17 at 9:37
Zanna
48.9k13123234
edited Nov 17 at 9:37
Zanna
48.9k13123234
48.9k13123234
asked Apr 25 '17 at 17:39
Littunen
2616
asked Apr 25 '17 at 17:39
Littunen
2616
asked Apr 25 '17 at 17:39
Littunen
2616
2616
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.
– Rod Smith
Apr 26 '17 at 13:45
Edited the post, I have already used the "Recommended Repair" at this time
– Littunen
Apr 26 '17 at 14:19
Every Acer we have seen needs you to enable a UEFI Supervisory password and from within UEFI drill down to the grub/ubuntu .efi boot files in the ESP and enable trust. Details on password & trust setting: askubuntu.com/questions/597213/…
– oldfred
Apr 26 '17 at 14:47
This seems to be the solution @oldfred, I can now boot into Ubuntu. Do you mind putting it as an answer?
– Littunen
Apr 26 '17 at 17:03
add a comment |
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.
– Rod Smith
Apr 26 '17 at 13:45
Edited the post, I have already used the "Recommended Repair" at this time
– Littunen
Apr 26 '17 at 14:19
Every Acer we have seen needs you to enable a UEFI Supervisory password and from within UEFI drill down to the grub/ubuntu .efi boot files in the ESP and enable trust. Details on password & trust setting: askubuntu.com/questions/597213/…
– oldfred
Apr 26 '17 at 14:47
This seems to be the solution @oldfred, I can now boot into Ubuntu. Do you mind putting it as an answer?
– Littunen
Apr 26 '17 at 17:03
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.
– Rod Smith
Apr 26 '17 at 13:45
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.
– Rod Smith
Apr 26 '17 at 13:45
Edited the post, I have already used the "Recommended Repair" at this time
– Littunen
Apr 26 '17 at 14:19
Edited the post, I have already used the "Recommended Repair" at this time
– Littunen
Apr 26 '17 at 14:19
Every Acer we have seen needs you to enable a UEFI Supervisory password and from within UEFI drill down to the grub/ubuntu .efi boot files in the ESP and enable trust. Details on password & trust setting: askubuntu.com/questions/597213/…
– oldfred
Apr 26 '17 at 14:47
Every Acer we have seen needs you to enable a UEFI Supervisory password and from within UEFI drill down to the grub/ubuntu .efi boot files in the ESP and enable trust. Details on password & trust setting: askubuntu.com/questions/597213/…
– oldfred
Apr 26 '17 at 14:47
This seems to be the solution @oldfred, I can now boot into Ubuntu. Do you mind putting it as an answer?
– Littunen
Apr 26 '17 at 17:03
This seems to be the solution @oldfred, I can now boot into Ubuntu. Do you mind putting it as an answer?
– Littunen
Apr 26 '17 at 17:03
add a comment |
1 Answer
1
active
oldest
votes
up vote
5
down vote
accepted
Every Acer we have seen needs you to enable a UEFI Supervisory password and from within UEFI drill down to the grub/ubuntu .efi boot files in the ESP and enable trust.
This seems to be unique to Acer.
But better than many other systems that require working around limits built into UEFI to only Boot Windows.
More details on password & trust settings:
http://askubuntu.com/questions/597213/bootable-device-not-found-after-clean-install-of-ubuntu-14-04-uefi
Acer video on setting Supervisory Password.
edited Oct 11 '17 at 7:32
Zanna
48.9k13123234
answered Apr 26 '17 at 17:55
oldfred
7,49421221
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
5
down vote
accepted
Every Acer we have seen needs you to enable a UEFI Supervisory password and from within UEFI drill down to the grub/ubuntu .efi boot files in the ESP and enable trust.
This seems to be unique to Acer.
But better than many other systems that require working around limits built into UEFI to only Boot Windows.
More details on password & trust settings:
http://askubuntu.com/questions/597213/bootable-device-not-found-after-clean-install-of-ubuntu-14-04-uefi
Acer video on setting Supervisory Password.
edited Oct 11 '17 at 7:32
Zanna
48.9k13123234
answered Apr 26 '17 at 17:55
oldfred
7,49421221
add a comment |
up vote
5
down vote
accepted
Every Acer we have seen needs you to enable a UEFI Supervisory password and from within UEFI drill down to the grub/ubuntu .efi boot files in the ESP and enable trust.
This seems to be unique to Acer.
But better than many other systems that require working around limits built into UEFI to only Boot Windows.
More details on password & trust settings:
http://askubuntu.com/questions/597213/bootable-device-not-found-after-clean-install-of-ubuntu-14-04-uefi
Acer video on setting Supervisory Password.
edited Oct 11 '17 at 7:32
Zanna
48.9k13123234
answered Apr 26 '17 at 17:55
oldfred
7,49421221
add a comment |
up vote
5
down vote
accepted
up vote
5
down vote
accepted
Every Acer we have seen needs you to enable a UEFI Supervisory password and from within UEFI drill down to the grub/ubuntu .efi boot files in the ESP and enable trust.
This seems to be unique to Acer.
But better than many other systems that require working around limits built into UEFI to only Boot Windows.
More details on password & trust settings:
http://askubuntu.com/questions/597213/bootable-device-not-found-after-clean-install-of-ubuntu-14-04-uefi
Acer video on setting Supervisory Password.
edited Oct 11 '17 at 7:32
Zanna
48.9k13123234
answered Apr 26 '17 at 17:55
oldfred
7,49421221
Every Acer we have seen needs you to enable a UEFI Supervisory password and from within UEFI drill down to the grub/ubuntu .efi boot files in the ESP and enable trust.
This seems to be unique to Acer.
But better than many other systems that require working around limits built into UEFI to only Boot Windows.
More details on password & trust settings:
http://askubuntu.com/questions/597213/bootable-device-not-found-after-clean-install-of-ubuntu-14-04-uefi
Acer video on setting Supervisory Password.
edited Oct 11 '17 at 7:32
Zanna
48.9k13123234
answered Apr 26 '17 at 17:55
oldfred
7,49421221
edited Oct 11 '17 at 7:32
Zanna
48.9k13123234
edited Oct 11 '17 at 7:32
Zanna
48.9k13123234
edited Oct 11 '17 at 7:32
Zanna
48.9k13123234
48.9k13123234
answered Apr 26 '17 at 17:55
oldfred
7,49421221
answered Apr 26 '17 at 17:55
oldfred
7,49421221
answered Apr 26 '17 at 17:55
oldfred
7,49421221
7,49421221
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f908854%2finstalled-ubuntu-17-04-and-now-cant-boot-at-all-failed-to-open-efi-boot-grubx%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
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.
– Rod Smith
Apr 26 '17 at 13:45
Edited the post, I have already used the "Recommended Repair" at this time
– Littunen
Apr 26 '17 at 14:19
Every Acer we have seen needs you to enable a UEFI Supervisory password and from within UEFI drill down to the grub/ubuntu .efi boot files in the ESP and enable trust. Details on password & trust setting: askubuntu.com/questions/597213/…
– oldfred
Apr 26 '17 at 14:47
This seems to be the solution @oldfred, I can now boot into Ubuntu. Do you mind putting it as an answer?
– Littunen
Apr 26 '17 at 17:03