From: Colin Watson <cjwatson@ubuntu.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Is it possible to have grub2's boot.img as my MBR, but have it look in a separate partition for core.img?
Date: Thu, 28 Jan 2010 11:45:47 +0000 [thread overview]
Message-ID: <20100128114547.GI4409@riva.ucam.org> (raw)
In-Reply-To: <loom.20100128T041511-405@post.gmane.org>
On Thu, Jan 28, 2010 at 03:37:44AM +0000, Wesley Smith wrote:
> I am sorry to bother you, but reading the docs has not helped, and Googling has
> turned up only other people suffering from the same problem, but not the
> solution to it.
>
> I have a multiboot system that I would like to use Grub to manage. The version
> of Grub shipping with my Linux distro is Grub2, and it installs its equivalent
> of core.img into the remaining sectors on the first track after the MBR but
> before the first partition. Unfortunately, those sectors are needed by another
> program.
>
> I have a separate primary /boot partition, with the rest of my Linux distro
> stored in an LVM. If I could only keep boot.img as my MBR but have it look in
> the /boot partition for core.img rather than having it read an embedded one from
> the sectors immediately following the MBR, everything would work fine. Is this
> possible with Grub2?
Yes, you can do this by using 'grub-install /dev/sda1' (or whatever the
device name for your /boot partition is).
Note that this setup typically requires the use of blocklists, which are
inherently unreliable. For example, you may find that you need to
re-run grub-install after certain filesystem operations; see the "And
blocklists?" section of http://grub.enbug.org/BIOS_Boot_Partition for a
description of the problem. This problem was present in GRUB Legacy as
well, although it did not warn about it.
--
Colin Watson [cjwatson@ubuntu.com]
next prev parent reply other threads:[~2010-01-28 11:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 3:37 Is it possible to have grub2's boot.img as my MBR, but have it look in a separate partition for core.img? Wesley Smith
2010-01-28 11:45 ` Colin Watson [this message]
2010-01-28 14:11 ` edgar.soldin
2010-01-28 14:55 ` Colin Watson
2010-01-28 16:39 ` edgar.soldin
[not found] ` <ca0f59981001280857p5f581035n4cd8519efda30e8@mail.gmail.com>
2010-01-28 17:15 ` edgar.soldin
[not found] ` <ca0f59981001280936o4457ff96wc95dad6f238ff461@mail.gmail.com>
2010-01-28 17:41 ` edgar.soldin
2010-01-29 5:43 ` Wesley Smith
2010-01-29 6:19 ` Bruce Dubbs
2010-01-29 9:54 ` Wesley Smith
2010-01-29 9:48 ` Grégoire Sutre
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=20100128114547.GI4409@riva.ucam.org \
--to=cjwatson@ubuntu.com \
--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.