From: Phil Turmel <philip@turmel.org>
To: Chris Murphy <lists@colorremedies.com>,
Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: UEFI and mdadm questions.
Date: Sun, 05 Oct 2014 14:18:46 -0400 [thread overview]
Message-ID: <54318B86.7060506@turmel.org> (raw)
In-Reply-To: <E82F134B-634B-46B9-A835-846CA89728FB@colorremedies.com>
On 10/03/2014 01:04 AM, Chris Murphy wrote:
>
> On Oct 1, 2014, at 12:33 PM, "Wilson, Jonathan"
> <piercing_male@hotmail.com> wrote:
>
>> From what I can tell with UEFI I need to set up a UEFI partition
>> with a FAT format.
>
> It's a particular kind of FAT, that's defined as EFI FAT, the idea
> being that if the originating FAT ever changes, EFI FAT won't.
>
>>
>> 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.
>
> BIOSboot applies to GPT disks on BIOS computers, not MBR. On MBR
> disks, the GRUB stage1 code jumps to stage2 code in the MBR gap which
> is the region between the MBR and the first partition's starting
> LBA.
>
>>
>> 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.
>
> No. An OSLoader is required, it's an EFI application. Its job is to
> load a kernel and initramfs. The kernel and initramfs could be on the
> ESP (EFI System partition) but this is fraught with limitations. The
> expectation is that the kernel and initramfs are on some other
> partition of the same disk. Of course if you're using GRUB it doesn't
> care and will find a kernel/initramfs off another disk also, or even
> off md raid.
An option to consider is to compile a kernel using the EFI stub option,
a pre-set command line, and an embedded initramfs. Then the kernel can
boot directly from the EFI FAT partition with *no bootloader*. The
embedded initramfs can support any raid/lvm/partitioning scheme
what-so-ever.
http://kroah.com/log/blog/2013/09/02/booting-a-self-signed-linux-kernel/
The cryptography is optional if you just want to boot really fast.
If your BIOS can be configured to try multiple boot images, it should be
possible to have true raid fallback without using motherboard or
hardware raid. (Set up md raid1 with metadata v1.0 of multiple copies
of the EFI FAT partition.) I've been meaning to try this....
Phil
next prev parent reply other threads:[~2014-10-05 18:18 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
2014-10-03 5:04 ` Chris Murphy
2014-10-05 18:18 ` Phil Turmel [this message]
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=54318B86.7060506@turmel.org \
--to=philip@turmel.org \
--cc=linux-raid@vger.kernel.org \
--cc=lists@colorremedies.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.