From: Edward Allcutt <emallcut@gleim.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Cc: 494589@bugs.debian.org
Subject: Re: grub-setup fails with "error message = file not found"
Date: Wed, 13 Aug 2008 15:12:22 -0400 [thread overview]
Message-ID: <48A33216.70106@gleim.com> (raw)
In-Reply-To: <20080813172817.GA13237@thorin>
Robert Millan wrote:
> On Wed, Aug 13, 2008 at 01:04:14PM -0400, Edward Allcutt wrote:
>> Robert Millan wrote:
>>> I suggest you allow GRUB to embed core.img instead by adding a BIOS boot
>>> partitition using Parted. We still need to trace down the problem with
>>> blocklists, but this will tell us whether the problem is related to this
>>> or something else.
>> I set the "boot" flag for /dev/sda1 using parted. I hope this is what
>> you meant. grub-setup still fails with the same error and it still
>> mentions "will leave the core image on the filesystem".
>
> The "boot" flag on GPT means "EFI system partition" (this is admittedly
> confusing). There's a flag for bios boot, but only in recent versions of
> Parted. But of course, I wouldn't do that to your existing sda1 unless
> you want it to be wiped with GRUB code.
I wish there were another tool supporting GPT. parted is a real pain to
use. Still I've got a dedicated "BIOS boot" partition now and grub-setup
seems happy to embed core.img on it without any errors.
While my problem is resolved it seems like there's still an annoying bug
in either the ext2 driver or whatever else is involved in generating
blocklists.
Thanks for the quick responses :)
--
Edward Allcutt
Network Operations
next prev parent reply other threads:[~2008-08-13 19:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-13 15:53 grub-setup fails with "error message = file not found" Edward Allcutt
2008-08-13 16:44 ` Robert Millan
2008-08-13 17:04 ` Edward Allcutt
2008-08-13 17:28 ` Robert Millan
2008-08-13 19:12 ` Edward Allcutt [this message]
2008-08-13 17:03 ` Robert Millan
2008-08-13 17:54 ` Edward Allcutt
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=48A33216.70106@gleim.com \
--to=emallcut@gleim.com \
--cc=494589@bugs.debian.org \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.