Booting into Ubuntu after Fresh Install of Ubuntu 14.04 LTS ( No Dual Boot ) on Acer Aspire ES1-512
I have run Boot Repair on my machine and then rebooted my machine with my Live USB out.
From this point, I was first presented with a screen that said
1) "Shim UEFI Key Management" then was presented with
2) Boot Manager screen with two options: a) Unknown Device and b) Windows Boot Manager. Selected "Unknown Device" as option (b) did nothing.
3) After this, saw a GRUB ver 2.02 screen with the first option of *Ubuntu, which then eventually got me into Ubuntu.
The above sequence of steps occurs everytime I reboot my machine.
Why all these steps?
FYI, here is my boot-repair info: http://paste.ubuntu.com/10562192/
You will notice that on lines: 549, 741 and 776, I am getting the line:
Boot0000* Unknown Device: HD(1,800,100000,aa8f4a18-e5fc-41ff-bb2d-826eab7312c9)File(EFIubuntushimx64.efi)RC
Would this be the reason I am getting the "Unknown Device" in my Boot Manager?
Thanks.
boot uefi boot-repair
asked Mar 8 '15 at 14:38
tonyftonyf
1,17741118
add a comment |
I have run Boot Repair on my machine and then rebooted my machine with my Live USB out.
From this point, I was first presented with a screen that said
1) "Shim UEFI Key Management" then was presented with
2) Boot Manager screen with two options: a) Unknown Device and b) Windows Boot Manager. Selected "Unknown Device" as option (b) did nothing.
3) After this, saw a GRUB ver 2.02 screen with the first option of *Ubuntu, which then eventually got me into Ubuntu.
The above sequence of steps occurs everytime I reboot my machine.
Why all these steps?
FYI, here is my boot-repair info: http://paste.ubuntu.com/10562192/
You will notice that on lines: 549, 741 and 776, I am getting the line:
Boot0000* Unknown Device: HD(1,800,100000,aa8f4a18-e5fc-41ff-bb2d-826eab7312c9)File(EFIubuntushimx64.efi)RC
Would this be the reason I am getting the "Unknown Device" in my Boot Manager?
Thanks.
boot uefi boot-repair
asked Mar 8 '15 at 14:38
tonyftonyf
1,17741118
add a comment |
I have run Boot Repair on my machine and then rebooted my machine with my Live USB out.
From this point, I was first presented with a screen that said
1) "Shim UEFI Key Management" then was presented with
2) Boot Manager screen with two options: a) Unknown Device and b) Windows Boot Manager. Selected "Unknown Device" as option (b) did nothing.
3) After this, saw a GRUB ver 2.02 screen with the first option of *Ubuntu, which then eventually got me into Ubuntu.
The above sequence of steps occurs everytime I reboot my machine.
Why all these steps?
FYI, here is my boot-repair info: http://paste.ubuntu.com/10562192/
You will notice that on lines: 549, 741 and 776, I am getting the line:
Boot0000* Unknown Device: HD(1,800,100000,aa8f4a18-e5fc-41ff-bb2d-826eab7312c9)File(EFIubuntushimx64.efi)RC
Would this be the reason I am getting the "Unknown Device" in my Boot Manager?
Thanks.
boot uefi boot-repair
asked Mar 8 '15 at 14:38
tonyftonyf
1,17741118
I have run Boot Repair on my machine and then rebooted my machine with my Live USB out.
From this point, I was first presented with a screen that said
1) "Shim UEFI Key Management" then was presented with
2) Boot Manager screen with two options: a) Unknown Device and b) Windows Boot Manager. Selected "Unknown Device" as option (b) did nothing.
3) After this, saw a GRUB ver 2.02 screen with the first option of *Ubuntu, which then eventually got me into Ubuntu.
The above sequence of steps occurs everytime I reboot my machine.
Why all these steps?
FYI, here is my boot-repair info: http://paste.ubuntu.com/10562192/
You will notice that on lines: 549, 741 and 776, I am getting the line:
Boot0000* Unknown Device: HD(1,800,100000,aa8f4a18-e5fc-41ff-bb2d-826eab7312c9)File(EFIubuntushimx64.efi)RC
Would this be the reason I am getting the "Unknown Device" in my Boot Manager?
Thanks.
boot uefi boot-repair
boot uefi boot-repair
asked Mar 8 '15 at 14:38
tonyftonyf
1,17741118
asked Mar 8 '15 at 14:38
tonyftonyf
1,17741118
edited Mar 8 '15 at 15:17
tonyf
asked Mar 8 '15 at 14:38
tonyftonyf
1,17741118
asked Mar 8 '15 at 14:38
tonyftonyf
1,17741118
asked Mar 8 '15 at 14:38
tonyftonyf
1,17741118
1,17741118
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The "Shim UEFI Key Management" screen is probably MokManager, which manages Secure Boot keys used by the Shim program. Shim is a signed pre-GRUB boot loader whose job is to enable Linux to boot on a computer that uses Secure Boot. Secure Boot is a complex topic; see my page on the subject (or many other pages; Google to find a selection) for more details.
The fact that you're seeing the same MokManager screen pop up on every boot means that either you're not registering a key or your firmware is forgetting them. If you're able to get into Ubuntu without registering a key, then my suspicion is that you've got at least two Linux boot paths registered; one is failing and then the other is launching. If you do register a key, then as I said, your firmware is forgetting them.
Posting your Boot Repair pastebin file would be helpful, yes.
answered Mar 8 '15 at 15:11
Rod SmithRod Smith
35.7k43970
FYI, added Boot Repair pastebin file link in my thread above with some additional info.
– tonyf
Mar 8 '15 at 15:18
With Secure Boot - do I need to disable it within my BIOS?
– tonyf
Mar 8 '15 at 15:26
The names shown inefibootmgrmay show up in your firmware's boot manager, so that is probably the source of "Unknown Device" there. It looks like you've got at least two (I suspect three) copies of Shim, and at least one of them isn't working, hence the failure and fallback to one working entry. Please review the Secure Boot link I posted earlier, and the first two sub-pages on its parent page. This will give you the background you need to track down which Shim copy is causing your problems and delete it.
– Rod Smith
Mar 8 '15 at 15:28
Where exactly (filename), do I delete these Shim copies and secondly, do I need to do anything with this "Unknown Device" issue? Thanks.
– tonyf
Mar 8 '15 at 15:31
Don't get hung up on the name "Unknown Device;" that's intended to be descriptive text for human consumption -- although some tool obviously botched that intention. As to where the files are, in Linux, they'd probably be in/boot/efi/EFI/ubuntuand/boot/efi/EFI/BOOT, although the suspected third copy will be elsewhere, perhaps not even mounted. That's why I said to read those pages; they'll describe what you need to know to figure out where things are. What little standardization there is on this is insufficient for me to give you specific instructions.
– Rod Smith
Mar 8 '15 at 20:53
add a comment |
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%2f594216%2fbooting-into-ubuntu-after-fresh-install-of-ubuntu-14-04-lts-no-dual-boot-on%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
The "Shim UEFI Key Management" screen is probably MokManager, which manages Secure Boot keys used by the Shim program. Shim is a signed pre-GRUB boot loader whose job is to enable Linux to boot on a computer that uses Secure Boot. Secure Boot is a complex topic; see my page on the subject (or many other pages; Google to find a selection) for more details.
The fact that you're seeing the same MokManager screen pop up on every boot means that either you're not registering a key or your firmware is forgetting them. If you're able to get into Ubuntu without registering a key, then my suspicion is that you've got at least two Linux boot paths registered; one is failing and then the other is launching. If you do register a key, then as I said, your firmware is forgetting them.
Posting your Boot Repair pastebin file would be helpful, yes.
answered Mar 8 '15 at 15:11
Rod SmithRod Smith
35.7k43970
FYI, added Boot Repair pastebin file link in my thread above with some additional info.
– tonyf
Mar 8 '15 at 15:18
With Secure Boot - do I need to disable it within my BIOS?
– tonyf
Mar 8 '15 at 15:26
The names shown inefibootmgrmay show up in your firmware's boot manager, so that is probably the source of "Unknown Device" there. It looks like you've got at least two (I suspect three) copies of Shim, and at least one of them isn't working, hence the failure and fallback to one working entry. Please review the Secure Boot link I posted earlier, and the first two sub-pages on its parent page. This will give you the background you need to track down which Shim copy is causing your problems and delete it.
– Rod Smith
Mar 8 '15 at 15:28
Where exactly (filename), do I delete these Shim copies and secondly, do I need to do anything with this "Unknown Device" issue? Thanks.
– tonyf
Mar 8 '15 at 15:31
Don't get hung up on the name "Unknown Device;" that's intended to be descriptive text for human consumption -- although some tool obviously botched that intention. As to where the files are, in Linux, they'd probably be in/boot/efi/EFI/ubuntuand/boot/efi/EFI/BOOT, although the suspected third copy will be elsewhere, perhaps not even mounted. That's why I said to read those pages; they'll describe what you need to know to figure out where things are. What little standardization there is on this is insufficient for me to give you specific instructions.
– Rod Smith
Mar 8 '15 at 20:53
add a comment |
The "Shim UEFI Key Management" screen is probably MokManager, which manages Secure Boot keys used by the Shim program. Shim is a signed pre-GRUB boot loader whose job is to enable Linux to boot on a computer that uses Secure Boot. Secure Boot is a complex topic; see my page on the subject (or many other pages; Google to find a selection) for more details.
The fact that you're seeing the same MokManager screen pop up on every boot means that either you're not registering a key or your firmware is forgetting them. If you're able to get into Ubuntu without registering a key, then my suspicion is that you've got at least two Linux boot paths registered; one is failing and then the other is launching. If you do register a key, then as I said, your firmware is forgetting them.
Posting your Boot Repair pastebin file would be helpful, yes.
answered Mar 8 '15 at 15:11
Rod SmithRod Smith
35.7k43970
FYI, added Boot Repair pastebin file link in my thread above with some additional info.
– tonyf
Mar 8 '15 at 15:18
With Secure Boot - do I need to disable it within my BIOS?
– tonyf
Mar 8 '15 at 15:26
The names shown inefibootmgrmay show up in your firmware's boot manager, so that is probably the source of "Unknown Device" there. It looks like you've got at least two (I suspect three) copies of Shim, and at least one of them isn't working, hence the failure and fallback to one working entry. Please review the Secure Boot link I posted earlier, and the first two sub-pages on its parent page. This will give you the background you need to track down which Shim copy is causing your problems and delete it.
– Rod Smith
Mar 8 '15 at 15:28
Where exactly (filename), do I delete these Shim copies and secondly, do I need to do anything with this "Unknown Device" issue? Thanks.
– tonyf
Mar 8 '15 at 15:31
Don't get hung up on the name "Unknown Device;" that's intended to be descriptive text for human consumption -- although some tool obviously botched that intention. As to where the files are, in Linux, they'd probably be in/boot/efi/EFI/ubuntuand/boot/efi/EFI/BOOT, although the suspected third copy will be elsewhere, perhaps not even mounted. That's why I said to read those pages; they'll describe what you need to know to figure out where things are. What little standardization there is on this is insufficient for me to give you specific instructions.
– Rod Smith
Mar 8 '15 at 20:53
add a comment |
The "Shim UEFI Key Management" screen is probably MokManager, which manages Secure Boot keys used by the Shim program. Shim is a signed pre-GRUB boot loader whose job is to enable Linux to boot on a computer that uses Secure Boot. Secure Boot is a complex topic; see my page on the subject (or many other pages; Google to find a selection) for more details.
The fact that you're seeing the same MokManager screen pop up on every boot means that either you're not registering a key or your firmware is forgetting them. If you're able to get into Ubuntu without registering a key, then my suspicion is that you've got at least two Linux boot paths registered; one is failing and then the other is launching. If you do register a key, then as I said, your firmware is forgetting them.
Posting your Boot Repair pastebin file would be helpful, yes.
answered Mar 8 '15 at 15:11
Rod SmithRod Smith
35.7k43970
The "Shim UEFI Key Management" screen is probably MokManager, which manages Secure Boot keys used by the Shim program. Shim is a signed pre-GRUB boot loader whose job is to enable Linux to boot on a computer that uses Secure Boot. Secure Boot is a complex topic; see my page on the subject (or many other pages; Google to find a selection) for more details.
The fact that you're seeing the same MokManager screen pop up on every boot means that either you're not registering a key or your firmware is forgetting them. If you're able to get into Ubuntu without registering a key, then my suspicion is that you've got at least two Linux boot paths registered; one is failing and then the other is launching. If you do register a key, then as I said, your firmware is forgetting them.
Posting your Boot Repair pastebin file would be helpful, yes.
answered Mar 8 '15 at 15:11
Rod SmithRod Smith
35.7k43970
answered Mar 8 '15 at 15:11
Rod SmithRod Smith
35.7k43970
answered Mar 8 '15 at 15:11
Rod SmithRod Smith
35.7k43970
answered Mar 8 '15 at 15:11
Rod SmithRod Smith
35.7k43970
35.7k43970
FYI, added Boot Repair pastebin file link in my thread above with some additional info.
– tonyf
Mar 8 '15 at 15:18
With Secure Boot - do I need to disable it within my BIOS?
– tonyf
Mar 8 '15 at 15:26
The names shown inefibootmgrmay show up in your firmware's boot manager, so that is probably the source of "Unknown Device" there. It looks like you've got at least two (I suspect three) copies of Shim, and at least one of them isn't working, hence the failure and fallback to one working entry. Please review the Secure Boot link I posted earlier, and the first two sub-pages on its parent page. This will give you the background you need to track down which Shim copy is causing your problems and delete it.
– Rod Smith
Mar 8 '15 at 15:28
Where exactly (filename), do I delete these Shim copies and secondly, do I need to do anything with this "Unknown Device" issue? Thanks.
– tonyf
Mar 8 '15 at 15:31
Don't get hung up on the name "Unknown Device;" that's intended to be descriptive text for human consumption -- although some tool obviously botched that intention. As to where the files are, in Linux, they'd probably be in/boot/efi/EFI/ubuntuand/boot/efi/EFI/BOOT, although the suspected third copy will be elsewhere, perhaps not even mounted. That's why I said to read those pages; they'll describe what you need to know to figure out where things are. What little standardization there is on this is insufficient for me to give you specific instructions.
– Rod Smith
Mar 8 '15 at 20:53
add a comment |
FYI, added Boot Repair pastebin file link in my thread above with some additional info.
– tonyf
Mar 8 '15 at 15:18
With Secure Boot - do I need to disable it within my BIOS?
– tonyf
Mar 8 '15 at 15:26
The names shown inefibootmgrmay show up in your firmware's boot manager, so that is probably the source of "Unknown Device" there. It looks like you've got at least two (I suspect three) copies of Shim, and at least one of them isn't working, hence the failure and fallback to one working entry. Please review the Secure Boot link I posted earlier, and the first two sub-pages on its parent page. This will give you the background you need to track down which Shim copy is causing your problems and delete it.
– Rod Smith
Mar 8 '15 at 15:28
Where exactly (filename), do I delete these Shim copies and secondly, do I need to do anything with this "Unknown Device" issue? Thanks.
– tonyf
Mar 8 '15 at 15:31
Don't get hung up on the name "Unknown Device;" that's intended to be descriptive text for human consumption -- although some tool obviously botched that intention. As to where the files are, in Linux, they'd probably be in/boot/efi/EFI/ubuntuand/boot/efi/EFI/BOOT, although the suspected third copy will be elsewhere, perhaps not even mounted. That's why I said to read those pages; they'll describe what you need to know to figure out where things are. What little standardization there is on this is insufficient for me to give you specific instructions.
– Rod Smith
Mar 8 '15 at 20:53
FYI, added Boot Repair pastebin file link in my thread above with some additional info.
– tonyf
Mar 8 '15 at 15:18
FYI, added Boot Repair pastebin file link in my thread above with some additional info.
– tonyf
Mar 8 '15 at 15:18
With Secure Boot - do I need to disable it within my BIOS?
– tonyf
Mar 8 '15 at 15:26
With Secure Boot - do I need to disable it within my BIOS?
– tonyf
Mar 8 '15 at 15:26
The names shown in
efibootmgr may show up in your firmware's boot manager, so that is probably the source of "Unknown Device" there. It looks like you've got at least two (I suspect three) copies of Shim, and at least one of them isn't working, hence the failure and fallback to one working entry. Please review the Secure Boot link I posted earlier, and the first two sub-pages on its parent page. This will give you the background you need to track down which Shim copy is causing your problems and delete it.– Rod Smith
Mar 8 '15 at 15:28
The names shown in
efibootmgr may show up in your firmware's boot manager, so that is probably the source of "Unknown Device" there. It looks like you've got at least two (I suspect three) copies of Shim, and at least one of them isn't working, hence the failure and fallback to one working entry. Please review the Secure Boot link I posted earlier, and the first two sub-pages on its parent page. This will give you the background you need to track down which Shim copy is causing your problems and delete it.– Rod Smith
Mar 8 '15 at 15:28
Where exactly (filename), do I delete these Shim copies and secondly, do I need to do anything with this "Unknown Device" issue? Thanks.
– tonyf
Mar 8 '15 at 15:31
Where exactly (filename), do I delete these Shim copies and secondly, do I need to do anything with this "Unknown Device" issue? Thanks.
– tonyf
Mar 8 '15 at 15:31
Don't get hung up on the name "Unknown Device;" that's intended to be descriptive text for human consumption -- although some tool obviously botched that intention. As to where the files are, in Linux, they'd probably be in
/boot/efi/EFI/ubuntu and /boot/efi/EFI/BOOT, although the suspected third copy will be elsewhere, perhaps not even mounted. That's why I said to read those pages; they'll describe what you need to know to figure out where things are. What little standardization there is on this is insufficient for me to give you specific instructions.– Rod Smith
Mar 8 '15 at 20:53
Don't get hung up on the name "Unknown Device;" that's intended to be descriptive text for human consumption -- although some tool obviously botched that intention. As to where the files are, in Linux, they'd probably be in
/boot/efi/EFI/ubuntu and /boot/efi/EFI/BOOT, although the suspected third copy will be elsewhere, perhaps not even mounted. That's why I said to read those pages; they'll describe what you need to know to figure out where things are. What little standardization there is on this is insufficient for me to give you specific instructions.– Rod Smith
Mar 8 '15 at 20:53
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%2f594216%2fbooting-into-ubuntu-after-fresh-install-of-ubuntu-14-04-lts-no-dual-boot-on%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
