Bug#494589: grub-setup fails with "error message = file not found"

[Robert Millan]

On Wed, Aug 13, 2008 at 01:04:14PM -0400, Edward Allcutt wrote:
> Robert Millan wrote:
> >On Wed, Aug 13, 2008 at 11:53:27AM -0400, Edward Allcutt wrote:
> >>[1] http://dev.teamgleim.com/~emallcut/grub2/grub-setup.log
> >
> >>grub-setup: info: will leave the core image on the filesystem
> >
> >The blocklist approach should still work, but it's not recommended.
> I was actually unaware that grub2 was using a blocklist. I thought it 
> always embedded the core image.

It embeds core.img whenever possible, which on GPT depends on whether you
have a dedicated partition for BIOS boot or not.

> >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.

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."