Messed up boot - System BootOrder not foundSystem Boot Order not found (Secure boot is not enabled)Installing...
How would vampires avoid contracting diseases?
Terry Pratchett book with a lawyer dragon and sheep
Is English unusual in having no second person plural form?
How quality assurance engineers test calculations?
What happens to unproductive professors?
Does Multiverse exist in MCU?
Graduate student with abysmal English writing skills, how to help
Why are they 'nude photos'?
How can I get a player to accept that they should stop trying to pull stunts without thinking them through first?
When I press the space bar it deletes the letters after it
Placing text inside a loop
Extract string from each line of a file
Is there any word for "disobedience to God"?
Is a request to book a business flight ticket for a graduate student an unreasonable one?
Is "I do not want you to go nowhere" a case of "DOUBLE-NEGATIVES" as claimed by Grammarly?
Was I subtly told to resign?
Can the Mage Hand cantrip be used to trip an enemy who is running away?
LED glows slightly during soldering
Would a non-attacking Barbarian's rage end the same turn he started it?
Are there any balance issues in allowing two half-feats to be taken without the Ability Score Increase instead of a feat?
What does the phrase "head down the rat's hole" mean here?
How were Martello towers supposed to work?
What's the point of having a RAID 1 configuration over incremental backups to a secondary drive?
Shortest hex dumping program
Messed up boot - System BootOrder not found
System Boot Order not found (Secure boot is not enabled)Installing Linux on acer travelmate 8573TGRestore EFI boot partitionBoot-Repair hangs, possible alternative?How to boot via grub2 rescue promt on UEFI system?UEFI not recognising EFI partition: no booting optionsGrub doesn't work after Arch install on an EFI system, how to fix/reinstall it?EFI can't to boot LinuxUnable to mount Mac's EFI partition from Ubuntu Live USBCan't boot Ubuntu 19.04 or Ubuntu19.04 LiveUSB after enrolling MOKBoot repair disk on mint live usb
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I am attempting to install Ubuntu 17.10.
What's happening:
- I turn on PC
- Get a message that I can't read in time, something along the lines of: System BootOrder not found. Initializing defaults.
- PC restarts
- Endless loop
What I've tried:
- Complete fresh install with Ubuntu live usb
- Boot in with live usb and use gparted to try and set some stuff up
- boot-info - http://paste.ubuntu.com/p/gSSdkpVfxt/
What I done leading up to this:
- PC was originally a Windows 10 install
- I removed Windows 10 to try Arch Linux
- I am now trying to install Ubuntu deleting my old Arch Linux installation
I believe I've messed up my booting and I am completely unsure how to fix it. Boot info asks me to change the path for the .efi file but I can't figure out how to do that. Running ThinkPad 470s.
ubuntu boot uefi
bumped to the homepage by Community♦ 20 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I am attempting to install Ubuntu 17.10.
What's happening:
- I turn on PC
- Get a message that I can't read in time, something along the lines of: System BootOrder not found. Initializing defaults.
- PC restarts
- Endless loop
What I've tried:
- Complete fresh install with Ubuntu live usb
- Boot in with live usb and use gparted to try and set some stuff up
- boot-info - http://paste.ubuntu.com/p/gSSdkpVfxt/
What I done leading up to this:
- PC was originally a Windows 10 install
- I removed Windows 10 to try Arch Linux
- I am now trying to install Ubuntu deleting my old Arch Linux installation
I believe I've messed up my booting and I am completely unsure how to fix it. Boot info asks me to change the path for the .efi file but I can't figure out how to do that. Running ThinkPad 470s.
ubuntu boot uefi
bumped to the homepage by Community♦ 20 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
1
This seems to be a reoccurring issue: askubuntu.com/questions/1006545/… unix.stackexchange.com/questions/183421/… askubuntu.com/questions/1005034/… bugzilla.redhat.com/show_bug.cgi?id=1512410
– jdwolf
May 13 '18 at 9:47
It does appear manually selecting Ubuntu from the UEFI menu helps some people. But I think this is because in those cases its skipping GRUB and using EFI-stub instead and GRUB is the culprit here.
– jdwolf
May 13 '18 at 9:48
Yeah, I don't even see Ubuntu in the UEFI menu unfortunately. Thanks for the links, this is going to take some deep digging it seems.
– notvita
May 13 '18 at 11:05
2
I managed to solve this by following the answer posted here Thanks
– notvita
May 13 '18 at 11:19
add a comment |
I am attempting to install Ubuntu 17.10.
What's happening:
- I turn on PC
- Get a message that I can't read in time, something along the lines of: System BootOrder not found. Initializing defaults.
- PC restarts
- Endless loop
What I've tried:
- Complete fresh install with Ubuntu live usb
- Boot in with live usb and use gparted to try and set some stuff up
- boot-info - http://paste.ubuntu.com/p/gSSdkpVfxt/
What I done leading up to this:
- PC was originally a Windows 10 install
- I removed Windows 10 to try Arch Linux
- I am now trying to install Ubuntu deleting my old Arch Linux installation
I believe I've messed up my booting and I am completely unsure how to fix it. Boot info asks me to change the path for the .efi file but I can't figure out how to do that. Running ThinkPad 470s.
ubuntu boot uefi
I am attempting to install Ubuntu 17.10.
What's happening:
- I turn on PC
- Get a message that I can't read in time, something along the lines of: System BootOrder not found. Initializing defaults.
- PC restarts
- Endless loop
What I've tried:
- Complete fresh install with Ubuntu live usb
- Boot in with live usb and use gparted to try and set some stuff up
- boot-info - http://paste.ubuntu.com/p/gSSdkpVfxt/
What I done leading up to this:
- PC was originally a Windows 10 install
- I removed Windows 10 to try Arch Linux
- I am now trying to install Ubuntu deleting my old Arch Linux installation
I believe I've messed up my booting and I am completely unsure how to fix it. Boot info asks me to change the path for the .efi file but I can't figure out how to do that. Running ThinkPad 470s.
ubuntu boot uefi
ubuntu boot uefi
edited Feb 9 at 18:42
Rui F Ribeiro
40.8k16 gold badges91 silver badges152 bronze badges
40.8k16 gold badges91 silver badges152 bronze badges
asked May 13 '18 at 7:28
notvitanotvita
111 gold badge1 silver badge3 bronze badges
111 gold badge1 silver badge3 bronze badges
bumped to the homepage by Community♦ 20 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 20 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
1
This seems to be a reoccurring issue: askubuntu.com/questions/1006545/… unix.stackexchange.com/questions/183421/… askubuntu.com/questions/1005034/… bugzilla.redhat.com/show_bug.cgi?id=1512410
– jdwolf
May 13 '18 at 9:47
It does appear manually selecting Ubuntu from the UEFI menu helps some people. But I think this is because in those cases its skipping GRUB and using EFI-stub instead and GRUB is the culprit here.
– jdwolf
May 13 '18 at 9:48
Yeah, I don't even see Ubuntu in the UEFI menu unfortunately. Thanks for the links, this is going to take some deep digging it seems.
– notvita
May 13 '18 at 11:05
2
I managed to solve this by following the answer posted here Thanks
– notvita
May 13 '18 at 11:19
add a comment |
1
This seems to be a reoccurring issue: askubuntu.com/questions/1006545/… unix.stackexchange.com/questions/183421/… askubuntu.com/questions/1005034/… bugzilla.redhat.com/show_bug.cgi?id=1512410
– jdwolf
May 13 '18 at 9:47
It does appear manually selecting Ubuntu from the UEFI menu helps some people. But I think this is because in those cases its skipping GRUB and using EFI-stub instead and GRUB is the culprit here.
– jdwolf
May 13 '18 at 9:48
Yeah, I don't even see Ubuntu in the UEFI menu unfortunately. Thanks for the links, this is going to take some deep digging it seems.
– notvita
May 13 '18 at 11:05
2
I managed to solve this by following the answer posted here Thanks
– notvita
May 13 '18 at 11:19
1
1
This seems to be a reoccurring issue: askubuntu.com/questions/1006545/… unix.stackexchange.com/questions/183421/… askubuntu.com/questions/1005034/… bugzilla.redhat.com/show_bug.cgi?id=1512410
– jdwolf
May 13 '18 at 9:47
This seems to be a reoccurring issue: askubuntu.com/questions/1006545/… unix.stackexchange.com/questions/183421/… askubuntu.com/questions/1005034/… bugzilla.redhat.com/show_bug.cgi?id=1512410
– jdwolf
May 13 '18 at 9:47
It does appear manually selecting Ubuntu from the UEFI menu helps some people. But I think this is because in those cases its skipping GRUB and using EFI-stub instead and GRUB is the culprit here.
– jdwolf
May 13 '18 at 9:48
It does appear manually selecting Ubuntu from the UEFI menu helps some people. But I think this is because in those cases its skipping GRUB and using EFI-stub instead and GRUB is the culprit here.
– jdwolf
May 13 '18 at 9:48
Yeah, I don't even see Ubuntu in the UEFI menu unfortunately. Thanks for the links, this is going to take some deep digging it seems.
– notvita
May 13 '18 at 11:05
Yeah, I don't even see Ubuntu in the UEFI menu unfortunately. Thanks for the links, this is going to take some deep digging it seems.
– notvita
May 13 '18 at 11:05
2
2
I managed to solve this by following the answer posted here Thanks
– notvita
May 13 '18 at 11:19
I managed to solve this by following the answer posted here Thanks
– notvita
May 13 '18 at 11:19
add a comment |
1 Answer
1
active
oldest
votes
BootOrder
is one of the UEFI boot variables, stored in NVRAM along with other firmware configuration (what used to be "BIOS settings").
In Linux, you can use efibootmgr -v
to view the boot variables.
Example:
# efibootmgr -v
BootCurrent: 0001
Timeout: 6 seconds
BootOrder: 0001,0002,0000,0003,0004,0005,0006
Boot0000* debian HD(1,GPT,4fb8aadb-9507-44b5-8cab-a052a0091e2b,0x800,0x100000)/File(EFIDEBIANGRUBX64.EFI)
Boot0001* rEFInd Boot Manager HD(1,GPT,4fb8aadb-9507-44b5-8cab-a052a0091e2b,0x800,0x100000)/File(EFIREFINDREFIND_X64.EFI)
Boot0002* UEFI: IP4 Realtek PCIe GBE Family Controller PciRoot(0x0)/Pci(0x1c,0x2)/Pci(0x0,0x0)/MAC(107b447ad398,0)/IPv4(0.0.0.0:0<->0.0.0.0:0,0,0)..BO
Boot0003 UEFI Shell HD(1,GPT,4fb8aadb-9507-44b5-8cab-a052a0091e2b,0x800,0x100000)/File(EFItoolsshell.efi)
Boot0004* UEFI:CD/DVD Drive BBS(129,,0x0)
Boot0005* UEFI:Removable Device BBS(130,,0x0)
Boot0006* UEFI:Network Device BBS(131,,0x0)
Here I have a Debian 9 system, with two bootloaders installed: the Debian default GRUB, and the more visually-oriented rEFInd, which I've set as the primary bootloader. I also have the UEFI Shell as a boot option, although that option is currently disabled.
Note that the BootOrder lists the order in which the other BootNNNN options will be tried.
You might have a BootNNNN line that's left over from the Windows or Arch installation. Since the bootloader file it refers to no longer exists, it is going to be useless. You can use efibootmgr -B -b NNNN
to delete it: just replace NNNN with the actual BootNNNN number you wish to delete.
Thanks for your time, but I just managed to solve the issue
– notvita
May 13 '18 at 11:19
No problem. However, please consider documenting your solution by writing an answer yourself, so that your solution may help others with a similar problem.
– telcoM
May 13 '18 at 11:30
I attempted to but it just got added as a comment on my OP. I followed the exact steps listed in the link for anyone else that runs into this issue!
– notvita
May 13 '18 at 11:35
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2funix.stackexchange.com%2fquestions%2f443508%2fmessed-up-boot-system-bootorder-not-found%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
BootOrder
is one of the UEFI boot variables, stored in NVRAM along with other firmware configuration (what used to be "BIOS settings").
In Linux, you can use efibootmgr -v
to view the boot variables.
Example:
# efibootmgr -v
BootCurrent: 0001
Timeout: 6 seconds
BootOrder: 0001,0002,0000,0003,0004,0005,0006
Boot0000* debian HD(1,GPT,4fb8aadb-9507-44b5-8cab-a052a0091e2b,0x800,0x100000)/File(EFIDEBIANGRUBX64.EFI)
Boot0001* rEFInd Boot Manager HD(1,GPT,4fb8aadb-9507-44b5-8cab-a052a0091e2b,0x800,0x100000)/File(EFIREFINDREFIND_X64.EFI)
Boot0002* UEFI: IP4 Realtek PCIe GBE Family Controller PciRoot(0x0)/Pci(0x1c,0x2)/Pci(0x0,0x0)/MAC(107b447ad398,0)/IPv4(0.0.0.0:0<->0.0.0.0:0,0,0)..BO
Boot0003 UEFI Shell HD(1,GPT,4fb8aadb-9507-44b5-8cab-a052a0091e2b,0x800,0x100000)/File(EFItoolsshell.efi)
Boot0004* UEFI:CD/DVD Drive BBS(129,,0x0)
Boot0005* UEFI:Removable Device BBS(130,,0x0)
Boot0006* UEFI:Network Device BBS(131,,0x0)
Here I have a Debian 9 system, with two bootloaders installed: the Debian default GRUB, and the more visually-oriented rEFInd, which I've set as the primary bootloader. I also have the UEFI Shell as a boot option, although that option is currently disabled.
Note that the BootOrder lists the order in which the other BootNNNN options will be tried.
You might have a BootNNNN line that's left over from the Windows or Arch installation. Since the bootloader file it refers to no longer exists, it is going to be useless. You can use efibootmgr -B -b NNNN
to delete it: just replace NNNN with the actual BootNNNN number you wish to delete.
Thanks for your time, but I just managed to solve the issue
– notvita
May 13 '18 at 11:19
No problem. However, please consider documenting your solution by writing an answer yourself, so that your solution may help others with a similar problem.
– telcoM
May 13 '18 at 11:30
I attempted to but it just got added as a comment on my OP. I followed the exact steps listed in the link for anyone else that runs into this issue!
– notvita
May 13 '18 at 11:35
add a comment |
BootOrder
is one of the UEFI boot variables, stored in NVRAM along with other firmware configuration (what used to be "BIOS settings").
In Linux, you can use efibootmgr -v
to view the boot variables.
Example:
# efibootmgr -v
BootCurrent: 0001
Timeout: 6 seconds
BootOrder: 0001,0002,0000,0003,0004,0005,0006
Boot0000* debian HD(1,GPT,4fb8aadb-9507-44b5-8cab-a052a0091e2b,0x800,0x100000)/File(EFIDEBIANGRUBX64.EFI)
Boot0001* rEFInd Boot Manager HD(1,GPT,4fb8aadb-9507-44b5-8cab-a052a0091e2b,0x800,0x100000)/File(EFIREFINDREFIND_X64.EFI)
Boot0002* UEFI: IP4 Realtek PCIe GBE Family Controller PciRoot(0x0)/Pci(0x1c,0x2)/Pci(0x0,0x0)/MAC(107b447ad398,0)/IPv4(0.0.0.0:0<->0.0.0.0:0,0,0)..BO
Boot0003 UEFI Shell HD(1,GPT,4fb8aadb-9507-44b5-8cab-a052a0091e2b,0x800,0x100000)/File(EFItoolsshell.efi)
Boot0004* UEFI:CD/DVD Drive BBS(129,,0x0)
Boot0005* UEFI:Removable Device BBS(130,,0x0)
Boot0006* UEFI:Network Device BBS(131,,0x0)
Here I have a Debian 9 system, with two bootloaders installed: the Debian default GRUB, and the more visually-oriented rEFInd, which I've set as the primary bootloader. I also have the UEFI Shell as a boot option, although that option is currently disabled.
Note that the BootOrder lists the order in which the other BootNNNN options will be tried.
You might have a BootNNNN line that's left over from the Windows or Arch installation. Since the bootloader file it refers to no longer exists, it is going to be useless. You can use efibootmgr -B -b NNNN
to delete it: just replace NNNN with the actual BootNNNN number you wish to delete.
Thanks for your time, but I just managed to solve the issue
– notvita
May 13 '18 at 11:19
No problem. However, please consider documenting your solution by writing an answer yourself, so that your solution may help others with a similar problem.
– telcoM
May 13 '18 at 11:30
I attempted to but it just got added as a comment on my OP. I followed the exact steps listed in the link for anyone else that runs into this issue!
– notvita
May 13 '18 at 11:35
add a comment |
BootOrder
is one of the UEFI boot variables, stored in NVRAM along with other firmware configuration (what used to be "BIOS settings").
In Linux, you can use efibootmgr -v
to view the boot variables.
Example:
# efibootmgr -v
BootCurrent: 0001
Timeout: 6 seconds
BootOrder: 0001,0002,0000,0003,0004,0005,0006
Boot0000* debian HD(1,GPT,4fb8aadb-9507-44b5-8cab-a052a0091e2b,0x800,0x100000)/File(EFIDEBIANGRUBX64.EFI)
Boot0001* rEFInd Boot Manager HD(1,GPT,4fb8aadb-9507-44b5-8cab-a052a0091e2b,0x800,0x100000)/File(EFIREFINDREFIND_X64.EFI)
Boot0002* UEFI: IP4 Realtek PCIe GBE Family Controller PciRoot(0x0)/Pci(0x1c,0x2)/Pci(0x0,0x0)/MAC(107b447ad398,0)/IPv4(0.0.0.0:0<->0.0.0.0:0,0,0)..BO
Boot0003 UEFI Shell HD(1,GPT,4fb8aadb-9507-44b5-8cab-a052a0091e2b,0x800,0x100000)/File(EFItoolsshell.efi)
Boot0004* UEFI:CD/DVD Drive BBS(129,,0x0)
Boot0005* UEFI:Removable Device BBS(130,,0x0)
Boot0006* UEFI:Network Device BBS(131,,0x0)
Here I have a Debian 9 system, with two bootloaders installed: the Debian default GRUB, and the more visually-oriented rEFInd, which I've set as the primary bootloader. I also have the UEFI Shell as a boot option, although that option is currently disabled.
Note that the BootOrder lists the order in which the other BootNNNN options will be tried.
You might have a BootNNNN line that's left over from the Windows or Arch installation. Since the bootloader file it refers to no longer exists, it is going to be useless. You can use efibootmgr -B -b NNNN
to delete it: just replace NNNN with the actual BootNNNN number you wish to delete.
BootOrder
is one of the UEFI boot variables, stored in NVRAM along with other firmware configuration (what used to be "BIOS settings").
In Linux, you can use efibootmgr -v
to view the boot variables.
Example:
# efibootmgr -v
BootCurrent: 0001
Timeout: 6 seconds
BootOrder: 0001,0002,0000,0003,0004,0005,0006
Boot0000* debian HD(1,GPT,4fb8aadb-9507-44b5-8cab-a052a0091e2b,0x800,0x100000)/File(EFIDEBIANGRUBX64.EFI)
Boot0001* rEFInd Boot Manager HD(1,GPT,4fb8aadb-9507-44b5-8cab-a052a0091e2b,0x800,0x100000)/File(EFIREFINDREFIND_X64.EFI)
Boot0002* UEFI: IP4 Realtek PCIe GBE Family Controller PciRoot(0x0)/Pci(0x1c,0x2)/Pci(0x0,0x0)/MAC(107b447ad398,0)/IPv4(0.0.0.0:0<->0.0.0.0:0,0,0)..BO
Boot0003 UEFI Shell HD(1,GPT,4fb8aadb-9507-44b5-8cab-a052a0091e2b,0x800,0x100000)/File(EFItoolsshell.efi)
Boot0004* UEFI:CD/DVD Drive BBS(129,,0x0)
Boot0005* UEFI:Removable Device BBS(130,,0x0)
Boot0006* UEFI:Network Device BBS(131,,0x0)
Here I have a Debian 9 system, with two bootloaders installed: the Debian default GRUB, and the more visually-oriented rEFInd, which I've set as the primary bootloader. I also have the UEFI Shell as a boot option, although that option is currently disabled.
Note that the BootOrder lists the order in which the other BootNNNN options will be tried.
You might have a BootNNNN line that's left over from the Windows or Arch installation. Since the bootloader file it refers to no longer exists, it is going to be useless. You can use efibootmgr -B -b NNNN
to delete it: just replace NNNN with the actual BootNNNN number you wish to delete.
answered May 13 '18 at 11:13
telcoMtelcoM
24.7k1 gold badge29 silver badges64 bronze badges
24.7k1 gold badge29 silver badges64 bronze badges
Thanks for your time, but I just managed to solve the issue
– notvita
May 13 '18 at 11:19
No problem. However, please consider documenting your solution by writing an answer yourself, so that your solution may help others with a similar problem.
– telcoM
May 13 '18 at 11:30
I attempted to but it just got added as a comment on my OP. I followed the exact steps listed in the link for anyone else that runs into this issue!
– notvita
May 13 '18 at 11:35
add a comment |
Thanks for your time, but I just managed to solve the issue
– notvita
May 13 '18 at 11:19
No problem. However, please consider documenting your solution by writing an answer yourself, so that your solution may help others with a similar problem.
– telcoM
May 13 '18 at 11:30
I attempted to but it just got added as a comment on my OP. I followed the exact steps listed in the link for anyone else that runs into this issue!
– notvita
May 13 '18 at 11:35
Thanks for your time, but I just managed to solve the issue
– notvita
May 13 '18 at 11:19
Thanks for your time, but I just managed to solve the issue
– notvita
May 13 '18 at 11:19
No problem. However, please consider documenting your solution by writing an answer yourself, so that your solution may help others with a similar problem.
– telcoM
May 13 '18 at 11:30
No problem. However, please consider documenting your solution by writing an answer yourself, so that your solution may help others with a similar problem.
– telcoM
May 13 '18 at 11:30
I attempted to but it just got added as a comment on my OP. I followed the exact steps listed in the link for anyone else that runs into this issue!
– notvita
May 13 '18 at 11:35
I attempted to but it just got added as a comment on my OP. I followed the exact steps listed in the link for anyone else that runs into this issue!
– notvita
May 13 '18 at 11:35
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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%2funix.stackexchange.com%2fquestions%2f443508%2fmessed-up-boot-system-bootorder-not-found%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
This seems to be a reoccurring issue: askubuntu.com/questions/1006545/… unix.stackexchange.com/questions/183421/… askubuntu.com/questions/1005034/… bugzilla.redhat.com/show_bug.cgi?id=1512410
– jdwolf
May 13 '18 at 9:47
It does appear manually selecting Ubuntu from the UEFI menu helps some people. But I think this is because in those cases its skipping GRUB and using EFI-stub instead and GRUB is the culprit here.
– jdwolf
May 13 '18 at 9:48
Yeah, I don't even see Ubuntu in the UEFI menu unfortunately. Thanks for the links, this is going to take some deep digging it seems.
– notvita
May 13 '18 at 11:05
2
I managed to solve this by following the answer posted here Thanks
– notvita
May 13 '18 at 11:19