All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Youngman <antmbox@youngman.org.uk>
To: Alex Elder <elder@ieee.or>,
	Anthony Youngman <antlists@youngman.org.uk>,
	linux-raid@vger.kernel.org
Subject: Re: ***UNCHECKED*** Re: 3-disk RAID5 won't assemble
Date: Sat, 21 Oct 2017 10:36:05 +0100	[thread overview]
Message-ID: <68dd7a9a-228b-ecc9-dbf9-3c3cb0f251bd@youngman.org.uk> (raw)
In-Reply-To: <7db1f2fc-3018-5a0a-89a1-74d6762df463@ieee.org>

On 21/10/17 04:40, Alex Elder wrote:
> You guys are really great.  I am back running again.  Thank you
> for taking the time to help me out.  It saved me a LOT of time
> trying to chase down what I needed to do, and most importantly
> you gave me the confidence to proceed with only a modest level
> of anxiety...  The hardest thing was creating a new systemd
> service to run the script at boot time (also a first for me).
> 
>> Buy NAS drives in the future, though.

> Hey, they were never going to fail!  RAID solves all problems.

Even the alleged experts (definitely "alleged" in my case :-) don't 
always do the right thing :-) I'm currently running two Seagate 
Barracudas - *without* the timeout script! - in a mirror configuration. 
But over the next few days I'll be building a new pc and I've got two 
raid-capable drives. It'll be a big learning experience because I use 
gentoo ... learning systemd, learning QEMU, learning KVM, learning...
> 
> But yeah, I'll look more closely at that next time.
> 
Cheers,
Wol

      reply	other threads:[~2017-10-21  9:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-20 19:51 3-disk RAID5 won't assemble Alex Elder
2017-10-20 20:34 ` Wols Lists
2017-10-20 22:46   ` Alex Elder
2017-10-20 23:37     ` ***UNCHECKED*** " Anthony Youngman
2017-10-20 23:49       ` Phil Turmel
2017-10-21  3:40         ` Alex Elder
2017-10-21  9:36           ` Anthony Youngman [this message]

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=68dd7a9a-228b-ecc9-dbf9-3c3cb0f251bd@youngman.org.uk \
    --to=antmbox@youngman.org.uk \
    --cc=antlists@youngman.org.uk \
    --cc=elder@ieee.or \
    --cc=linux-raid@vger.kernel.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 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.