From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: John Robinson <john.robinson@anonymous.org.uk>
Cc: "Lars Täuber" <taeuber@bbaw.de>, linux-raid@vger.kernel.org
Subject: Re: grub2/grub-pc install not possible on mdadm
Date: Fri, 02 Mar 2012 14:15:08 +0100 [thread overview]
Message-ID: <4F50C7DC.3000700@profihost.ag> (raw)
In-Reply-To: <4F50ABA3.1070603@anonymous.org.uk>
> No. When booting with MBR, all that goes in the boot sector is enough to
> load the next stage. That next stage will include the raid1x module. It
> lives in the gap between the MBR and the first partition - with old
> fdisk, that was 31K, with more recent fdisk it's 1MB. With no partition
> table on the drives and 1.2 metadata, there's only 3.5K for it, which
> isn't enough.
But that's why i've a BIOS_GRUB partition on the raid and so also on the
disk. Shouldn't it be the same size for 0.9 which starts at the
beginning, too?
> What's actually happening with metadata 0.90 or 1.0, because they have
> their data from the beginning, is that the partition table, GRUB etc
> that you have installed into md127 appears to the BIOS as two drives
> with boot sectors, partition tables, etc, and it then proceeds to boot
> off the first drive.
So the bios needs to read the partition table? I thought the MBR would
be enough.
> Until grub has loaded, you rely on the fact that
> what you installed inside the RAID-1 is laid out in exactly the way the
> BIOS expects to find it on a single drive.
>
> What you've done with metadata 1.2 is put GRUB in a place that needs
> GRUB to find it.
With metadata 0.9 i can install grub on sda and sdb even when there's no
part. table.
But with 1.2 grub says it cannot find a partition table so it cannot
install . So it seems to be a grub bug? grub-probe correctly dectecs a
1.2 metadata md raid on the disks but then still doesn't want to install
with the no partition table message.
Stefan
next prev parent reply other threads:[~2012-03-02 13:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 9:10 grub2/grub-pc install not possible on mdadm Stefan Priebe - Profihost AG
2012-03-01 10:10 ` Jes Sorensen
2012-03-01 10:25 ` Stefan Priebe - Profihost AG
2012-03-01 10:38 ` Jes Sorensen
2012-03-02 8:44 ` Stefan Priebe - Profihost AG
2012-03-02 9:06 ` Lars Täuber
2012-03-02 9:11 ` Stefan Priebe - Profihost AG
2012-03-02 9:24 ` John Robinson
2012-03-02 9:33 ` Stefan Priebe - Profihost AG
2012-03-02 11:14 ` John Robinson
2012-03-02 13:15 ` Stefan Priebe - Profihost AG [this message]
2012-03-02 13:45 ` John Robinson
2012-03-02 15:32 ` Lars Täuber
2012-03-05 7:50 ` Stefan Priebe - Profihost AG
2012-03-05 9:38 ` John Robinson
2012-03-05 10:14 ` Lars Täuber
2012-03-05 11:31 ` John Robinson
2012-03-05 11:38 ` Lars Täuber
2012-03-05 12:34 ` John Robinson
2012-03-02 9:14 ` Lars Täuber
2012-03-02 9:15 ` Lars Täuber
2012-03-02 10:56 ` Jes Sorensen
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=4F50C7DC.3000700@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=john.robinson@anonymous.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=taeuber@bbaw.de \
/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.