From: John Robinson <john.robinson@anonymous.org.uk>
To: jlcenter@comcast.net
Cc: linux-raid@vger.kernel.org
Subject: Re: Install grub2 to /dev/md126 fails
Date: Sat, 07 Jan 2012 15:39:06 +0000 [thread overview]
Message-ID: <4F08671A.6090403@anonymous.org.uk> (raw)
In-Reply-To: <123493149.466191.1325863934205.JavaMail.root@sz0019a.westchester.pa.mail.comcast.net>
On 06/01/2012 15:32, jlcenter@comcast.net wrote:
> Hi,
>
> I'm going to try again to build the raid1 array, but I was wondering
> if the GPT partitions should be created first on the physical disks,
> then create& assemble the array? Or, if the array should be
> created& assembled, then partition the array? I'm raiding the whole
> disk(s), not partitions. Reading the wiki, I get the impression the
> first way is preferable, but most of the descriptions I've read
> on-line suggest doing the latter. Also, for mdadm with GPT
> partitions, is there any preferred order to the partitions, i.e.,
> does the bios boot partition have to be the first partition on the
> array?
If my understanding is correct, you want an IMSM array that can be
booted by a uEFI BIOS? In which case, I think you need an array over the
whole disks (which might give you a /dev/md127 for a container, and
/dev/md126 for the data), GPT partition table over that, first partition
a GPT boot partition (so you will be installing GRUB2 to /dev/md126p1 -
this is NOT a filesystem partition), and then whatever you want after
that, e.g. to keep it simple a /dev/md126p2 for swap and /dev/md126p3
for your filesystem.
If you don't have a uEFI BIOS, it gets more complicated; you will need a
hybrid MBR with a traditional boot sector and at least the GPT boot
partition exposed :-(
Caveat: I've read a lot but I haven't actually done this, so I may be
talking rubbish...
Cheers,
John.
prev parent reply other threads:[~2012-01-07 15:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-31 3:59 Install grub2 to /dev/md126 fails jlcenter
2012-01-02 23:34 ` NeilBrown
2012-01-06 3:43 ` jlcenter
2012-01-03 10:55 ` Jes Sorensen
2012-01-04 1:35 ` jlcenter
2012-01-04 2:24 ` Jérôme Poulin
2012-01-06 15:32 ` jlcenter
2012-01-07 15:39 ` John Robinson [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=4F08671A.6090403@anonymous.org.uk \
--to=john.robinson@anonymous.org.uk \
--cc=jlcenter@comcast.net \
--cc=linux-raid@vger.kernel.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 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).