Messed up boot - System BootOrder not found
up vote
1
down vote
favorite
So the title basically says it all. I've got myself into a bit of a situation where I cannot boot into my fresh install system at all. I can only guess it has something to do with my booting not being setup correctly.
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
Like I said, 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.
Any help would be greatly appreciated. Thanks.
ubuntu boot uefi
asked May 13 at 7:28
notvita
613
add a comment |
up vote
1
down vote
favorite
So the title basically says it all. I've got myself into a bit of a situation where I cannot boot into my fresh install system at all. I can only guess it has something to do with my booting not being setup correctly.
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
Like I said, 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.
Any help would be greatly appreciated. Thanks.
ubuntu boot uefi
asked May 13 at 7:28
notvita
613
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 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 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 at 11:05
2
I managed to solve this by following the answer posted here Thanks
– notvita
May 13 at 11:19
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
So the title basically says it all. I've got myself into a bit of a situation where I cannot boot into my fresh install system at all. I can only guess it has something to do with my booting not being setup correctly.
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
Like I said, 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.
Any help would be greatly appreciated. Thanks.
ubuntu boot uefi
asked May 13 at 7:28
notvita
613
So the title basically says it all. I've got myself into a bit of a situation where I cannot boot into my fresh install system at all. I can only guess it has something to do with my booting not being setup correctly.
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
Like I said, 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.
Any help would be greatly appreciated. Thanks.
ubuntu boot uefi
ubuntu boot uefi
asked May 13 at 7:28
notvita
613
asked May 13 at 7:28
notvita
613
asked May 13 at 7:28
notvita
613
asked May 13 at 7:28
notvita
613
asked May 13 at 7:28
notvita
613
613
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 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 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 at 11:05
2
I managed to solve this by following the answer posted here Thanks
– notvita
May 13 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 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 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 at 11:05
2
I managed to solve this by following the answer posted here Thanks
– notvita
May 13 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 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 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 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 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 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 at 11:05
2
2
I managed to solve this by following the answer posted here Thanks
– notvita
May 13 at 11:19
I managed to solve this by following the answer posted here Thanks
– notvita
May 13 at 11:19
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
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 at 11:13
telcoM
15.2k12143
Thanks for your time, but I just managed to solve the issue
– notvita
May 13 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 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 at 11:35
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
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 at 11:13
telcoM
15.2k12143
Thanks for your time, but I just managed to solve the issue
– notvita
May 13 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 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 at 11:35
add a comment |
up vote
0
down vote
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 at 11:13
telcoM
15.2k12143
Thanks for your time, but I just managed to solve the issue
– notvita
May 13 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 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 at 11:35
add a comment |
up vote
0
down vote
up vote
0
down vote
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 at 11:13
telcoM
15.2k12143
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 at 11:13
telcoM
15.2k12143
answered May 13 at 11:13
telcoM
15.2k12143
answered May 13 at 11:13
telcoM
15.2k12143
answered May 13 at 11:13
telcoM
15.2k12143
15.2k12143
Thanks for your time, but I just managed to solve the issue
– notvita
May 13 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 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 at 11:35
add a comment |
Thanks for your time, but I just managed to solve the issue
– notvita
May 13 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 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 at 11:35
Thanks for your time, but I just managed to solve the issue
– notvita
May 13 at 11:19
Thanks for your time, but I just managed to solve the issue
– notvita
May 13 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 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 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 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 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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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 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 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 at 11:05
2
I managed to solve this by following the answer posted here Thanks
– notvita
May 13 at 11:19