From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Grub fails. I missed something.
Date: Mon, 17 Mar 2025 08:21:29 +0000 [thread overview]
Message-ID: <8504219.T7Z3S40VBb@rogueboard> (raw)
In-Reply-To: <f873ee9b-de06-7a78-3d1e-00d6f7dddeae@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1747 bytes --]
On Monday, 17 March 2025 02:34:47 Greenwich Mean Time Dale wrote:
> Grant Edwards wrote:
> > On 2025-03-16, Michael <confabulate@kintzios.com> wrote:
> >> Ugh! I didn't provide a comprehensive answer - sorry. All this MBR
> >> nostalgia I've been trying to forget. LOL!
> >>
> >> If you are installing GRUB on a GPT disk, which is meant to boot on
> >> a legacy BIOS MoBo, you *must* create a BIOS Boot Partition (gdisk
> >> code EF02). GRUB will drop its boot.img in the disk's MBR (sector
> >> 0) then would try to install its core.img in sector 1, exactly where
> >> GPT has stored its own primary table. With a BIOS Boot Partition
> >> this clash is averted.
> >
> > You /can/ use an embedded block list to install legacy BIOS boot mode
> > grub using an MBR table without a BIOS Boot Partition, but don't do
> > it. It requires manual intervention any time grub gets updated, so it's
> > a pain to maintain. The "right" answer is to create a BIOS boot
> > partition. Then it will "just work".
>
> I can second that, from experience. I might add while I'm typing, I'm
> getting ready to update my backups. I just booted the NAS box. I hit
> the power button on the way to my chair. By the time I read your reply,
> it was already sitting at the login prompt. I think it boots a little
> faster. Having the OS on a SSD might be a little faster.
>
> While I like the new GPT way, I really need to use the old way on the
> older hardware. I just keep forgetting to. :/
>
> Dale
>
> :-) :-)
Details on size recommendation for storing GRUB Stage 2 image is details here,
including the parted stanza for creating a BIOS Boot Partition on GPT disks:
https://www.gnu.org/software/grub/manual/grub/grub.html#BIOS-installation
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-03-17 8:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-15 7:29 [gentoo-user] Grub fails. I missed something Dale
2025-03-15 9:18 ` Michael
2025-03-15 20:42 ` Dale
2025-03-15 21:43 ` eric
2025-03-16 2:15 ` William Kenworthy
2025-03-16 5:04 ` Dale
2025-03-16 5:34 ` William Kenworthy
2025-03-16 7:30 ` Dale
2025-03-16 9:58 ` Dale
2025-03-16 11:40 ` Michael
2025-03-16 14:05 ` Michael
2025-03-16 19:14 ` Dale
2025-03-17 1:01 ` [gentoo-user] " Grant Edwards
2025-03-17 2:34 ` Dale
2025-03-17 8:21 ` Michael [this message]
2025-03-17 13:28 ` Grant Edwards
2025-03-17 3:50 ` [gentoo-user] " Dale
2025-03-17 8:10 ` Michael
2025-03-20 2:25 ` Dale
2025-03-23 5:41 ` Dale
2025-03-23 22:28 ` Frank Steinmetzger
2025-03-24 0:38 ` Dale
2025-03-18 22:35 ` Frank Steinmetzger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8504219.T7Z3S40VBb@rogueboard \
--to=confabulate@kintzios.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox