All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthonys Lists <antlists@youngman.org.uk>
To: "Wilson, Jonathan" <piercing_male@hotmail.com>,
	Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: UEFI and mdadm questions.
Date: Thu, 02 Oct 2014 01:17:55 +0100	[thread overview]
Message-ID: <542C99B3.6060809@youngman.org.uk> (raw)
In-Reply-To: <BLU436-SMTP10330CBEBC0CA1E27853BE498B80@phx.gbl>

On 01/10/2014 17:33, Wilson, Jonathan wrote:

I've just been struggling with exactly this trying to move my gentoo 
system on to raid ...
>  From what I can tell with UEFI I need to set up a UEFI partition with a
> FAT format.

I believe so, yes.
>
> On my current BIOS system I have a Biosboot 1M, /boot Raid1 200M and /
> Raid 1 40G.
>
> Obviously Grub installs to the mbr, and then installs a bit into
> Biosboot which can read raids, hence it can read and boot from /boot.

Is this grub1, or grub2? I gather grub1 actually CAN'T read raid, which 
is why you need to use raid version 0.9. Grub then thinks the disk is 
plain ext4 or whatever, and reads it fine. grub2 actually handles raid, 
and therefore is happy with newer raids like 1.2
>
> Further, from what I can tell, into the UEFI partition can go either a
> kernel & initramfs with UEFI support, or a "loader" that then loads the
> kernel.
>
> What I am unsure about are...
>
> 1)  Can the loader/kernel understand md raid? so the / can be in a bog
> standard raid1 v1.2?

Don't think so. Apparently the kernel can NOT put a raid array together 
so you have a catch-22 - the kernel needs the raid in order to start 
user-space, but it needs user-space in order to find the raid ... :-(

So you need an initramfs to solve the conundrum. And of course, grub1 
doesn't work with uefi :-(
>
> 2) I'm guessing I would no longer need the /boot as that would be
> replaced by what ever was in the UEFI partition?

You do need /boot - not least so grub2 can find its config file (that's 
not quite true, but close enough...)

>
> 3) as my "/boot" is currently in a raid 1 my life is simple, should any
> changes occur they are replicated to the drives I have set up as /boot
> raid 1, and I installed the mbr portion of boot loader manually on each
> disk and tested pulling one, and then booting from another.. it
> worked :-)

In the world of grub2/raid1.2 I wish things looked that simple. From my 
"badly burned novice" viewpoint, I don't think it is.

> So I would like to keep things, if not simple, at least less likely to
> have problems because I forgot to install duplicates of the UEFI on all
> the disks... so can I use a .90v raid1 on the UEFI partition, then
> format it as fat... so that all copies of what ever is in the UEFI
> partition are replicated across the multiple raid1 disks, instead of
> having to remember to copy what ever is in there manually to ach disk?

Interesting idea ... but I get the impression that once you've set up 
the uefi partition and got it working, you shouldn't normally ever need 
to go back to it. This is, I think, one of those cases you need to set 
up a crib sheet and not do anything without it, as you'll forget from 
one time to the next (which is why, I think, you want to use raid :-) 
Personally, I *wouldn't* want to use raid, on the assumption that I'm 
going to screw it up and  don't want a mirror trashing disk2 as I trash 
disk1.

Cheers,
Wol

  reply	other threads:[~2014-10-02  0:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-01 16:33 UEFI and mdadm questions Wilson, Jonathan
2014-10-02  0:17 ` Anthonys Lists [this message]
2014-10-03  5:04 ` Chris Murphy
2014-10-05 18:18   ` Phil Turmel
2014-10-05 20:22     ` Chris Murphy
2014-10-06 15:58       ` Phil Turmel
2014-10-07 22:59         ` Chris Murphy
2014-10-06  8:43   ` Francis Moreau
2014-10-06  6:14 ` Francis Moreau

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=542C99B3.6060809@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=piercing_male@hotmail.com \
    /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.