Unable to detect/boot Windows 10 after converting Ubuntu from MBR+BIOS to GPT+EFIWindows 7 doesn't boot after Ubuntu installUnable to boot: Missing Operating systemHow can I change/convert a Ubuntu MBR drive to a GPT, and make Ubuntu boot from EFI?How to remove unnecessary EFI entries from GRUB?Unable to reduce Grub boot delayMulti boot EFI and MBR/BIOS pendrive, one grub.cfg fileUbuntu 14.04 hangs, can fix/login but then after reboot it hangs again. Have bootscript/details. Wubi issue?Grub2 Hybrid Boot (EFI+BIOS)Windows 10 Overrides boot settings in UEFI BIOS, requires Live CD fix to repair
What is the purpose of the rules in counterpoint composition?
Typing "PartOf" in excel changes automatically to part of?
Turning off Apple hardware checks on startup
What is latinum and where does it occur?
how to have a const variable in a for loop for generation of template classes?
Feeling of forcing oneself to do something
Clonezilla made a smaller image than actual drive size
Why do airlines usually ask you how much purchase you have made?
Is it academically dishonest to submit the same project to two different classes in the same semester?
Retracting Recommendation Letters
Why do cargo airplanes fly fewer cycles then airliners?
Can a German employer force mandatory overtime and forbid salary discussion?
In Germany, why does the burden of proof fall on authorities rather than the company or individual when it comes to possible illegal funds?
Is the use of ellipsis (...) dismissive or rude?
Why impeach Trump now and not earlier?
Why did Sofia do this to John's bottle?
Between while and do in shell script
Permanent river of lava
How does vampirism work in 5e?
Should I still follow "programming to an interface not implementation" even if I think using concrete class members is the simpler solution?
In Alita: Battle Angel do cyborgs have stomachs?
Does detect magic detect itself?
Did the Mueller report find that Trump committed any felonies?
Can socialism and capitalism coexist in the same country?
Unable to detect/boot Windows 10 after converting Ubuntu from MBR+BIOS to GPT+EFI
Windows 7 doesn't boot after Ubuntu installUnable to boot: Missing Operating systemHow can I change/convert a Ubuntu MBR drive to a GPT, and make Ubuntu boot from EFI?How to remove unnecessary EFI entries from GRUB?Unable to reduce Grub boot delayMulti boot EFI and MBR/BIOS pendrive, one grub.cfg fileUbuntu 14.04 hangs, can fix/login but then after reboot it hangs again. Have bootscript/details. Wubi issue?Grub2 Hybrid Boot (EFI+BIOS)Windows 10 Overrides boot settings in UEFI BIOS, requires Live CD fix to repair
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;
TL;DR
How can I boot from a EFI GRUB installation on a disc A a Windows 10 BIOS installation on a disk B?
Long explanationos-prober
is not detecting Windows anymore after having migrated Ubuntu from MBR+BIOS to GPT+EFI.
My disk situation is a little complicated:
sda 1,8T
└─sda1 ext4 1,4T /media/Steam Steam
sdb 931,5G
├─sdb1 vfat 512M
├─sdb2 ext4 125G home
├─sdb3 ext4 774,5G /media/Dati_ext4 Dati_ext4
└─sdb4 ext4 31,5G Ubuntu18.04
sdc 232,9G
├─sdc1 ntfs 100M
├─sdc2 ntfs 59G Win10
├─sdc3 ntfs 483M
└─sdc4 ntfs 172,9G Dati_NTFS
nvme0n1 477G
├─nvme0n1p1 ext4 62,4G / Ubuntu19.10
├─nvme0n1p2 vfat 200M /boot/efi EFI
└─nvme0n1p3 ext4 322,1G /home home
- I have 4 disks (1 NVMe and 3 SSDs).
- Before today they were all using MBR and the UEFI was booting the NVMe in legacy mode.
- I have 2 installation of Ubuntu (19.10 and 18.04) and 1 of Windows 10.
- Each OS has it's own disk (and the 4th disk as no OS installed). This means that each OS had its own boot loader installed on the MBR of each disk.
- GRUB was also able to see every other OS so, from the GRUB of the NVMe, I was able to boot any of the 3 OSs.
Today I decided to convert the NVMe installation of Ubuntu form MBR+BIOS to GPT+EFI. Since I did not touch any other disk, I was hoping that the GRUB will detect the other OSs and boot them normally.
The conversion worked fine and I'm able to boot in Ubuntu 19.10. But os-prober
recognize Ubuntu 18.04 but not Windows 10.
What I would like to do is either to find a fix for os-prober
, so that it recognize Windows, or to manually specify the GRUB configuration to boot the Windows MBR+BIOS installation.
I already tried something for the second approach but it didn't worked.
I added this to the /etc/grub.d/40_custom
of the EFI installation:
menuentry 'Windows 10 (su /dev/sdc1)' --class windows --class os
insmod part_msdos
insmod ntfs
set root='hd2,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd2,msdos1 --hint-efi=hd2,msdos1 --hint-baremetal=ahci2,msdos1 C08E2C498E2C3A74
else
search --no-floppy --fs-uuid --set=root C08E2C498E2C3A74
fi
parttool $root hidden-
drivemap -s (hd0) $root
chainloader +1
I took that from the working Ubuntu 18.04 GRUB MBR+BIOS installation.
But when I select Windows 10 from the GRUB menu I get just this error:
Setting partition type to 0x7
error: can't fine command `drivemap'.
error: invalid EFI file path.
Is it even possible to boot from an EFI GRUB a BIOS installation on a different disk of Windows 10?
boot grub2 windows uefi grub-efi
add a comment
|
TL;DR
How can I boot from a EFI GRUB installation on a disc A a Windows 10 BIOS installation on a disk B?
Long explanationos-prober
is not detecting Windows anymore after having migrated Ubuntu from MBR+BIOS to GPT+EFI.
My disk situation is a little complicated:
sda 1,8T
└─sda1 ext4 1,4T /media/Steam Steam
sdb 931,5G
├─sdb1 vfat 512M
├─sdb2 ext4 125G home
├─sdb3 ext4 774,5G /media/Dati_ext4 Dati_ext4
└─sdb4 ext4 31,5G Ubuntu18.04
sdc 232,9G
├─sdc1 ntfs 100M
├─sdc2 ntfs 59G Win10
├─sdc3 ntfs 483M
└─sdc4 ntfs 172,9G Dati_NTFS
nvme0n1 477G
├─nvme0n1p1 ext4 62,4G / Ubuntu19.10
├─nvme0n1p2 vfat 200M /boot/efi EFI
└─nvme0n1p3 ext4 322,1G /home home
- I have 4 disks (1 NVMe and 3 SSDs).
- Before today they were all using MBR and the UEFI was booting the NVMe in legacy mode.
- I have 2 installation of Ubuntu (19.10 and 18.04) and 1 of Windows 10.
- Each OS has it's own disk (and the 4th disk as no OS installed). This means that each OS had its own boot loader installed on the MBR of each disk.
- GRUB was also able to see every other OS so, from the GRUB of the NVMe, I was able to boot any of the 3 OSs.
Today I decided to convert the NVMe installation of Ubuntu form MBR+BIOS to GPT+EFI. Since I did not touch any other disk, I was hoping that the GRUB will detect the other OSs and boot them normally.
The conversion worked fine and I'm able to boot in Ubuntu 19.10. But os-prober
recognize Ubuntu 18.04 but not Windows 10.
What I would like to do is either to find a fix for os-prober
, so that it recognize Windows, or to manually specify the GRUB configuration to boot the Windows MBR+BIOS installation.
I already tried something for the second approach but it didn't worked.
I added this to the /etc/grub.d/40_custom
of the EFI installation:
menuentry 'Windows 10 (su /dev/sdc1)' --class windows --class os
insmod part_msdos
insmod ntfs
set root='hd2,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd2,msdos1 --hint-efi=hd2,msdos1 --hint-baremetal=ahci2,msdos1 C08E2C498E2C3A74
else
search --no-floppy --fs-uuid --set=root C08E2C498E2C3A74
fi
parttool $root hidden-
drivemap -s (hd0) $root
chainloader +1
I took that from the working Ubuntu 18.04 GRUB MBR+BIOS installation.
But when I select Windows 10 from the GRUB menu I get just this error:
Setting partition type to 0x7
error: can't fine command `drivemap'.
error: invalid EFI file path.
Is it even possible to boot from an EFI GRUB a BIOS installation on a different disk of Windows 10?
boot grub2 windows uefi grub-efi
add a comment
|
TL;DR
How can I boot from a EFI GRUB installation on a disc A a Windows 10 BIOS installation on a disk B?
Long explanationos-prober
is not detecting Windows anymore after having migrated Ubuntu from MBR+BIOS to GPT+EFI.
My disk situation is a little complicated:
sda 1,8T
└─sda1 ext4 1,4T /media/Steam Steam
sdb 931,5G
├─sdb1 vfat 512M
├─sdb2 ext4 125G home
├─sdb3 ext4 774,5G /media/Dati_ext4 Dati_ext4
└─sdb4 ext4 31,5G Ubuntu18.04
sdc 232,9G
├─sdc1 ntfs 100M
├─sdc2 ntfs 59G Win10
├─sdc3 ntfs 483M
└─sdc4 ntfs 172,9G Dati_NTFS
nvme0n1 477G
├─nvme0n1p1 ext4 62,4G / Ubuntu19.10
├─nvme0n1p2 vfat 200M /boot/efi EFI
└─nvme0n1p3 ext4 322,1G /home home
- I have 4 disks (1 NVMe and 3 SSDs).
- Before today they were all using MBR and the UEFI was booting the NVMe in legacy mode.
- I have 2 installation of Ubuntu (19.10 and 18.04) and 1 of Windows 10.
- Each OS has it's own disk (and the 4th disk as no OS installed). This means that each OS had its own boot loader installed on the MBR of each disk.
- GRUB was also able to see every other OS so, from the GRUB of the NVMe, I was able to boot any of the 3 OSs.
Today I decided to convert the NVMe installation of Ubuntu form MBR+BIOS to GPT+EFI. Since I did not touch any other disk, I was hoping that the GRUB will detect the other OSs and boot them normally.
The conversion worked fine and I'm able to boot in Ubuntu 19.10. But os-prober
recognize Ubuntu 18.04 but not Windows 10.
What I would like to do is either to find a fix for os-prober
, so that it recognize Windows, or to manually specify the GRUB configuration to boot the Windows MBR+BIOS installation.
I already tried something for the second approach but it didn't worked.
I added this to the /etc/grub.d/40_custom
of the EFI installation:
menuentry 'Windows 10 (su /dev/sdc1)' --class windows --class os
insmod part_msdos
insmod ntfs
set root='hd2,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd2,msdos1 --hint-efi=hd2,msdos1 --hint-baremetal=ahci2,msdos1 C08E2C498E2C3A74
else
search --no-floppy --fs-uuid --set=root C08E2C498E2C3A74
fi
parttool $root hidden-
drivemap -s (hd0) $root
chainloader +1
I took that from the working Ubuntu 18.04 GRUB MBR+BIOS installation.
But when I select Windows 10 from the GRUB menu I get just this error:
Setting partition type to 0x7
error: can't fine command `drivemap'.
error: invalid EFI file path.
Is it even possible to boot from an EFI GRUB a BIOS installation on a different disk of Windows 10?
boot grub2 windows uefi grub-efi
TL;DR
How can I boot from a EFI GRUB installation on a disc A a Windows 10 BIOS installation on a disk B?
Long explanationos-prober
is not detecting Windows anymore after having migrated Ubuntu from MBR+BIOS to GPT+EFI.
My disk situation is a little complicated:
sda 1,8T
└─sda1 ext4 1,4T /media/Steam Steam
sdb 931,5G
├─sdb1 vfat 512M
├─sdb2 ext4 125G home
├─sdb3 ext4 774,5G /media/Dati_ext4 Dati_ext4
└─sdb4 ext4 31,5G Ubuntu18.04
sdc 232,9G
├─sdc1 ntfs 100M
├─sdc2 ntfs 59G Win10
├─sdc3 ntfs 483M
└─sdc4 ntfs 172,9G Dati_NTFS
nvme0n1 477G
├─nvme0n1p1 ext4 62,4G / Ubuntu19.10
├─nvme0n1p2 vfat 200M /boot/efi EFI
└─nvme0n1p3 ext4 322,1G /home home
- I have 4 disks (1 NVMe and 3 SSDs).
- Before today they were all using MBR and the UEFI was booting the NVMe in legacy mode.
- I have 2 installation of Ubuntu (19.10 and 18.04) and 1 of Windows 10.
- Each OS has it's own disk (and the 4th disk as no OS installed). This means that each OS had its own boot loader installed on the MBR of each disk.
- GRUB was also able to see every other OS so, from the GRUB of the NVMe, I was able to boot any of the 3 OSs.
Today I decided to convert the NVMe installation of Ubuntu form MBR+BIOS to GPT+EFI. Since I did not touch any other disk, I was hoping that the GRUB will detect the other OSs and boot them normally.
The conversion worked fine and I'm able to boot in Ubuntu 19.10. But os-prober
recognize Ubuntu 18.04 but not Windows 10.
What I would like to do is either to find a fix for os-prober
, so that it recognize Windows, or to manually specify the GRUB configuration to boot the Windows MBR+BIOS installation.
I already tried something for the second approach but it didn't worked.
I added this to the /etc/grub.d/40_custom
of the EFI installation:
menuentry 'Windows 10 (su /dev/sdc1)' --class windows --class os
insmod part_msdos
insmod ntfs
set root='hd2,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd2,msdos1 --hint-efi=hd2,msdos1 --hint-baremetal=ahci2,msdos1 C08E2C498E2C3A74
else
search --no-floppy --fs-uuid --set=root C08E2C498E2C3A74
fi
parttool $root hidden-
drivemap -s (hd0) $root
chainloader +1
I took that from the working Ubuntu 18.04 GRUB MBR+BIOS installation.
But when I select Windows 10 from the GRUB menu I get just this error:
Setting partition type to 0x7
error: can't fine command `drivemap'.
error: invalid EFI file path.
Is it even possible to boot from an EFI GRUB a BIOS installation on a different disk of Windows 10?
boot grub2 windows uefi grub-efi
boot grub2 windows uefi grub-efi
asked Sep 27 at 22:28
Roberto LeinardiRoberto Leinardi
4905 silver badges12 bronze badges
4905 silver badges12 bronze badges
add a comment
|
add a comment
|
1 Answer
1
active
oldest
votes
Short answer, you can't boot a legacy Windows from UEFI grub. Once grub boots, the boot mode has been set to UEFI, and your Windows is in legacy mode, so cannot boot. You can select the device Windows is on (presumably with its own boot loaders), and boot that from the EFI boot menu (some function key at power-up to allow you to select boot device/OS). You could have either another grub installation or Windows boot successfully off that second disk, which would be in legacy mode. Try just booting the second disk, Windows may come up.
I ended up converting the Windows 10 installation to GPT+EFI usingmbr2gpt /convert /allowFullOS
. Nowos-prober
correctly sees it and GRUB boots it.
– Roberto Leinardi
Sep 27 at 23:39
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/4.0/"u003ecc by-sa 4.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%2f1177167%2funable-to-detect-boot-windows-10-after-converting-ubuntu-from-mbrbios-to-gptef%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
Short answer, you can't boot a legacy Windows from UEFI grub. Once grub boots, the boot mode has been set to UEFI, and your Windows is in legacy mode, so cannot boot. You can select the device Windows is on (presumably with its own boot loaders), and boot that from the EFI boot menu (some function key at power-up to allow you to select boot device/OS). You could have either another grub installation or Windows boot successfully off that second disk, which would be in legacy mode. Try just booting the second disk, Windows may come up.
I ended up converting the Windows 10 installation to GPT+EFI usingmbr2gpt /convert /allowFullOS
. Nowos-prober
correctly sees it and GRUB boots it.
– Roberto Leinardi
Sep 27 at 23:39
add a comment
|
Short answer, you can't boot a legacy Windows from UEFI grub. Once grub boots, the boot mode has been set to UEFI, and your Windows is in legacy mode, so cannot boot. You can select the device Windows is on (presumably with its own boot loaders), and boot that from the EFI boot menu (some function key at power-up to allow you to select boot device/OS). You could have either another grub installation or Windows boot successfully off that second disk, which would be in legacy mode. Try just booting the second disk, Windows may come up.
I ended up converting the Windows 10 installation to GPT+EFI usingmbr2gpt /convert /allowFullOS
. Nowos-prober
correctly sees it and GRUB boots it.
– Roberto Leinardi
Sep 27 at 23:39
add a comment
|
Short answer, you can't boot a legacy Windows from UEFI grub. Once grub boots, the boot mode has been set to UEFI, and your Windows is in legacy mode, so cannot boot. You can select the device Windows is on (presumably with its own boot loaders), and boot that from the EFI boot menu (some function key at power-up to allow you to select boot device/OS). You could have either another grub installation or Windows boot successfully off that second disk, which would be in legacy mode. Try just booting the second disk, Windows may come up.
Short answer, you can't boot a legacy Windows from UEFI grub. Once grub boots, the boot mode has been set to UEFI, and your Windows is in legacy mode, so cannot boot. You can select the device Windows is on (presumably with its own boot loaders), and boot that from the EFI boot menu (some function key at power-up to allow you to select boot device/OS). You could have either another grub installation or Windows boot successfully off that second disk, which would be in legacy mode. Try just booting the second disk, Windows may come up.
answered Sep 27 at 22:43
ubfan1ubfan1
11.1k4 gold badges20 silver badges31 bronze badges
11.1k4 gold badges20 silver badges31 bronze badges
I ended up converting the Windows 10 installation to GPT+EFI usingmbr2gpt /convert /allowFullOS
. Nowos-prober
correctly sees it and GRUB boots it.
– Roberto Leinardi
Sep 27 at 23:39
add a comment
|
I ended up converting the Windows 10 installation to GPT+EFI usingmbr2gpt /convert /allowFullOS
. Nowos-prober
correctly sees it and GRUB boots it.
– Roberto Leinardi
Sep 27 at 23:39
I ended up converting the Windows 10 installation to GPT+EFI using
mbr2gpt /convert /allowFullOS
. Now os-prober
correctly sees it and GRUB boots it.– Roberto Leinardi
Sep 27 at 23:39
I ended up converting the Windows 10 installation to GPT+EFI using
mbr2gpt /convert /allowFullOS
. Now os-prober
correctly sees it and GRUB boots it.– Roberto Leinardi
Sep 27 at 23:39
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%2f1177167%2funable-to-detect-boot-windows-10-after-converting-ubuntu-from-mbrbios-to-gptef%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