From: Anthony Youngman <antlists@youngman.org.uk>
To: linuxknight <linuxknight@gmail.com>,
"David C. Rankin" <drankinatty@suddenlinkmail.com>
Cc: mdraid <linux-raid@vger.kernel.org>
Subject: Re: Linux software raid troubles
Date: Fri, 14 Apr 2017 20:23:22 +0100 [thread overview]
Message-ID: <d8bf2e60-fd1f-1fe3-0744-0e9029ec5b69@youngman.org.uk> (raw)
In-Reply-To: <CAAO=44YCU+OF-xBytuMCHEtV7WbHE6EVyJ_9ncGmM9VNWcj9MA@mail.gmail.com>
On 14/04/17 16:01, linuxknight wrote:
> One last question, is it acceptable to let graphical installers setup
> the software raid for me or should I use one disk and create a raid
> mirror later once the OS is setup?
Can't give you any advice on how to do it, but I'd be inclined to create
one huge array using all your disks. For each physical disk, one
partition for UEFI or grub, possibly a second partition for a mirrored
root partition, then all the rest for a raid array with LVM on top.
I'm hoping to build a new system set up like that, but that's probably a
few months down the line.
Oh - and using the installer to set it up is probably going to be a
nightmare. My experience is gentoo, which expects me to set it up
manually, or SuSE which was a pain setting up custom partitioning.
Cheers,
Wol
next prev parent reply other threads:[~2017-04-14 19:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-12 14:31 Linux software raid troubles linuxknight
2017-04-12 14:45 ` Reindl Harald
[not found] ` <CAAO=44bsG1yrmYbag1eruNA_tdXxqiJptnRyPB=4TW6r5771HQ@mail.gmail.com>
2017-04-12 15:29 ` Reindl Harald
2017-04-12 15:36 ` linuxknight
2017-04-12 16:11 ` Reindl Harald
2017-04-14 4:43 ` David C. Rankin
2017-04-14 15:01 ` linuxknight
2017-04-14 15:52 ` Reindl Harald
2017-04-14 19:23 ` Anthony Youngman [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-04-12 14:06 linuxknight
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=d8bf2e60-fd1f-1fe3-0744-0e9029ec5b69@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=drankinatty@suddenlinkmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=linuxknight@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox