linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.net>
To: Phil Turmel <philip@turmel.org>
Cc: Rudy Zijlstra <rudy@grumpydevil.homelinux.org>,
	Another Sillyname <anothersname@googlemail.com>,
	linux-raid@vger.kernel.org
Subject: Re: Installing Linux directly onto RAID6 Array...........
Date: Tue, 12 May 2015 17:31:47 +0500	[thread overview]
Message-ID: <20150512173147.0d2c3363@natsu> (raw)
In-Reply-To: <5551F01A.4050705@turmel.org>

[-- Attachment #1: Type: text/plain, Size: 551 bytes --]

On Tue, 12 May 2015 08:20:42 -0400
Phil Turmel <philip@turmel.org> wrote:

> > Doing something like that... and using network boot to solve those issues
> > 
> > Last i tried grub2 could not handle a raid6 directly (could be changed now)
> 
> You could also boot from a USB device, possibly one that memory caches
> its root filesystem (like System Rescue CD).

Just place GRUB and the /boot partition with kernel and initrd on a USB stick,
the rest (root FS) can be on RAID6. That's what I do on one machine.

-- 
With respect,
Roman

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2015-05-12 12:31 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-12 10:08 Installing Linux directly onto RAID6 Array Another Sillyname
2015-05-12 10:20 ` Rudy Zijlstra
2015-05-12 12:20   ` Phil Turmel
2015-05-12 12:31     ` Roman Mamedov [this message]
     [not found]       ` <CAOS+5GHhUoYxTTYOWU7cdN6GSdffSMGrhWHU5ZtWEjc4jEm3eg@mail.gmail.com>
2015-05-12 13:12         ` Fwd: " Another Sillyname
2015-05-12 13:42           ` Roman Mamedov
2015-05-12 13:27 ` Wilson, Jonathan
2015-05-12 14:05   ` Another Sillyname
2015-05-13  0:02 ` Adam Goryachev
     [not found]   ` <CAOS+5GEP6+7OAHkqQjeyGHAB5u-_-Vq2JWGpcOemYHdCjmR5Lg@mail.gmail.com>
2015-05-24  1:18     ` Fwd: " Another Sillyname
2015-05-24  8:36       ` Mikael Abrahamsson
2015-05-24  9:08         ` Another Sillyname
2015-05-24  9:46           ` Mikael Abrahamsson
2015-05-24 10:07             ` Another Sillyname
2015-05-24 10:35               ` Mikael Abrahamsson
2015-05-24 10:42                 ` Another Sillyname
2015-05-26  8:29           ` NeilBrown
2015-05-26 13:18             ` Another Sillyname
2015-05-24 11:12         ` Fwd: " Wols Lists
2015-05-24 11:57           ` Brad Campbell
2015-05-24 12:41             ` Wols Lists
2015-05-24 13:48               ` Brad Campbell
2015-05-24 14:06               ` Mikael Abrahamsson
2015-05-24 14:53                 ` Wols Lists
2015-05-24 14:57                   ` Mikael Abrahamsson
2015-05-25 21:03                     ` Another Sillyname
2015-05-25 23:20                       ` Wols Lists
2015-05-26  7:08                         ` Another Sillyname
2015-05-26  8:06                           ` Mikael Abrahamsson
2015-05-26 11:18                             ` Another Sillyname
2015-05-26 14:08                               ` Mikael Abrahamsson
2015-05-26 20:11                                 ` Wols Lists
2015-05-26 21:02                                   ` Another Sillyname
2015-05-27  4:59                                   ` Mikael Abrahamsson

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=20150512173147.0d2c3363@natsu \
    --to=rm@romanrm.net \
    --cc=anothersname@googlemail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=philip@turmel.org \
    --cc=rudy@grumpydevil.homelinux.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).