All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Greaves <david@dgreaves.com>
To: Chris Eddington <chrise@synplicity.com>
Cc: Bill Davidsen <davidsen@tmr.com>, linux-raid@vger.kernel.org
Subject: Re: Raid5 assemble after dual sata port failure
Date: Sun, 18 Nov 2007 12:25:25 +0000	[thread overview]
Message-ID: <47402F35.9020401@dgreaves.com> (raw)
In-Reply-To: <473E8AC2.9020701@synplicity.com>

Chris Eddington wrote:
> Key questions:
> - I assume ddrescue will do a much better job of correcting errors when
> imaging a disk?  My colleague used ghost which is just a copy tool.  I
> don't understand the capabilities of ddrescue on raid partitions that well.
ddrescue should do a *much* better job.
It knows nothing about raid and operates on the underlying device. It retries
bad sectors in a clever manner.


> - fdisk -l reports that all the drives are exactly the same size with
> exactly the same # sectors shown below.  I don't quite follow the
> hpa_resize issue, but it appears the drives don't have hidden HPA
> sectors - I guess?  Note that sdc is the original drive, where sda, sdb,
> and sdd are the imaged drives.
> 
> So what do you recommend to do first?  Should I try xfs_repair on the
> ghost copy,
No
 or just re-copy myself using ddrescue?
Yes.
  Are there special
> settings to ddrescue I should consider to verify/correct potential HPA
> changes?
Ideally just ddrescue the entire device to a file and use loopback.

For the faulty disk then if you have space, make a second copy and xfs_repair
using that. If it fails then you can easily re-image the good disks but it may
not be so easy to re-image the bad one.

David

  reply	other threads:[~2007-11-18 12:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-07 20:28 Raid5 assemble after dual sata port failure Chris Eddington
2007-11-08 10:33 ` David Greaves
2007-11-09 21:23   ` Chris Eddington
2007-11-10  0:28     ` Chris Eddington
2007-11-10  9:16       ` David Greaves
2007-11-10 18:46         ` Chris Eddington
2007-11-11 17:09           ` David Greaves
2007-11-11 17:41             ` Chris Eddington
2007-11-11 22:49               ` David Greaves
2007-11-12  1:01                 ` Bill Davidsen
2007-11-17  6:31                   ` Chris Eddington
2007-11-18 12:25                     ` David Greaves [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-11-07 20:23 chrise

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=47402F35.9020401@dgreaves.com \
    --to=david@dgreaves.com \
    --cc=chrise@synplicity.com \
    --cc=davidsen@tmr.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.