From: Bryan Wintermute <bryanwintermute@gmail.com>
To: linux-raid@vger.kernel.org
Subject: RAID 5 - One drive dropped while replacing another
Date: Tue, 1 Feb 2011 15:27:50 -0800 [thread overview]
Message-ID: <AANLkTikSjLhoUM5f2ibqCUmo8XF-tsrhxZ7oieg08dtD@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinXTYds442gPrs9a9vKtWTo4OcDHDEzvO0njvyv@mail.gmail.com>
Hi,
I have a RAID5 setup with 15 drives. One drive died, so I purchased a
replacement and added it to the array. During this process, however,
another drive dropped. Upon further inspection, the second failed
drive has some bad sectors that appears to be keeping mdadm from
completing the recovery. If I remove the replacement drive, thus
keeping mdadm from recovering, the array functions and most of the
data is intact (save for the occasional missing files and folders).
Mdadm is able to recover for about 30 seconds to 1 minute before it
drops the drive and quits the recovery. Is there anything I can do to
get around these bad sectors or force mdadm to ignore them to at least
complete the recovery? I don't care about losing some of the data, but
it'd be nice to not lose all of it.
I'm running Ubuntu 10.04 LTS x64 with mdadm - v2.6.7.1 - 15th October 2008
Please let me know if you need any more information.
Thank you for your time and any help,
Bryan
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next parent reply other threads:[~2011-02-01 23:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTinXTYds442gPrs9a9vKtWTo4OcDHDEzvO0njvyv@mail.gmail.com>
2011-02-01 23:27 ` Bryan Wintermute [this message]
2011-02-01 23:36 ` RAID 5 - One drive dropped while replacing another Roman Mamedov
2011-02-02 6:20 ` Leslie Rhorer
2011-02-02 14:21 ` hansbkk
2011-02-02 14:28 ` Roman Mamedov
2011-02-02 15:28 ` hansbkk
[not found] ` <AANLkTikm5unULgkUBM__d8N9XPReu9BtjijAHt9zzvaP@mail.gmail.com>
2011-02-02 16:29 ` hansbkk
2011-02-02 21:15 ` David Brown
2011-02-02 17:25 ` Leslie Rhorer
2011-02-02 17:51 ` hansbkk
2011-02-02 20:56 ` Leslie Rhorer
2011-02-02 14:29 ` Mathias Burén
2011-02-02 14:47 ` Robin Hill
2011-02-02 16:24 ` David Brown
2011-02-02 16:48 ` hansbkk
2011-02-02 21:22 ` David Brown
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=AANLkTikSjLhoUM5f2ibqCUmo8XF-tsrhxZ7oieg08dtD@mail.gmail.com \
--to=bryanwintermute@gmail.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).