From: Wols Lists <antlists@youngman.org.uk>
To: o1bigtenor <o1bigtenor@gmail.com>,
Adam Goryachev <mailinglists@websitemanagers.com.au>
Cc: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: Questions
Date: Mon, 15 Feb 2016 19:50:56 +0000 [thread overview]
Message-ID: <56C22C20.9090002@youngman.org.uk> (raw)
In-Reply-To: <CAPpdf59u6SPD3=sv1XmKR09jzt6OL8TYLgOj==i3G4775fqbhg@mail.gmail.com>
On 15/02/16 12:12, o1bigtenor wrote:
> I am looking at replacing ALL the drives in the array so that I can
> reduce the likelihood of these kind of issues for a longer period than
> a few months.
>
> Would you be able to tell me what steps should I be taking to replace
> the entire array?
>
> Should I replace the drives one at a time (sort of just like I did
> this time) using the same commands?
If you have a spare SATA (I presume they're sata drives) slot, then
definitely not. It might be worth buying an add-in card to give you an
extra slot, they're only a few quid.
Look up "mdadm --replace". That'll keep the old drive in the array until
the new one has replaced it, keeping the array fully functional all the
time.
Doing --fail, --remove, --add places the array in danger until the
entire sequence is complete, and if you're doing it several times then
you're massively increasing the chances of trouble.
In fact, if you get an add-in card, you might be able to replace several
drives at once - I don't know - read up and see if it's supported (or not).
Cheers,
Wol
next prev parent reply other threads:[~2016-02-15 19:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-14 4:28 Questions o1bigtenor
2016-02-14 6:34 ` Questions Adam Goryachev
2016-02-14 11:53 ` Questions o1bigtenor
2016-02-14 12:24 ` Questions Adam Goryachev
2016-02-15 12:12 ` Questions o1bigtenor
2016-02-15 19:50 ` Wols Lists [this message]
2016-02-15 21:01 ` Questions o1bigtenor
2016-02-15 22:05 ` Questions Adam Goryachev
2016-02-16 11:46 ` Questions o1bigtenor
2016-02-16 14:00 ` Questions Adam Goryachev
2016-02-16 18:33 ` Questions o1bigtenor
2016-02-16 14:32 ` Questions Wols Lists
2016-02-16 18:37 ` Questions o1bigtenor
2016-02-15 22:09 ` Questions Wols Lists
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=56C22C20.9090002@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=mailinglists@websitemanagers.com.au \
--cc=o1bigtenor@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