EFI boot mmx64.efi not found
Please see attached screenshots of BIOS startup settings.
I (you don't need to tell me how stupid I was) accidentally deleted /sda1 on an Ubuntu 16.04 machine resulting in damaged EFI Boot settings.
But I was smart, too, as I had a current backup.
Ran boot recover utility - no joy.
Re-installed the Ubuntu operating system but keep getting these horror messages when booting up so I'm pretty sure it's not a OS problem. Most certainly a BIO/EFI issue.
(the screenshot with the dark background pretty much says it all)
I can boot with Ubuntu usb and access drives, etc. but booting from the hard drive just doesn't work.
Tell me what you need to know to help me. Output of commands will be gladly provided.
grub-efi
asked Dec 20 at 0:57
jeffschips
294
add a comment |
Please see attached screenshots of BIOS startup settings.
I (you don't need to tell me how stupid I was) accidentally deleted /sda1 on an Ubuntu 16.04 machine resulting in damaged EFI Boot settings.
But I was smart, too, as I had a current backup.
Ran boot recover utility - no joy.
Re-installed the Ubuntu operating system but keep getting these horror messages when booting up so I'm pretty sure it's not a OS problem. Most certainly a BIO/EFI issue.
(the screenshot with the dark background pretty much says it all)
I can boot with Ubuntu usb and access drives, etc. but booting from the hard drive just doesn't work.
Tell me what you need to know to help me. Output of commands will be gladly provided.
grub-efi
asked Dec 20 at 0:57
jeffschips
294
Have you recreated ESP - efi system partition as FAT32 with boot flag/esp flag? Then you may be able to use Boot-Repair's advanced mode and the full reinstall of grub. Be sure to boot live installer in UEFI mode.
– oldfred
Dec 20 at 4:51
add a comment |
Please see attached screenshots of BIOS startup settings.
I (you don't need to tell me how stupid I was) accidentally deleted /sda1 on an Ubuntu 16.04 machine resulting in damaged EFI Boot settings.
But I was smart, too, as I had a current backup.
Ran boot recover utility - no joy.
Re-installed the Ubuntu operating system but keep getting these horror messages when booting up so I'm pretty sure it's not a OS problem. Most certainly a BIO/EFI issue.
(the screenshot with the dark background pretty much says it all)
I can boot with Ubuntu usb and access drives, etc. but booting from the hard drive just doesn't work.
Tell me what you need to know to help me. Output of commands will be gladly provided.
grub-efi
asked Dec 20 at 0:57
jeffschips
294
Please see attached screenshots of BIOS startup settings.
I (you don't need to tell me how stupid I was) accidentally deleted /sda1 on an Ubuntu 16.04 machine resulting in damaged EFI Boot settings.
But I was smart, too, as I had a current backup.
Ran boot recover utility - no joy.
Re-installed the Ubuntu operating system but keep getting these horror messages when booting up so I'm pretty sure it's not a OS problem. Most certainly a BIO/EFI issue.
(the screenshot with the dark background pretty much says it all)
I can boot with Ubuntu usb and access drives, etc. but booting from the hard drive just doesn't work.
Tell me what you need to know to help me. Output of commands will be gladly provided.
grub-efi
grub-efi
asked Dec 20 at 0:57
jeffschips
294
asked Dec 20 at 0:57
jeffschips
294
asked Dec 20 at 0:57
jeffschips
294
asked Dec 20 at 0:57
jeffschips
294
asked Dec 20 at 0:57
jeffschips
294
294
Have you recreated ESP - efi system partition as FAT32 with boot flag/esp flag? Then you may be able to use Boot-Repair's advanced mode and the full reinstall of grub. Be sure to boot live installer in UEFI mode.
– oldfred
Dec 20 at 4:51
add a comment |
Have you recreated ESP - efi system partition as FAT32 with boot flag/esp flag? Then you may be able to use Boot-Repair's advanced mode and the full reinstall of grub. Be sure to boot live installer in UEFI mode.
– oldfred
Dec 20 at 4:51
Have you recreated ESP - efi system partition as FAT32 with boot flag/esp flag? Then you may be able to use Boot-Repair's advanced mode and the full reinstall of grub. Be sure to boot live installer in UEFI mode.
– oldfred
Dec 20 at 4:51
Have you recreated ESP - efi system partition as FAT32 with boot flag/esp flag? Then you may be able to use Boot-Repair's advanced mode and the full reinstall of grub. Be sure to boot live installer in UEFI mode.
– oldfred
Dec 20 at 4:51
add a comment |
1 Answer
1
active
oldest
votes
SOLVED:
This thread, reply #34 was what worked.
In my case it was not a USB that would not boot (as per the article above) but the desktop machine. To fix it, I booted into a recovery disk like "boot repair" and bypassed the automatic repair sequence that boot repair steps you into once you have booted up in that recovery mode.
Then I opened a terminal and navigated to the /EFI directory on the stricken machine that would not boot.
There were two directories there: Boot and ubuntu.
I copied the file grubx64.efi from the BOOT directory and placed it into the ubuntu directory and renamed it to mmx64.efi.
Then I closed down the machine and rebooted and entered the BIOS. Therein I set the machine to boot from "ubuntu" (which was never listed there previously).
That's how I fixed this mess.
Hope this helps but would also suggest anyone with this problem read through the other suggestions on the above referenced link as I was in ubuntu and others may be different.
edited Dec 21 at 0:44
user68186
15.2k84665
answered Dec 20 at 17:08
jeffschips
294
1
Please edit your answer to include the essential elements of the solution. The link only is not sufficient for a good answer. Keep the link as reference. See How do I write a good answer in the under the help section of this site.
– user68186
Dec 20 at 17:14
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%2f1103234%2fefi-boot-mmx64-efi-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
SOLVED:
This thread, reply #34 was what worked.
In my case it was not a USB that would not boot (as per the article above) but the desktop machine. To fix it, I booted into a recovery disk like "boot repair" and bypassed the automatic repair sequence that boot repair steps you into once you have booted up in that recovery mode.
Then I opened a terminal and navigated to the /EFI directory on the stricken machine that would not boot.
There were two directories there: Boot and ubuntu.
I copied the file grubx64.efi from the BOOT directory and placed it into the ubuntu directory and renamed it to mmx64.efi.
Then I closed down the machine and rebooted and entered the BIOS. Therein I set the machine to boot from "ubuntu" (which was never listed there previously).
That's how I fixed this mess.
Hope this helps but would also suggest anyone with this problem read through the other suggestions on the above referenced link as I was in ubuntu and others may be different.
edited Dec 21 at 0:44
user68186
15.2k84665
answered Dec 20 at 17:08
jeffschips
294
1
Please edit your answer to include the essential elements of the solution. The link only is not sufficient for a good answer. Keep the link as reference. See How do I write a good answer in the under the help section of this site.
– user68186
Dec 20 at 17:14
add a comment |
SOLVED:
This thread, reply #34 was what worked.
In my case it was not a USB that would not boot (as per the article above) but the desktop machine. To fix it, I booted into a recovery disk like "boot repair" and bypassed the automatic repair sequence that boot repair steps you into once you have booted up in that recovery mode.
Then I opened a terminal and navigated to the /EFI directory on the stricken machine that would not boot.
There were two directories there: Boot and ubuntu.
I copied the file grubx64.efi from the BOOT directory and placed it into the ubuntu directory and renamed it to mmx64.efi.
Then I closed down the machine and rebooted and entered the BIOS. Therein I set the machine to boot from "ubuntu" (which was never listed there previously).
That's how I fixed this mess.
Hope this helps but would also suggest anyone with this problem read through the other suggestions on the above referenced link as I was in ubuntu and others may be different.
edited Dec 21 at 0:44
user68186
15.2k84665
answered Dec 20 at 17:08
jeffschips
294
1
Please edit your answer to include the essential elements of the solution. The link only is not sufficient for a good answer. Keep the link as reference. See How do I write a good answer in the under the help section of this site.
– user68186
Dec 20 at 17:14
add a comment |
SOLVED:
This thread, reply #34 was what worked.
In my case it was not a USB that would not boot (as per the article above) but the desktop machine. To fix it, I booted into a recovery disk like "boot repair" and bypassed the automatic repair sequence that boot repair steps you into once you have booted up in that recovery mode.
Then I opened a terminal and navigated to the /EFI directory on the stricken machine that would not boot.
There were two directories there: Boot and ubuntu.
I copied the file grubx64.efi from the BOOT directory and placed it into the ubuntu directory and renamed it to mmx64.efi.
Then I closed down the machine and rebooted and entered the BIOS. Therein I set the machine to boot from "ubuntu" (which was never listed there previously).
That's how I fixed this mess.
Hope this helps but would also suggest anyone with this problem read through the other suggestions on the above referenced link as I was in ubuntu and others may be different.
edited Dec 21 at 0:44
user68186
15.2k84665
answered Dec 20 at 17:08
jeffschips
294
SOLVED:
This thread, reply #34 was what worked.
In my case it was not a USB that would not boot (as per the article above) but the desktop machine. To fix it, I booted into a recovery disk like "boot repair" and bypassed the automatic repair sequence that boot repair steps you into once you have booted up in that recovery mode.
Then I opened a terminal and navigated to the /EFI directory on the stricken machine that would not boot.
There were two directories there: Boot and ubuntu.
I copied the file grubx64.efi from the BOOT directory and placed it into the ubuntu directory and renamed it to mmx64.efi.
Then I closed down the machine and rebooted and entered the BIOS. Therein I set the machine to boot from "ubuntu" (which was never listed there previously).
That's how I fixed this mess.
Hope this helps but would also suggest anyone with this problem read through the other suggestions on the above referenced link as I was in ubuntu and others may be different.
edited Dec 21 at 0:44
user68186
15.2k84665
answered Dec 20 at 17:08
jeffschips
294
edited Dec 21 at 0:44
user68186
15.2k84665
edited Dec 21 at 0:44
user68186
15.2k84665
edited Dec 21 at 0:44
user68186
15.2k84665
15.2k84665
answered Dec 20 at 17:08
jeffschips
294
answered Dec 20 at 17:08
jeffschips
294
answered Dec 20 at 17:08
jeffschips
294
294
1
Please edit your answer to include the essential elements of the solution. The link only is not sufficient for a good answer. Keep the link as reference. See How do I write a good answer in the under the help section of this site.
– user68186
Dec 20 at 17:14
add a comment |
1
Please edit your answer to include the essential elements of the solution. The link only is not sufficient for a good answer. Keep the link as reference. See How do I write a good answer in the under the help section of this site.
– user68186
Dec 20 at 17:14
1
1
Please edit your answer to include the essential elements of the solution. The link only is not sufficient for a good answer. Keep the link as reference. See How do I write a good answer in the under the help section of this site.
– user68186
Dec 20 at 17:14
Please edit your answer to include the essential elements of the solution. The link only is not sufficient for a good answer. Keep the link as reference. See How do I write a good answer in the under the help section of this site.
– user68186
Dec 20 at 17:14
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.
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%2faskubuntu.com%2fquestions%2f1103234%2fefi-boot-mmx64-efi-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
Have you recreated ESP - efi system partition as FAT32 with boot flag/esp flag? Then you may be able to use Boot-Repair's advanced mode and the full reinstall of grub. Be sure to boot live installer in UEFI mode.
– oldfred
Dec 20 at 4:51