linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Robinson <john.robinson@anonymous.org.uk>
To: Ronny Adsetts <ronny.adsetts@amazinginternet.com>
Cc: Linux RAID ML <linux-raid@vger.kernel.org>
Subject: Re: RAID mirror, resyncing from bad disk
Date: Mon, 14 Sep 2009 10:23:15 +0100	[thread overview]
Message-ID: <4AAE0B83.8040009@anonymous.org.uk> (raw)
In-Reply-To: <4AAE0930.1030204@amazinginternet.com>

On 14/09/2009 10:13, Ronny Adsetts wrote:
> John Robinson said at 13/09/2009 21:24:
>> On 13/09/2009 20:19, Ronny Adsetts wrote:
>> [...]
>>> The problematic array is /dev/md2 and the dying disk is /dev/sdc.
>>>
>>> When I try to resync it gets to about 99.2% then gives load of I/O
>>> errors in /var/log/kern.log and finally gives up and restarts the sync.
>>>
>>> Ideally I just want to tell the system to ignore the bad sector and
>>> just resync the array.
>>>
>>> Does anyone have any ideas on how I can get this resolved short of
>>> reinstalling?
>> You need to ddrescue the contents of the dying drive onto a good one,
>> then replace the dying drive with the fresh one. This will require
>> taking the array down but you won't have to reinstall, unless you've
>> lost something important in the lost sectors on the dying drive.
> 
> The bad sector is thankfully right at the end of the disk in an unallocated part of the LVM setup.
> 
> So, do I ddrescue the entire disk? I assume this will copy everything including the partition table and other gubbins?

Yes you do, and yes it will. You don't have to use ddrescue, there are 
other tools - for examples see 
http://www.forensicswiki.org/wiki/Ddrescue - but ddrescue would be my 
choice.

> Thanks very much, this looks like a winner to me. :-).

Good luck with it!

Cheers,

John.

      reply	other threads:[~2009-09-14  9:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-13 19:19 RAID mirror, resyncing from bad disk Ronny Adsetts
2009-09-13 20:24 ` John Robinson
2009-09-13 22:49   ` Majed B.
2009-09-14  9:00     ` Ronny Adsetts
2009-09-14  9:13   ` Ronny Adsetts
2009-09-14  9:23     ` John Robinson [this message]

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=4AAE0B83.8040009@anonymous.org.uk \
    --to=john.robinson@anonymous.org.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=ronny.adsetts@amazinginternet.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).