From: David Brown <david.brown@hesbynett.no>
To: linux-raid@vger.kernel.org
Subject: Re: Raid 5, 2 disk failed
Date: Tue, 25 Jan 2011 00:12:49 +0100 [thread overview]
Message-ID: <ihl11h$psb$1@dough.gmane.org> (raw)
In-Reply-To: <AANLkTi=17u_e24gJMQFQJiCYCUok7-fETW=__HGhJFXg@mail.gmail.com>
On 24/01/11 22:31, Daniel Landstedt wrote:
> Hi, for starters, great work with the linux raid guys.
>
> Now for the unpleasantness's
>
> Please..
> ...help
>
>
> I have a raid 5 with 4 disks and 1 spare.
> 2 disks failed at the same time.
>
I don't know if this will be any help - it certainly won't make you feel
better...
Raid 5 protects against a single disk failure - if a second disk fails,
you've lost your data. If the disk(s) haven't really failed, but have
only had temporary problems, then you might be able to put them together
again, with a lot of work. Standard disk recovery techniques should be
used - boot from a live CD like system recovery cd, use dd_rescue to
make the best possible raw copies of your original 4 disks (including
the bad ones). Then make copies of /those/ copies, so that if you mess
up you can make new copies without having to re-read the dodgy disks.
If the "failed" disks were actually mostly okay, you should be able to
put the raid5 array together again and get most of the data out.
For future use, consider raid6 rather than raid5, or perhaps raid10
(which is less efficient at disk space, but faster for some use and a
lot faster at recovery). There isn't any good reason for using raid5
with a spare rather than raid6, unless you have an ancient processor.
next prev parent reply other threads:[~2011-01-24 23:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 21:31 Raid 5, 2 disk failed Daniel Landstedt
2011-01-24 23:12 ` David Brown [this message]
2011-01-25 0:30 ` Neil 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='ihl11h$psb$1@dough.gmane.org' \
--to=david.brown@hesbynett.no \
--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).