linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Francis Moreau <francis.moro@gmail.com>
To: David Brown <david.brown@hesbynett.no>,
	Phil Turmel <philip@turmel.org>,
	Chris Murphy <lists@colorremedies.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Soft RAID and EFI systems
Date: Tue, 04 Feb 2014 09:53:09 +0100	[thread overview]
Message-ID: <52F0AA75.2030006@gmail.com> (raw)
In-Reply-To: <52F0A976.9080306@hesbynett.no>

On 02/04/2014 09:48 AM, David Brown wrote:
> On 04/02/14 09:41, Francis Moreau wrote:
>> On 02/02/2014 11:57 PM, Phil Turmel wrote:
>>> On 02/02/2014 05:30 PM, Chris Murphy wrote:
>>>>
>>>> On Feb 2, 2014, at 2:34 PM, Francis Moreau <francis.moro@gmail.com>
>>>> wrote:
>>>>>
>>>>> That's funny because one of the reasons I want to use UEFI firmware
>>>>> is to get rid of grub (I don't like it and the way it has become
>>>>> such a bloated beast): since /boot is vfat and has its own
>>>>> partition, I prefer use a much simpler bootloader such as
>>>>> gummyboot.
>>>
>>> Ditching the bootloader is possible:
>>>
>>> http://kroah.com/log/blog/2013/09/02/booting-a-self-signed-linux-kernel/
>>>
>>
>> Well yeah it's possible but not currently usable IMHO. It means that you
>> need to build your own kernel, include in this kernel the initramfs
>> image and you need to redo the whole process if you want to change a
>> single option in the kernel command line.
>>
>>> It seems to me that you should be able to create a raid1 v1.0 MD array
>>> of your EFI support partitions, and put the combined and signed
>>> kernel/initramfs onto it (mirrored to all member drives).
>>
>> Are both v0.9 and v1.0 MD  put their metadata at the end of a partition
>> ? I thought only v0.9 would do that.
> 
> Yes, it is only 0.9 format that is at the end of the partition.  This
> means that a plain raid1 mirror (with as many disks as you like, as long
> as they are simple mirrors and not raid10) looks just like a normal
> partition for other tools.  As long as it is read-only, tools that are
> not raid-aware can use it.  For example, grub and lilo can happily boot
> from a 0.9 metadata raid1 array just like from a normal partition.
> (Actually, modern grub understands a lot of md raid formats.)  The same
> thing should apply to EFI, as long as it does not attempt to write to
> the partition.
> 

hmm I need to check if EFI specifies that the ESP is never written by
the firmware. If not it might be risky to rely on it.


  reply	other threads:[~2014-02-04  8:53 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-31 17:02 Soft RAID and EFI systems Francis Moreau
2014-02-01 22:04 ` Martin Wilck
2014-02-02 21:39   ` Francis Moreau
2014-02-02 21:56     ` Martin Wilck
2014-02-02 20:39 ` Chris Murphy
2014-02-02 21:34   ` Francis Moreau
2014-02-02 22:30     ` Chris Murphy
2014-02-02 22:57       ` Phil Turmel
2014-02-03  7:19         ` Martin Wilck
2014-02-04  8:41         ` Francis Moreau
2014-02-04  8:48           ` David Brown
2014-02-04  8:53             ` Francis Moreau [this message]
2014-02-04 12:27             ` Phil Turmel
2014-02-04 15:13             ` Chris Murphy
2014-02-04 15:29               ` Chris Murphy
2014-02-07  7:42               ` Francis Moreau
2014-02-04  8:32       ` Francis Moreau
2014-02-04  8:57         ` David Brown
2014-02-04  9:06           ` Francis Moreau
2014-02-04  9:35             ` David Brown
2014-02-04  9:45               ` Francis Moreau
2014-02-04 15:27             ` Chris Murphy
2014-02-04 15:40           ` Chris Murphy
2014-02-04 14:50         ` Chris Murphy
2014-02-07  8:00           ` Francis Moreau
2014-02-03  9:56 ` David Brown
2014-02-04  8:22   ` 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=52F0AA75.2030006@gmail.com \
    --to=francis.moro@gmail.com \
    --cc=david.brown@hesbynett.no \
    --cc=linux-raid@vger.kernel.org \
    --cc=lists@colorremedies.com \
    --cc=philip@turmel.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).