Question

11

"GPT detected. Please create a BIOS-Boot partition" while using boot-repair

rated 0 times [ 11] [ 0] / answers: 1 / hits: 97331 / 1 Year ago, fri, may 12, 2023, 10:11:01

Since I updated Windows to 8.1 my Grub menu disappeared. I ran Ubuntu using Live USB, I used Boot-Repair but something went wrong. If I click on Reccomended repair I get this error:

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.

So I tried to set my sda9 (I think that it's the Ubuntu system partition, since it's ext4) with the bios_grub flag and then to run Boot-Repair again. It didn't work.

I don't know what to do. My Grub was working fine (using UEFI) before I updated Windows.

I removed the bios_grub flag. Then I used fsck and it didn't find any error. So I tried again with Boot-Repair but it always gives me the "GPT detected" error. My boot is on UEFI mode, Secure Boot is "off".

When I boot my PC with SecureBoot OFF, I can reach the GRUB menu. But it's empty (the only voice is "System Setup").

I mounted my Ubuntu system disk:

sudo mount /dev/sda9 /mnt

and the other things:

sudo mount --bind /dev /mnt/dev

sudo mount --bind /proc /mnt/proc

sudo mount --bind /sys /mnt/sys

I logged on the system with chroot:

sudo chroot /mnt

I re-installed grub:

grub-install /dev/sda

update-grub2

But it still doesn't work.

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

luringdge

Add To Favorites

Follow

Total Points: 3

Total Questions: 126

Total Answers: 109

Location: India

Member since Sun, Feb 6, 2022

2 Years ago

answered 1 Year ago odenanno · Accepted Answer

First, the bios_grub flag in parted or GParted is a way to identify a BIOS Boot Partition. GRUB 2 uses this partition to hold part of its boot code when the computer boots in BIOS mode. It's normally about 1MiB in size, although it can be smaller in some cases. Most importantly, if Boot Repair re-ran the GRUB installer after you set the bios_grub flag on your Linux root (/) partition, you may have trashed that partition. Thus, before you do anything else, I recommend you:

Remove the bios_grub flag from your Linux root (/) partition.

Test your Linux root (/) partition with fsck (or equivalent functionality in GParted or other GUI tools). If the partition has errors, fix them or restore your system from a backup. Only once you're sure that you can mount the partition and use it normally should you proceed.

Second, you had this problem because you booted your emergency disc in BIOS/CSM/legacy mode rather than in EFI mode. You need to learn how to control your computer's boot mode. You can usually do this via a boot manager that's accessed by hitting Esc or a function key early in the boot process (before GRUB appears); but there's no standardization on how to access this boot manager or what options it provides. Thus, you may need to experiment to figure this out.

Third, if you can figure out how to boot your live CD in EFI mode, Boot Repair should fix the problem. Alternatively, you should be able to use a CD-R or USB flash drive version of my rEFInd boot manager to get Linux booted. Once Linux is up and running, you should be able to use efibootmgr to restore GRUB as the default boot loader, but the details depend on how it's configured now. Briefly, you must use the -o option to efibootmgr to set GRUB's entry as the first one. This question and answers cover the issue from a different angle. Instead of restoring GRUB, you could consider installing rEFInd to your hard disk, too.

EDIT: Try using my rEFInd boot manager: Use the USB flash drive or CD-R image to create a suitable medium and boot from that. This should give you an option for Windows and at least one option for Linux. If you can boot both Windows and Linux, install the Debian package of rEFInd in Linux. This should switch the computer to use rEFInd by default, and you should be able to boot everything normally.