Dualboot upgrade gone wrong. Boot-repair cannot find Windows. How can I add this BIOS-Boot partition?
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgO9GURib1T8z7lCwjOGLQaGtrueEthgQ8LO42ZX8cOfTqDK4jvDDpKkLFwf2J49kYCMNW7d4ABih_XCb_2UXdq5fPJDkoyg7-8g_YfRUot-XnaXkNYycsNp7lA5_TW9td0FFpLQ2APzKcZ/s1600/1.jpg)
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhYQ0N5W1qAOxLP7t7iOM6O6AzbZnkXUy16s7P_CWfOb5UbTQY_aDsc727chyphenhyphen5W4IppVNernMMQeaUFTB_rFzAd95_CDt-tnwN-nBx6JyUp2duGjPaL5-VgNO41AVsA_vu30EJcipdDG409/s400/Clash+Royale+CLAN+TAG%2523URR8PPP.png)
up vote
0
down vote
favorite
After a long time away from Linux I thought: "I'll just add extra SSD,
it should be easy..."
Wrong. I messed up everything.
After install, boot-repair tells me:
GPT detected. Please create a BIOS-Boot partition (>1MB, unformatted filesystem, bios_grub flag). This can be performed via tools such as Gparted. Then try again. Alternatively, you can retry after activating the [Separate /boot/efi partition:] option.
How can I add this BIOS-Boot partition without breaking the Ubuntu install?
My system is like:
sda 223,6G
âÂÂâÂÂsda1 vfat 223,6G /mnt/boot-sav/sda1 240
sdb 931,5G
âÂÂâÂÂsdb1 ntfs 223G /mnt/boot-sav/sdb1
âÂÂâÂÂsdb2 ntfs 467M /mnt/boot-sav/sdb2
âÂÂâÂÂsdb3 16M
sdc 489,1G
âÂÂâÂÂsdc1 vfat 512M /boot/efi
âÂÂâÂÂsdc2 ext4 488,6G /
sr0 1024M
sda
is empty SSD.sdb
in Windows 10 hard disk.sdc
is current Ubuntu SSD.
Where should I start?
dual-boot grub2 partitioning uefi 18.04
add a comment |Â
up vote
0
down vote
favorite
After a long time away from Linux I thought: "I'll just add extra SSD,
it should be easy..."
Wrong. I messed up everything.
After install, boot-repair tells me:
GPT detected. Please create a BIOS-Boot partition (>1MB, unformatted filesystem, bios_grub flag). This can be performed via tools such as Gparted. Then try again. Alternatively, you can retry after activating the [Separate /boot/efi partition:] option.
How can I add this BIOS-Boot partition without breaking the Ubuntu install?
My system is like:
sda 223,6G
âÂÂâÂÂsda1 vfat 223,6G /mnt/boot-sav/sda1 240
sdb 931,5G
âÂÂâÂÂsdb1 ntfs 223G /mnt/boot-sav/sdb1
âÂÂâÂÂsdb2 ntfs 467M /mnt/boot-sav/sdb2
âÂÂâÂÂsdb3 16M
sdc 489,1G
âÂÂâÂÂsdc1 vfat 512M /boot/efi
âÂÂâÂÂsdc2 ext4 488,6G /
sr0 1024M
sda
is empty SSD.sdb
in Windows 10 hard disk.sdc
is current Ubuntu SSD.
Where should I start?
dual-boot grub2 partitioning uefi 18.04
You already have that partition assdc1
, I believe. Just boot-repair or your BIOS/UEFI now wants to boot fromsda
as your first drive, instead ofsdc
which contains the boot loader and EFI files. Can you just try and swap them around in your UEFI setup? If that doesn't work, you might try swapping their cables.
â Byte Commander
May 20 at 22:31
Not quite. The bios_grub is for BIOS boot on gpt partitioned drives. Normally gpt is used with UEFI and with UEFI boot you must have an ESP - efi system partition which is FAT32 with boot flag. You must be consistent in how you boot installer, and then your hard drive after install. And any repair flash drives. Once using UEFI with gpt always boot in UEFI boot mode. And if Windows boots in UEFI boot mode only use gpt & UEFI boot. But if booting in BIOS mode from gpt, then you must have a bios_grub partition. Best to use same boot mode as Windows and better to use UEFI with newer UEFI.
â oldfred
May 20 at 22:54
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
After a long time away from Linux I thought: "I'll just add extra SSD,
it should be easy..."
Wrong. I messed up everything.
After install, boot-repair tells me:
GPT detected. Please create a BIOS-Boot partition (>1MB, unformatted filesystem, bios_grub flag). This can be performed via tools such as Gparted. Then try again. Alternatively, you can retry after activating the [Separate /boot/efi partition:] option.
How can I add this BIOS-Boot partition without breaking the Ubuntu install?
My system is like:
sda 223,6G
âÂÂâÂÂsda1 vfat 223,6G /mnt/boot-sav/sda1 240
sdb 931,5G
âÂÂâÂÂsdb1 ntfs 223G /mnt/boot-sav/sdb1
âÂÂâÂÂsdb2 ntfs 467M /mnt/boot-sav/sdb2
âÂÂâÂÂsdb3 16M
sdc 489,1G
âÂÂâÂÂsdc1 vfat 512M /boot/efi
âÂÂâÂÂsdc2 ext4 488,6G /
sr0 1024M
sda
is empty SSD.sdb
in Windows 10 hard disk.sdc
is current Ubuntu SSD.
Where should I start?
dual-boot grub2 partitioning uefi 18.04
After a long time away from Linux I thought: "I'll just add extra SSD,
it should be easy..."
Wrong. I messed up everything.
After install, boot-repair tells me:
GPT detected. Please create a BIOS-Boot partition (>1MB, unformatted filesystem, bios_grub flag). This can be performed via tools such as Gparted. Then try again. Alternatively, you can retry after activating the [Separate /boot/efi partition:] option.
How can I add this BIOS-Boot partition without breaking the Ubuntu install?
My system is like:
sda 223,6G
âÂÂâÂÂsda1 vfat 223,6G /mnt/boot-sav/sda1 240
sdb 931,5G
âÂÂâÂÂsdb1 ntfs 223G /mnt/boot-sav/sdb1
âÂÂâÂÂsdb2 ntfs 467M /mnt/boot-sav/sdb2
âÂÂâÂÂsdb3 16M
sdc 489,1G
âÂÂâÂÂsdc1 vfat 512M /boot/efi
âÂÂâÂÂsdc2 ext4 488,6G /
sr0 1024M
sda
is empty SSD.sdb
in Windows 10 hard disk.sdc
is current Ubuntu SSD.
Where should I start?
dual-boot grub2 partitioning uefi 18.04
edited May 20 at 22:28
![](https://i.stack.imgur.com/m8DYH.jpg?s=32&g=1)
![](https://i.stack.imgur.com/m8DYH.jpg?s=32&g=1)
Byte Commander
58.1k26155264
58.1k26155264
asked May 20 at 21:58
foolevil
12
12
You already have that partition assdc1
, I believe. Just boot-repair or your BIOS/UEFI now wants to boot fromsda
as your first drive, instead ofsdc
which contains the boot loader and EFI files. Can you just try and swap them around in your UEFI setup? If that doesn't work, you might try swapping their cables.
â Byte Commander
May 20 at 22:31
Not quite. The bios_grub is for BIOS boot on gpt partitioned drives. Normally gpt is used with UEFI and with UEFI boot you must have an ESP - efi system partition which is FAT32 with boot flag. You must be consistent in how you boot installer, and then your hard drive after install. And any repair flash drives. Once using UEFI with gpt always boot in UEFI boot mode. And if Windows boots in UEFI boot mode only use gpt & UEFI boot. But if booting in BIOS mode from gpt, then you must have a bios_grub partition. Best to use same boot mode as Windows and better to use UEFI with newer UEFI.
â oldfred
May 20 at 22:54
add a comment |Â
You already have that partition assdc1
, I believe. Just boot-repair or your BIOS/UEFI now wants to boot fromsda
as your first drive, instead ofsdc
which contains the boot loader and EFI files. Can you just try and swap them around in your UEFI setup? If that doesn't work, you might try swapping their cables.
â Byte Commander
May 20 at 22:31
Not quite. The bios_grub is for BIOS boot on gpt partitioned drives. Normally gpt is used with UEFI and with UEFI boot you must have an ESP - efi system partition which is FAT32 with boot flag. You must be consistent in how you boot installer, and then your hard drive after install. And any repair flash drives. Once using UEFI with gpt always boot in UEFI boot mode. And if Windows boots in UEFI boot mode only use gpt & UEFI boot. But if booting in BIOS mode from gpt, then you must have a bios_grub partition. Best to use same boot mode as Windows and better to use UEFI with newer UEFI.
â oldfred
May 20 at 22:54
You already have that partition as
sdc1
, I believe. Just boot-repair or your BIOS/UEFI now wants to boot from sda
as your first drive, instead of sdc
which contains the boot loader and EFI files. Can you just try and swap them around in your UEFI setup? If that doesn't work, you might try swapping their cables.â Byte Commander
May 20 at 22:31
You already have that partition as
sdc1
, I believe. Just boot-repair or your BIOS/UEFI now wants to boot from sda
as your first drive, instead of sdc
which contains the boot loader and EFI files. Can you just try and swap them around in your UEFI setup? If that doesn't work, you might try swapping their cables.â Byte Commander
May 20 at 22:31
Not quite. The bios_grub is for BIOS boot on gpt partitioned drives. Normally gpt is used with UEFI and with UEFI boot you must have an ESP - efi system partition which is FAT32 with boot flag. You must be consistent in how you boot installer, and then your hard drive after install. And any repair flash drives. Once using UEFI with gpt always boot in UEFI boot mode. And if Windows boots in UEFI boot mode only use gpt & UEFI boot. But if booting in BIOS mode from gpt, then you must have a bios_grub partition. Best to use same boot mode as Windows and better to use UEFI with newer UEFI.
â oldfred
May 20 at 22:54
Not quite. The bios_grub is for BIOS boot on gpt partitioned drives. Normally gpt is used with UEFI and with UEFI boot you must have an ESP - efi system partition which is FAT32 with boot flag. You must be consistent in how you boot installer, and then your hard drive after install. And any repair flash drives. Once using UEFI with gpt always boot in UEFI boot mode. And if Windows boots in UEFI boot mode only use gpt & UEFI boot. But if booting in BIOS mode from gpt, then you must have a bios_grub partition. Best to use same boot mode as Windows and better to use UEFI with newer UEFI.
â oldfred
May 20 at 22:54
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1038499%2fdualboot-upgrade-gone-wrong-boot-repair-cannot-find-windows-how-can-i-add-this%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
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
You already have that partition as
sdc1
, I believe. Just boot-repair or your BIOS/UEFI now wants to boot fromsda
as your first drive, instead ofsdc
which contains the boot loader and EFI files. Can you just try and swap them around in your UEFI setup? If that doesn't work, you might try swapping their cables.â Byte Commander
May 20 at 22:31
Not quite. The bios_grub is for BIOS boot on gpt partitioned drives. Normally gpt is used with UEFI and with UEFI boot you must have an ESP - efi system partition which is FAT32 with boot flag. You must be consistent in how you boot installer, and then your hard drive after install. And any repair flash drives. Once using UEFI with gpt always boot in UEFI boot mode. And if Windows boots in UEFI boot mode only use gpt & UEFI boot. But if booting in BIOS mode from gpt, then you must have a bios_grub partition. Best to use same boot mode as Windows and better to use UEFI with newer UEFI.
â oldfred
May 20 at 22:54