From: Ben Nemec <lists@nemebean.com>
To: linux-raid@vger.kernel.org
Subject: Replacing a drive in RAID 0
Date: Mon, 02 Aug 2010 17:18:11 -0500 [thread overview]
Message-ID: <1c7fae50481e2f053798107bf2ad2737@localhost> (raw)
Hi,
I have a disk in a RAID 0 array that SMART tells me is dying, but hasn't
died yet. I have a warranty replacement on the way, and I'm wondering if
there's any way to copy the data off the dying drive to the new drive and
swap the RAID array to use the new one (assuming the old one lasts long
enough to do that, of course). Can I just dd the entire drive over and
replace the bad drive? Can the md tools do it somehow? Maybe it's
impossible? Obviously nothing on this array is irreplaceable, but it would
save me some hassle reinstalling things if I could save it.
Thanks.
-Ben
next reply other threads:[~2010-08-02 22:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 22:18 Ben Nemec [this message]
2010-08-03 5:22 ` Replacing a drive in RAID 0 Mikael Abrahamsson
2010-08-03 6:14 ` Neil Brown
2010-08-03 7:46 ` Roman Mamedov
2010-08-03 8:29 ` Neil Brown
2010-08-03 15:28 ` Ben Nemec
2010-08-05 6:59 ` Leslie Rhorer
2010-08-05 14:51 ` Ben Nemec
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=1c7fae50481e2f053798107bf2ad2737@localhost \
--to=lists@nemebean.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).