From: Johannes Truschnigg <johannes@truschnigg.info>
To: "Mathias Burén" <mathias.buren@gmail.com>
Cc: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: Do I have a bad HDD?
Date: Sun, 31 Jul 2011 20:25:42 +0200 [thread overview]
Message-ID: <4E359E26.2080500@truschnigg.info> (raw)
In-Reply-To: <CADNH=7F3CVZ6r56jFrSHoVyzOZTHCfXPE_j-Rn8powbB6BLBYQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1859 bytes --]
Hi Mathias,
PLEASE don't always quote everything you've just written a few minutes
ago when replying to yourself. This makes these responses really, really
inconvenient to read.
Concerning your problem at hand: Don't panic, everything should be fine.
Your RAID did what it is supposed to do: protect your from a single
drive failure without inducing downtime. A disk has failed, and now it's
time to replace it, that's nothing out of the ordinary. You don't need
to shut down your system - RAID systems have "no service interruption in
case of an accident" as a design goal, and md is rather good at meeting
just that.
If your SATA controller supports hotplug (and if it's SATA-300, that
much is for certain), just unplug the old drive, replace it with a new
one, clone your partition table setup (if any) from an old driver to the
new one, have md pick up the disk and integrate it into your array, and
see how everything'll be taken care of automatically. md will resync the
array once the new disk is part of the array, and it will be smooth
sailing again afterwards. Just make sure you don't pull out the wrong
drive, but correctly identify the broken one. ;)
While the array's being worked on, you can do whatever you intended to
do with your seemingly healthy array from of a few hours ago - the only
difference it that (some) things will go slower, but that's about it.
The only serious problem you could run into is a second and third
harddrive failing while your array isn't 100% OK again yet - but even in
that case, you'd have a backup ready, now wouldn't you? :)
--
with best regards:
- Johannes Truschnigg ( johannes@truschnigg.info )
www: http://johannes.truschnigg.info/
phone: +43 650 2 133337
xmpp: johannes@truschnigg.info
Please do not bother me with HTML-eMail or attachments. Thank you.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2011-07-31 18:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-31 13:05 Do I have a bad HDD? Mathias Burén
2011-07-31 17:59 ` Mathias Burén
2011-07-31 18:05 ` Mathias Burén
2011-07-31 18:14 ` Mathias Burén
2011-07-31 18:25 ` Johannes Truschnigg [this message]
2011-07-31 18:31 ` Mathias Burén
2011-07-31 23:42 ` Phil Turmel
2011-07-31 23:56 ` Mathias Burén
2011-08-22 17:10 ` Mathias Burén
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=4E359E26.2080500@truschnigg.info \
--to=johannes@truschnigg.info \
--cc=linux-raid@vger.kernel.org \
--cc=mathias.buren@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