Can't get rid of «Default Boot Device Missing» message on boot
I recently bought an Acer Swift 3 ultrabook preloaded with Windows 10, which I wiped out to install Ubuntu 16.04.1 in single-boot. In my case installs are generally a breeze, but not this time. Long story short, I ended up with a «No Bootable Device» message on boot. I fixed the problem with Boot-repair. The ultrabook now works perfectly.
After the repair, however, I kept getting at boot time a blue window with this message : « Default Boot Device Missing or Boot failed. Insert recovery media and hit any key ». Hitting a key would lead me to a Boot Manager with only one entry : 1- Windows boot manager. Selecting it would then get me to Grub, with the usual Ubuntu option.
I search the net, found this post Bootable device not found after clean install of Ubuntu 14.04 UEFI, modified the BIOS-settings as instructed («Select an UEFI file as trusted for executing» and so on), to no avail. The blue rectangle just won’t go away at boot. The only change is that there is now a Ubuntu entry in the Windows Boot manager.
Secure Boot is enabled.
The boot priority order is :
1- EFI File Boot 0 : Ubuntu
2- Windows Boot Manager
3- HDD : HF S256G39TND-N210A
By the way, when I modified the BIOS-Settings in the Security tab, I found three .efi files in HDDO - EFI - ubuntu. I selected the first one (as suggested), and left the other two untouched: grubx64.efi and MokManager.efi.
I could ot course reinstall Ubuntu from scratch, but since I've already installed a whole bunch of applications, I’d rather find a workaround.
The output of sudo efibootmgr -v can be found here:
output
boot grub2 uefi
edited Apr 13 '17 at 12:24
Community♦
1
asked Nov 25 '16 at 17:52
NovemberSnowNovemberSnow
6419
add a comment |
I recently bought an Acer Swift 3 ultrabook preloaded with Windows 10, which I wiped out to install Ubuntu 16.04.1 in single-boot. In my case installs are generally a breeze, but not this time. Long story short, I ended up with a «No Bootable Device» message on boot. I fixed the problem with Boot-repair. The ultrabook now works perfectly.
After the repair, however, I kept getting at boot time a blue window with this message : « Default Boot Device Missing or Boot failed. Insert recovery media and hit any key ». Hitting a key would lead me to a Boot Manager with only one entry : 1- Windows boot manager. Selecting it would then get me to Grub, with the usual Ubuntu option.
I search the net, found this post Bootable device not found after clean install of Ubuntu 14.04 UEFI, modified the BIOS-settings as instructed («Select an UEFI file as trusted for executing» and so on), to no avail. The blue rectangle just won’t go away at boot. The only change is that there is now a Ubuntu entry in the Windows Boot manager.
Secure Boot is enabled.
The boot priority order is :
1- EFI File Boot 0 : Ubuntu
2- Windows Boot Manager
3- HDD : HF S256G39TND-N210A
By the way, when I modified the BIOS-Settings in the Security tab, I found three .efi files in HDDO - EFI - ubuntu. I selected the first one (as suggested), and left the other two untouched: grubx64.efi and MokManager.efi.
I could ot course reinstall Ubuntu from scratch, but since I've already installed a whole bunch of applications, I’d rather find a workaround.
The output of sudo efibootmgr -v can be found here:
output
boot grub2 uefi
edited Apr 13 '17 at 12:24
Community♦
1
asked Nov 25 '16 at 17:52
NovemberSnowNovemberSnow
6419
1
Please typesudo efibootmgr -vin a Terminal window in Ubuntu. You should then either edit your question to cut-and-paste the output there, adding four spaces to the start of each line; or post the output to a pastebin site and post the URL to your document here.
– Rod Smith
Nov 25 '16 at 20:57
add a comment |
I recently bought an Acer Swift 3 ultrabook preloaded with Windows 10, which I wiped out to install Ubuntu 16.04.1 in single-boot. In my case installs are generally a breeze, but not this time. Long story short, I ended up with a «No Bootable Device» message on boot. I fixed the problem with Boot-repair. The ultrabook now works perfectly.
After the repair, however, I kept getting at boot time a blue window with this message : « Default Boot Device Missing or Boot failed. Insert recovery media and hit any key ». Hitting a key would lead me to a Boot Manager with only one entry : 1- Windows boot manager. Selecting it would then get me to Grub, with the usual Ubuntu option.
I search the net, found this post Bootable device not found after clean install of Ubuntu 14.04 UEFI, modified the BIOS-settings as instructed («Select an UEFI file as trusted for executing» and so on), to no avail. The blue rectangle just won’t go away at boot. The only change is that there is now a Ubuntu entry in the Windows Boot manager.
Secure Boot is enabled.
The boot priority order is :
1- EFI File Boot 0 : Ubuntu
2- Windows Boot Manager
3- HDD : HF S256G39TND-N210A
By the way, when I modified the BIOS-Settings in the Security tab, I found three .efi files in HDDO - EFI - ubuntu. I selected the first one (as suggested), and left the other two untouched: grubx64.efi and MokManager.efi.
I could ot course reinstall Ubuntu from scratch, but since I've already installed a whole bunch of applications, I’d rather find a workaround.
The output of sudo efibootmgr -v can be found here:
output
boot grub2 uefi
edited Apr 13 '17 at 12:24
Community♦
1
asked Nov 25 '16 at 17:52
NovemberSnowNovemberSnow
6419
I recently bought an Acer Swift 3 ultrabook preloaded with Windows 10, which I wiped out to install Ubuntu 16.04.1 in single-boot. In my case installs are generally a breeze, but not this time. Long story short, I ended up with a «No Bootable Device» message on boot. I fixed the problem with Boot-repair. The ultrabook now works perfectly.
After the repair, however, I kept getting at boot time a blue window with this message : « Default Boot Device Missing or Boot failed. Insert recovery media and hit any key ». Hitting a key would lead me to a Boot Manager with only one entry : 1- Windows boot manager. Selecting it would then get me to Grub, with the usual Ubuntu option.
I search the net, found this post Bootable device not found after clean install of Ubuntu 14.04 UEFI, modified the BIOS-settings as instructed («Select an UEFI file as trusted for executing» and so on), to no avail. The blue rectangle just won’t go away at boot. The only change is that there is now a Ubuntu entry in the Windows Boot manager.
Secure Boot is enabled.
The boot priority order is :
1- EFI File Boot 0 : Ubuntu
2- Windows Boot Manager
3- HDD : HF S256G39TND-N210A
By the way, when I modified the BIOS-Settings in the Security tab, I found three .efi files in HDDO - EFI - ubuntu. I selected the first one (as suggested), and left the other two untouched: grubx64.efi and MokManager.efi.
I could ot course reinstall Ubuntu from scratch, but since I've already installed a whole bunch of applications, I’d rather find a workaround.
The output of sudo efibootmgr -v can be found here:
output
boot grub2 uefi
boot grub2 uefi
edited Apr 13 '17 at 12:24
Community♦
1
asked Nov 25 '16 at 17:52
NovemberSnowNovemberSnow
6419
edited Apr 13 '17 at 12:24
Community♦
1
asked Nov 25 '16 at 17:52
NovemberSnowNovemberSnow
6419
edited Apr 13 '17 at 12:24
Community♦
1
edited Apr 13 '17 at 12:24
Community♦
1
edited Apr 13 '17 at 12:24
Community♦
1
1
asked Nov 25 '16 at 17:52
NovemberSnowNovemberSnow
6419
asked Nov 25 '16 at 17:52
NovemberSnowNovemberSnow
6419
asked Nov 25 '16 at 17:52
NovemberSnowNovemberSnow
6419
6419
1
Please typesudo efibootmgr -vin a Terminal window in Ubuntu. You should then either edit your question to cut-and-paste the output there, adding four spaces to the start of each line; or post the output to a pastebin site and post the URL to your document here.
– Rod Smith
Nov 25 '16 at 20:57
add a comment |
1
Please typesudo efibootmgr -vin a Terminal window in Ubuntu. You should then either edit your question to cut-and-paste the output there, adding four spaces to the start of each line; or post the output to a pastebin site and post the URL to your document here.
– Rod Smith
Nov 25 '16 at 20:57
1
1
Please type
sudo efibootmgr -v in a Terminal window in Ubuntu. You should then either edit your question to cut-and-paste the output there, adding four spaces to the start of each line; or post the output to a pastebin site and post the URL to your document here.– Rod Smith
Nov 25 '16 at 20:57
Please type
sudo efibootmgr -v in a Terminal window in Ubuntu. You should then either edit your question to cut-and-paste the output there, adding four spaces to the start of each line; or post the output to a pastebin site and post the URL to your document here.– Rod Smith
Nov 25 '16 at 20:57
add a comment |
2 Answers
2
active
oldest
votes
The solution to my problem was found by user oldfred, from the Ubuntu forums.
Can't get rid of «Default Boot Device Missing» message on boot
From the output of sudo efibootmgr -v
he deduced that:
It looks like your default UEFI boot entry 0001 is fwupx64.efi which is the grub menu entry to get into UEFI.
If you have secure boot on you want to boot shimx64.efi which is 0002 but shown as unknown device.
On his advice I went back into UEFI and set "trust" and a label on the shimx64.efi file.
Et voilà!
answered Dec 10 '16 at 0:06
NovemberSnowNovemberSnow
6419
add a comment |
I am giving you two links with answers for your Swift 3 troubles.
How to get GRUB boot option?
see both the answers in this question and the comments as well.
there are two parts to this.
Part 1 - getting Ubuntu with a mainline 4.12 and above kernel and installing it
part 2 - enabling secure boot, adding your efi file as secure, disabling secure boot, and making grub come on top of the boot list.
good luck ;)
answered Jul 29 '17 at 5:19
Ubuntu NutCrackerUbuntu NutCracker
126
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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%2f853565%2fcant-get-rid-of-default-boot-device-missing-message-on-boot%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
The solution to my problem was found by user oldfred, from the Ubuntu forums.
Can't get rid of «Default Boot Device Missing» message on boot
From the output of sudo efibootmgr -v
he deduced that:
It looks like your default UEFI boot entry 0001 is fwupx64.efi which is the grub menu entry to get into UEFI.
If you have secure boot on you want to boot shimx64.efi which is 0002 but shown as unknown device.
On his advice I went back into UEFI and set "trust" and a label on the shimx64.efi file.
Et voilà!
answered Dec 10 '16 at 0:06
NovemberSnowNovemberSnow
6419
add a comment |
The solution to my problem was found by user oldfred, from the Ubuntu forums.
Can't get rid of «Default Boot Device Missing» message on boot
From the output of sudo efibootmgr -v
he deduced that:
It looks like your default UEFI boot entry 0001 is fwupx64.efi which is the grub menu entry to get into UEFI.
If you have secure boot on you want to boot shimx64.efi which is 0002 but shown as unknown device.
On his advice I went back into UEFI and set "trust" and a label on the shimx64.efi file.
Et voilà!
answered Dec 10 '16 at 0:06
NovemberSnowNovemberSnow
6419
add a comment |
The solution to my problem was found by user oldfred, from the Ubuntu forums.
Can't get rid of «Default Boot Device Missing» message on boot
From the output of sudo efibootmgr -v
he deduced that:
It looks like your default UEFI boot entry 0001 is fwupx64.efi which is the grub menu entry to get into UEFI.
If you have secure boot on you want to boot shimx64.efi which is 0002 but shown as unknown device.
On his advice I went back into UEFI and set "trust" and a label on the shimx64.efi file.
Et voilà!
answered Dec 10 '16 at 0:06
NovemberSnowNovemberSnow
6419
The solution to my problem was found by user oldfred, from the Ubuntu forums.
Can't get rid of «Default Boot Device Missing» message on boot
From the output of sudo efibootmgr -v
he deduced that:
It looks like your default UEFI boot entry 0001 is fwupx64.efi which is the grub menu entry to get into UEFI.
If you have secure boot on you want to boot shimx64.efi which is 0002 but shown as unknown device.
On his advice I went back into UEFI and set "trust" and a label on the shimx64.efi file.
Et voilà!
answered Dec 10 '16 at 0:06
NovemberSnowNovemberSnow
6419
answered Dec 10 '16 at 0:06
NovemberSnowNovemberSnow
6419
answered Dec 10 '16 at 0:06
NovemberSnowNovemberSnow
6419
answered Dec 10 '16 at 0:06
NovemberSnowNovemberSnow
6419
6419
add a comment |
add a comment |
I am giving you two links with answers for your Swift 3 troubles.
How to get GRUB boot option?
see both the answers in this question and the comments as well.
there are two parts to this.
Part 1 - getting Ubuntu with a mainline 4.12 and above kernel and installing it
part 2 - enabling secure boot, adding your efi file as secure, disabling secure boot, and making grub come on top of the boot list.
good luck ;)
answered Jul 29 '17 at 5:19
Ubuntu NutCrackerUbuntu NutCracker
126
add a comment |
I am giving you two links with answers for your Swift 3 troubles.
How to get GRUB boot option?
see both the answers in this question and the comments as well.
there are two parts to this.
Part 1 - getting Ubuntu with a mainline 4.12 and above kernel and installing it
part 2 - enabling secure boot, adding your efi file as secure, disabling secure boot, and making grub come on top of the boot list.
good luck ;)
answered Jul 29 '17 at 5:19
Ubuntu NutCrackerUbuntu NutCracker
126
add a comment |
I am giving you two links with answers for your Swift 3 troubles.
How to get GRUB boot option?
see both the answers in this question and the comments as well.
there are two parts to this.
Part 1 - getting Ubuntu with a mainline 4.12 and above kernel and installing it
part 2 - enabling secure boot, adding your efi file as secure, disabling secure boot, and making grub come on top of the boot list.
good luck ;)
answered Jul 29 '17 at 5:19
Ubuntu NutCrackerUbuntu NutCracker
126
I am giving you two links with answers for your Swift 3 troubles.
How to get GRUB boot option?
see both the answers in this question and the comments as well.
there are two parts to this.
Part 1 - getting Ubuntu with a mainline 4.12 and above kernel and installing it
part 2 - enabling secure boot, adding your efi file as secure, disabling secure boot, and making grub come on top of the boot list.
good luck ;)
answered Jul 29 '17 at 5:19
Ubuntu NutCrackerUbuntu NutCracker
126
answered Jul 29 '17 at 5:19
Ubuntu NutCrackerUbuntu NutCracker
126
answered Jul 29 '17 at 5:19
Ubuntu NutCrackerUbuntu NutCracker
126
answered Jul 29 '17 at 5:19
Ubuntu NutCrackerUbuntu NutCracker
126
126
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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%2f853565%2fcant-get-rid-of-default-boot-device-missing-message-on-boot%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
1
Please type
sudo efibootmgr -vin a Terminal window in Ubuntu. You should then either edit your question to cut-and-paste the output there, adding four spaces to the start of each line; or post the output to a pastebin site and post the URL to your document here.– Rod Smith
Nov 25 '16 at 20:57