From: John Robinson <john.robinson@anonymous.org.uk>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: "Lars Täuber" <taeuber@bbaw.de>, linux-raid@vger.kernel.org
Subject: Re: grub2/grub-pc install not possible on mdadm
Date: Mon, 05 Mar 2012 09:38:34 +0000 [thread overview]
Message-ID: <4F54899A.4040301@anonymous.org.uk> (raw)
In-Reply-To: <4F547038.7060009@profihost.ag>
On 05/03/2012 07:50, Stefan Priebe - Profihost AG wrote:
> Am 02.03.2012 16:32, schrieb Lars Täuber:
>> Hi Stefan,
>>
>> the metadata versions 1.0 and 1.1 and 1.2 are the same but for the position of
>> the metadata on disk. Simply use metadata version 1.0 and everything works as
>> with 0.9.
>>
>> Grub does to read partition tables inside raid devices.
Sure it does, but that's not the point.
>> Because a raid1 with metadata 1.0 or 0.9 looks like a plain disk to grub it
>> can read a partition table like there was no raid array.
For the fourth time, no.
Because a RAID1 with metadata 0.9 or 1.0 looks like a plain disc to the
BIOS, it can read a partition table like there was no RAID array, and
therefore the BIOS can load GRUB.
> Ah OK thanks. using Metadata 1.0 works fine.
It will work OK, but just be very, very careful never to run a GPT
partition tool directly on /dev/sda or /dev/sdb, because it will write
the backup of the GPT partition table at the end of the disc,
potentially destroying the metadata for the array.
You would still be safer having partition tables on the drives, and
building your array(s) from those partition(s), the opposite way round
from how you are doing it just now.
Cheers,
John.
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-03-05 9:38 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 [this message]
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=4F54899A.4040301@anonymous.org.uk \
--to=john.robinson@anonymous.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=s.priebe@profihost.ag \
--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 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).