From: David Greaves <david@dgreaves.com>
To: Carlos Carvalho <carlos@fisica.ufpr.br>
Cc: linux-raid@vger.kernel.org, tbostrom@writemem.com
Subject: Re: Problem with 5disk RAID5 array - two drives lost
Date: Sat, 22 Apr 2006 20:54:05 +0100 [thread overview]
Message-ID: <444A89DD.2000803@dgreaves.com> (raw)
In-Reply-To: <17482.34615.908339.197028@fisica.ufpr.br>
Carlos Carvalho wrote:
> Molle Bestefich (molle.bestefich@gmail.com) wrote on 22 April 2006 05:54:
> >Tim Bostrom wrote:
> >> raid5: Disk failure on hdf1, disabling device.
> >
> >MD doesn't like to find errors when it's rebuilding.
> >It will kick that disk off the array, which will cause MD to return
> >crap (instead of stopping the array and removing the device - I
> >wonder), again causing 'mount' etc. to fail.
> >
> >Quite unfortunate for you, since you have absolutely no redundancy
> >with 4/5 drives, and you really can't afford to have the 4th disk
> >kicked just because there's a bad block on it.
>
> Yes...
>
> As Molle says, you have a chance that it's a driver/cable problem.
> What you can also do is dd the disk to another one and try to rebuild
> the array with the new disk so that you won't get errors during the
> reconstruction. If you get errors during the copy you'll have to
> decide what to do with the bad blocks. Some people prefer to use
> ddrescue instead of dd; I've never tried it.
I've used ddrescue and would *highly* recommend it. Use the GNU version,
not the other one (dd_rescue?)
It handles errors very well indeed and has a good display to show what's
happening.
It seems faster than dd (possibly threaded so streams both drives rather
than read a drive, write a drive)
David
next prev parent reply other threads:[~2006-04-22 19:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-19 19:39 Problem with 5disk RAID5 array - two drives lost Tim Bostrom
2006-04-22 3:54 ` Molle Bestefich
2006-04-22 19:42 ` Carlos Carvalho
2006-04-22 19:52 ` Molle Bestefich
2006-04-22 19:54 ` David Greaves [this message]
2006-04-24 0:17 ` Tim Bostrom
2006-04-24 2:00 ` Arthur Britto
2006-04-24 14:01 ` David Greaves
2006-04-25 14:55 ` Tim Bostrom
2006-04-26 6:19 ` Tim Bostrom
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=444A89DD.2000803@dgreaves.com \
--to=david@dgreaves.com \
--cc=carlos@fisica.ufpr.br \
--cc=linux-raid@vger.kernel.org \
--cc=tbostrom@writemem.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;
as well as URLs for NNTP newsgroup(s).