From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: linux-raid@vger.kernel.org
Subject: Re: grub2/grub-pc install not possible on mdadm
Date: Fri, 02 Mar 2012 11:56:17 +0100 [thread overview]
Message-ID: <4F50A751.8020504@redhat.com> (raw)
In-Reply-To: <4F508864.4050600@profihost.ag>
On 03/02/12 09:44, Stefan Priebe - Profihost AG wrote:
>
>> Looking at your original mail again - you are running a raid with
>> metadata 1.2, which means your BIOS will not know how to read the disks
>> as a raid device.
>> You should be able to install grub into the MBR of /dev/sda or /dev/sdb.
>> I believe that is possible with 1.2 metadata. 1.1 was totally broken for
>> this if I remember correctly.
>
> Correct that's why i've also tried to install it on sda / sdb but then
> grub complains about not finding any partition table.
Well there is no point in trying to install it onto the actual RAID
since that is guaranteed not to work. Why it fails on sda/sdb like that
I cannot explain.
>> That said, if your system is EFI based, I suspect you will need to have
>> the bios_grub partition on the physical drives so the BIOS can read it.
>> It's not going to do much good having it on the raid partition if the
>> BIOS isn't able to read those.
> The bios is not the problem - grub simply does not want to install it
> boot sector to sda / sdb.
>
> It does it fine when using metadata 0.9.
I cannot say why it fails like this, maybe someone else knows more but
Neil did reply to you earlier with a summary on metadata and boot loaders:
Quote:
So 1.0 is good for boot loaders
1.1 is bad for boot loaders
1.2 is OK for boot loaders and good for other reasons (resizeable
devices).
Alternatively, why not just create a partition table on the drivers,
reserve a couple of MBs for the boot loader information and the problems
should go away?
Jes
prev parent reply other threads:[~2012-03-02 10:56 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
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 [this message]
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=4F50A751.8020504@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=s.priebe@profihost.ag \
/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;
as well as URLs for NNTP newsgroup(s).