public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] best practise for 4 disks ... redundancy
Date: Wed, 11 Mar 2015 11:09:29 +0000	[thread overview]
Message-ID: <20150311110929.5fdb4970@digimed.co.uk> (raw)
In-Reply-To: <54FFE4A2.3060008@xunil.at>

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

On Wed, 11 Mar 2015 07:45:54 +0100, Stefan G. Weichinger wrote:

> yesterday I received a shiny new server for a client.
> 
> It brings 4 x 1 TB SATA disks, is capable of UEFI and I started setting
> it up.
> 
> GPT partitioning, small partition(s) for the ESP, some swap, and bigger
> partitions of type fd=raid for creating 2 mdadm-raids (rootfs and data)
> with level 6.
> 
> ok so far.
> 
> Then I spent some hours fiddling with grub2, gummiboot et al to get that
> box booting up fine. dracut doesn't assemble the rootfs-raid etc etc ...
> -> fun

I found this with a LUKS root filesystem, dracut doesn't automatically
detect such devices any more, so speed up the boot. You need to specify
rd.auto or rd.mdraid to force it.

> even if I manage to have it booting via UEFI from /dev/sda1 or so ... I
> still have this single point of failure as the vfat-partitioned ESP is
> on one physical disk only.
> 
> I would like to set it up in a way that it boots even when the /dev/sda
> dies ...

I generally set up boot on a RAID1 across all disks. You can still
access individual disks in a RAID1 array, so you can set your computer
to boot from sda1 then sda2 etc but mount /boot on the array, so all
updates are pushed to all four disks.
 

-- 
Neil Bothwick

I distinctly remember forgetting that.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2015-03-11 11:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-11  6:45 [gentoo-user] best practise for 4 disks ... redundancy Stefan G. Weichinger
2015-03-11 11:09 ` Neil Bothwick [this message]
2015-03-11 15:52   ` Stefan G. Weichinger
2015-03-11 16:06     ` Neil Bothwick
2015-03-11 22:14       ` Stefan G. Weichinger
2015-03-11 22:32         ` Neil Bothwick
2015-03-12 11:30           ` Stefan G. Weichinger
2015-03-12 16:48             ` Neil Bothwick
2015-03-12 17:12               ` Stefan G. Weichinger
2015-03-12 17:28                 ` Neil Bothwick
2015-03-12 18:52                   ` Stefan G. Weichinger
2015-03-13  8:38                     ` Stefan G. Weichinger
2015-03-13  8:59                       ` Neil Bothwick
2015-03-13 13:55                         ` Stefan G. Weichinger
2015-03-13 14:11                           ` Neil Bothwick
2015-03-17 22:00                             ` Stefan G. Weichinger

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=20150311110929.5fdb4970@digimed.co.uk \
    --to=neil@digimed.co.uk \
    --cc=gentoo-user@lists.gentoo.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