From: Lane Brooks <lbrooks@mit.edu>
To: linux-raid@vger.kernel.org
Subject: Multiple Disk Failure Recovery
Date: Sat, 14 Oct 2006 22:29:16 -0400 [thread overview]
Message-ID: <45319CFC.4050708@mit.edu> (raw)
I have a RAID 5 setup with one spare disk. One of the disks failed, so
I replaced it, and while it was recovering, it found some bad sectors on
another drive (unreadable and uncorrectable SMART errors). This
generated a fail event and shut down the array.
When I restart the array with the force command, it starts the recovery
process and dies when it gets to the bad sectors, so I am stuck in an
infinite loop.
I am wondering if there is a way to cut my losses with these bad sectors
and have it recover what it can so that I can get my raid array back to
functioning. Right now I cannot get a spare disk recovery to finish
because these bad sectors. Is there a way to force as much recovery as
possible so that I can replace this newly faulty drive?
Thanks
Lane
next reply other threads:[~2006-10-15 2:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-15 2:29 Lane Brooks [this message]
2006-10-15 6:35 ` Multiple Disk Failure Recovery David Rees
2006-10-15 12:16 ` Roger Gammans
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=45319CFC.4050708@mit.edu \
--to=lbrooks@mit.edu \
--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