linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Stefan /*St0fF*/ Hübner" <stefan.huebner@stud.tu-ilmenau.de>
To: Keith Keller <kkeller@wombat.san-francisco.ca.us>
Cc: linux-raid@vger.kernel.org
Subject: Re: using dd (or dd_rescue) to salvage array
Date: Sat, 04 Feb 2012 19:01:36 +0100	[thread overview]
Message-ID: <4F2D7280.8020500@stud.tu-ilmenau.de> (raw)
In-Reply-To: <0cdtv8xv8f.ln2@goaway.wombat.san-francisco.ca.us>

Am 03.02.2012 17:08, schrieb Keith Keller:
> On 2012-02-01, Keith Keller <kkeller@wombat.san-francisco.ca.us> wrote:
>>
>> Well, for better or worse, this is now a moot question--I had another
>> drive kicked out of the array, I believe prematurely by the controller.
> 
> It turns out to be worse--the drive does in fact appear to be failing,
> which would be the third failure on this RAID6 array.  I had what might
> be a crazy thought--would it be worth the trouble to attempt to use dd
> (or dd_rescue, a tool I found that claims to continue on bad blocks) to
> write the disk image to another disk, and attempt a rebuild with the new
> disk?  Or am I just wasting my time?  (The array is hosting an rsnapshot
> backup set, so I can recreate the latest snapshot, but it'll take a
> while.  So it'd be nice to save the array if it's possible and not time-
> consuming.)
> 
> Thanks for your help!
> 
> --keith
> 
Hi Keith,

actually, ddrescue is THE WAY TO GO in this case.  Don't use the old
ddrescue, but the GNU version.  Some distros call it gddrescue, on
gentoo the old one is called dd-rescue and the gnu-one ddrescue.  Just
check it out: http://www.gnu.org/software/ddrescue/ddrescue.html

Good luck,
Stefan

  reply	other threads:[~2012-02-04 18:01 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-07  1:34 Please Help! RAID5 -> 6 reshapre gone bad Richard Herd
2012-02-07  2:15 ` Phil Turmel
     [not found]   ` <CAOANJV955ZdLexRTjVkQzTMapAaMitq5eqxP0rUvDjjLh4Wgzw@mail.gmail.com>
2012-02-07  2:57     ` Phil Turmel
2012-02-07  3:10       ` Richard Herd
2012-02-07  3:24       ` Keith Keller
2012-02-07  3:38         ` Phil Turmel
2012-01-31  6:31           ` rebuild raid6 after two failures Keith Keller
2012-02-01  4:42             ` Keith Keller
2012-02-01  5:31               ` NeilBrown
2012-02-01  5:48                 ` Keith Keller
2012-02-03 16:08               ` using dd (or dd_rescue) to salvage array Keith Keller
2012-02-04 18:01                 ` Stefan /*St0fF*/ Hübner [this message]
2012-02-05 19:10                   ` Keith Keller
2012-02-06 21:37                     ` Stefan *St0fF* Huebner
2012-02-07  3:44                       ` Keith Keller
2012-02-07  4:24                       ` Keith Keller
2012-02-07 20:01                         ` Stefan *St0fF* Huebner
2012-02-08  7:13         ` Please Help! RAID5 -> 6 reshapre gone bad Stan Hoeppner
2012-02-07  3:04     ` Fwd: " Richard Herd
2012-02-07  2:39 ` NeilBrown
2012-02-07  3:10   ` NeilBrown
2012-02-07  3:19     ` Richard Herd
2012-02-07  3:39       ` NeilBrown
2012-02-07  3:50         ` Richard Herd
2012-02-07  4:25           ` NeilBrown
2012-02-07  5:02             ` Richard Herd
2012-02-07  5:16               ` NeilBrown

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=4F2D7280.8020500@stud.tu-ilmenau.de \
    --to=stefan.huebner@stud.tu-ilmenau.de \
    --cc=kkeller@wombat.san-francisco.ca.us \
    --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).