Grub rescue error: Installed Ubuntu in Legacy alongside Windows10 in UEFI
Sorry for asking an already asked question, but I couldn't find anything that solved my problem. I did an extensive research on the internet (many users had similar problems) still I'm not able to fix it.
So, I messed up my laptops booting system: I installed Ubuntu in Legacy mode alongside a pre-installed Windows10 in UEFI. As you may know, one should't do it. I tried to restore things several times (by deleting the Ubuntu partition first and trying to install it again in EFI mode; by setting root
and prefix
to the right partition/path; etc...) - but nothing worked.
At the moment I cannot boot neither Windows nor Ubuntu.
When I try to set the prefix
to /boot/grub/i386-pc
and then enter insmod normal
or insmod linux
I get:
filesystem '(hd0,X)/boot/grub/i386-pc/x86_64-efi/blabla.mod' not found
That's is because there is no "x86_64-efi" folder at all! The rescue grub automatically sets this folder in the path and I don't know why.
The only thing I can do is booting Ubuntu from my pen drive, though when I start the boot-repair it says:
The current session is in legacy mode. Please reboot the computer, and use this software in an EFI session. ...
Here is the link to my Pastebin.
I still can see that Windows10 partitions in Gparted, but I don't know how to get it to work/boot again. Do you have any suggestions?
boot dual-boot 18.04 uefi grubrescue
New contributor
add a comment |
Sorry for asking an already asked question, but I couldn't find anything that solved my problem. I did an extensive research on the internet (many users had similar problems) still I'm not able to fix it.
So, I messed up my laptops booting system: I installed Ubuntu in Legacy mode alongside a pre-installed Windows10 in UEFI. As you may know, one should't do it. I tried to restore things several times (by deleting the Ubuntu partition first and trying to install it again in EFI mode; by setting root
and prefix
to the right partition/path; etc...) - but nothing worked.
At the moment I cannot boot neither Windows nor Ubuntu.
When I try to set the prefix
to /boot/grub/i386-pc
and then enter insmod normal
or insmod linux
I get:
filesystem '(hd0,X)/boot/grub/i386-pc/x86_64-efi/blabla.mod' not found
That's is because there is no "x86_64-efi" folder at all! The rescue grub automatically sets this folder in the path and I don't know why.
The only thing I can do is booting Ubuntu from my pen drive, though when I start the boot-repair it says:
The current session is in legacy mode. Please reboot the computer, and use this software in an EFI session. ...
Here is the link to my Pastebin.
I still can see that Windows10 partitions in Gparted, but I don't know how to get it to work/boot again. Do you have any suggestions?
boot dual-boot 18.04 uefi grubrescue
New contributor
2
Possible duplicate of Black screen after selecting an option from grub boot menu
– karel
Jan 8 at 13:40
You need to boot Ubuntu live installer in UEFI mode. Boot-Repair says it is in Legacy mode. You need to turn off fast start in Windows, report says data in cache. And you (almost) never install grub to a partition particularly FAT32 or NTFS. Fast start off:askubuntu.com/questions/843153/… We may have to run commands to clear the ESP's boot partition, but first try chkdsk on your ESP (sda1) from your Windows repair disk or dosfsck: askubuntu.com/questions/862724/grub2-failed-to-install/…
– oldfred
Jan 8 at 14:32
@oldfred I can't load windows anymore. Is there another way to disable fast start?
– iLenia
Jan 8 at 15:10
You may need a cold boot.askubuntu.com/questions/652966/… And then turn off fast boot in UEFI and boot Windows UEFI boot option. You may need f8 to get to Windows repair console also. Fast boot in UEFI is so quick you often have no time to press keys to get UEFI boot menu. And that is different than fast start up setting in Windows.
– oldfred
Jan 8 at 16:44
add a comment |
Sorry for asking an already asked question, but I couldn't find anything that solved my problem. I did an extensive research on the internet (many users had similar problems) still I'm not able to fix it.
So, I messed up my laptops booting system: I installed Ubuntu in Legacy mode alongside a pre-installed Windows10 in UEFI. As you may know, one should't do it. I tried to restore things several times (by deleting the Ubuntu partition first and trying to install it again in EFI mode; by setting root
and prefix
to the right partition/path; etc...) - but nothing worked.
At the moment I cannot boot neither Windows nor Ubuntu.
When I try to set the prefix
to /boot/grub/i386-pc
and then enter insmod normal
or insmod linux
I get:
filesystem '(hd0,X)/boot/grub/i386-pc/x86_64-efi/blabla.mod' not found
That's is because there is no "x86_64-efi" folder at all! The rescue grub automatically sets this folder in the path and I don't know why.
The only thing I can do is booting Ubuntu from my pen drive, though when I start the boot-repair it says:
The current session is in legacy mode. Please reboot the computer, and use this software in an EFI session. ...
Here is the link to my Pastebin.
I still can see that Windows10 partitions in Gparted, but I don't know how to get it to work/boot again. Do you have any suggestions?
boot dual-boot 18.04 uefi grubrescue
New contributor
Sorry for asking an already asked question, but I couldn't find anything that solved my problem. I did an extensive research on the internet (many users had similar problems) still I'm not able to fix it.
So, I messed up my laptops booting system: I installed Ubuntu in Legacy mode alongside a pre-installed Windows10 in UEFI. As you may know, one should't do it. I tried to restore things several times (by deleting the Ubuntu partition first and trying to install it again in EFI mode; by setting root
and prefix
to the right partition/path; etc...) - but nothing worked.
At the moment I cannot boot neither Windows nor Ubuntu.
When I try to set the prefix
to /boot/grub/i386-pc
and then enter insmod normal
or insmod linux
I get:
filesystem '(hd0,X)/boot/grub/i386-pc/x86_64-efi/blabla.mod' not found
That's is because there is no "x86_64-efi" folder at all! The rescue grub automatically sets this folder in the path and I don't know why.
The only thing I can do is booting Ubuntu from my pen drive, though when I start the boot-repair it says:
The current session is in legacy mode. Please reboot the computer, and use this software in an EFI session. ...
Here is the link to my Pastebin.
I still can see that Windows10 partitions in Gparted, but I don't know how to get it to work/boot again. Do you have any suggestions?
boot dual-boot 18.04 uefi grubrescue
boot dual-boot 18.04 uefi grubrescue
New contributor
New contributor
edited Jan 8 at 14:08
iLenia
New contributor
asked Jan 8 at 13:36
iLeniaiLenia
1
1
New contributor
New contributor
2
Possible duplicate of Black screen after selecting an option from grub boot menu
– karel
Jan 8 at 13:40
You need to boot Ubuntu live installer in UEFI mode. Boot-Repair says it is in Legacy mode. You need to turn off fast start in Windows, report says data in cache. And you (almost) never install grub to a partition particularly FAT32 or NTFS. Fast start off:askubuntu.com/questions/843153/… We may have to run commands to clear the ESP's boot partition, but first try chkdsk on your ESP (sda1) from your Windows repair disk or dosfsck: askubuntu.com/questions/862724/grub2-failed-to-install/…
– oldfred
Jan 8 at 14:32
@oldfred I can't load windows anymore. Is there another way to disable fast start?
– iLenia
Jan 8 at 15:10
You may need a cold boot.askubuntu.com/questions/652966/… And then turn off fast boot in UEFI and boot Windows UEFI boot option. You may need f8 to get to Windows repair console also. Fast boot in UEFI is so quick you often have no time to press keys to get UEFI boot menu. And that is different than fast start up setting in Windows.
– oldfred
Jan 8 at 16:44
add a comment |
2
Possible duplicate of Black screen after selecting an option from grub boot menu
– karel
Jan 8 at 13:40
You need to boot Ubuntu live installer in UEFI mode. Boot-Repair says it is in Legacy mode. You need to turn off fast start in Windows, report says data in cache. And you (almost) never install grub to a partition particularly FAT32 or NTFS. Fast start off:askubuntu.com/questions/843153/… We may have to run commands to clear the ESP's boot partition, but first try chkdsk on your ESP (sda1) from your Windows repair disk or dosfsck: askubuntu.com/questions/862724/grub2-failed-to-install/…
– oldfred
Jan 8 at 14:32
@oldfred I can't load windows anymore. Is there another way to disable fast start?
– iLenia
Jan 8 at 15:10
You may need a cold boot.askubuntu.com/questions/652966/… And then turn off fast boot in UEFI and boot Windows UEFI boot option. You may need f8 to get to Windows repair console also. Fast boot in UEFI is so quick you often have no time to press keys to get UEFI boot menu. And that is different than fast start up setting in Windows.
– oldfred
Jan 8 at 16:44
2
2
Possible duplicate of Black screen after selecting an option from grub boot menu
– karel
Jan 8 at 13:40
Possible duplicate of Black screen after selecting an option from grub boot menu
– karel
Jan 8 at 13:40
You need to boot Ubuntu live installer in UEFI mode. Boot-Repair says it is in Legacy mode. You need to turn off fast start in Windows, report says data in cache. And you (almost) never install grub to a partition particularly FAT32 or NTFS. Fast start off:askubuntu.com/questions/843153/… We may have to run commands to clear the ESP's boot partition, but first try chkdsk on your ESP (sda1) from your Windows repair disk or dosfsck: askubuntu.com/questions/862724/grub2-failed-to-install/…
– oldfred
Jan 8 at 14:32
You need to boot Ubuntu live installer in UEFI mode. Boot-Repair says it is in Legacy mode. You need to turn off fast start in Windows, report says data in cache. And you (almost) never install grub to a partition particularly FAT32 or NTFS. Fast start off:askubuntu.com/questions/843153/… We may have to run commands to clear the ESP's boot partition, but first try chkdsk on your ESP (sda1) from your Windows repair disk or dosfsck: askubuntu.com/questions/862724/grub2-failed-to-install/…
– oldfred
Jan 8 at 14:32
@oldfred I can't load windows anymore. Is there another way to disable fast start?
– iLenia
Jan 8 at 15:10
@oldfred I can't load windows anymore. Is there another way to disable fast start?
– iLenia
Jan 8 at 15:10
You may need a cold boot.askubuntu.com/questions/652966/… And then turn off fast boot in UEFI and boot Windows UEFI boot option. You may need f8 to get to Windows repair console also. Fast boot in UEFI is so quick you often have no time to press keys to get UEFI boot menu. And that is different than fast start up setting in Windows.
– oldfred
Jan 8 at 16:44
You may need a cold boot.askubuntu.com/questions/652966/… And then turn off fast boot in UEFI and boot Windows UEFI boot option. You may need f8 to get to Windows repair console also. Fast boot in UEFI is so quick you often have no time to press keys to get UEFI boot menu. And that is different than fast start up setting in Windows.
– oldfred
Jan 8 at 16:44
add a comment |
0
active
oldest
votes
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
});
}
});
iLenia is a new contributor. Be nice, and check out our Code of Conduct.
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%2f1107990%2fgrub-rescue-error-installed-ubuntu-in-legacy-alongside-windows10-in-uefi%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
iLenia is a new contributor. Be nice, and check out our Code of Conduct.
iLenia is a new contributor. Be nice, and check out our Code of Conduct.
iLenia is a new contributor. Be nice, and check out our Code of Conduct.
iLenia is a new contributor. Be nice, and check out our Code of Conduct.
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%2f1107990%2fgrub-rescue-error-installed-ubuntu-in-legacy-alongside-windows10-in-uefi%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
2
Possible duplicate of Black screen after selecting an option from grub boot menu
– karel
Jan 8 at 13:40
You need to boot Ubuntu live installer in UEFI mode. Boot-Repair says it is in Legacy mode. You need to turn off fast start in Windows, report says data in cache. And you (almost) never install grub to a partition particularly FAT32 or NTFS. Fast start off:askubuntu.com/questions/843153/… We may have to run commands to clear the ESP's boot partition, but first try chkdsk on your ESP (sda1) from your Windows repair disk or dosfsck: askubuntu.com/questions/862724/grub2-failed-to-install/…
– oldfred
Jan 8 at 14:32
@oldfred I can't load windows anymore. Is there another way to disable fast start?
– iLenia
Jan 8 at 15:10
You may need a cold boot.askubuntu.com/questions/652966/… And then turn off fast boot in UEFI and boot Windows UEFI boot option. You may need f8 to get to Windows repair console also. Fast boot in UEFI is so quick you often have no time to press keys to get UEFI boot menu. And that is different than fast start up setting in Windows.
– oldfred
Jan 8 at 16:44