All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Nelson <freeandy@gmail.com>
To: linux-raid@vger.kernel.org
Subject: Re: will mdadm work with a raid created using raidtools
Date: Thu, 16 Feb 2006 12:23:54 -0600	[thread overview]
Message-ID: <dt2fvr$sea$1@sea.gmane.org> (raw)
In-Reply-To: <20060216174727.GH8762@intoxicatedmind.net>

Frank Blendinger wrote:
> On Thu, Feb 16, 2006 at 11:31:06AM -0600, Andrew Nelson wrote:
> 
>>>It's probably not your fault - blame /dev/hde! This sounds like a bad
>>>error on the disk - you should really get a new one, and try to copy
>>>/dev/hde to the new disk (with dd_rescue for example). This _might_ save
>>>the data.
>>>
>>>Then you can try to create the array with the new disk and hope that
>>>it will work.
>>
>>
>>I thought the whole idea of a raid 1 was that if one drive went bad I could just
>>plug a new drive in and the raid would rebuild without problems.
> 
> 
> That is certainly right. I just wanted to tell you, that your /dev/hde
> probably has a serious hardware error, and that you should replace it!
> 
> Of course you can just throw it out, put in a new drive, rebuild the
> array with your other drive and the new one, and then resync. This
> should work just fine.
> 
> I guess my first answer was quite confusing, sorry. It's absolutely not
> necessary to copy the old hde with dd_rescue.
> 
> 
> Greetings,
> Frank

Is it possible to assemble the array with just /dev/hdg?  I swear I saw an
option somewhere that allowed just such a thing but now I can't find it anywhere.

//andy




  reply	other threads:[~2006-02-16 18:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-15 19:07 will mdadm work with a raid created using raidtools Andrew Nelson
2006-02-15 22:50 ` Neil Brown
2006-02-16 15:15   ` Andrew Nelson
2006-02-16 17:14     ` Frank Blendinger
2006-02-16 17:31       ` Andrew Nelson
2006-02-16 17:47         ` Frank Blendinger
2006-02-16 18:23           ` Andrew Nelson [this message]
2006-02-16 19:37             ` Andrew Nelson

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='dt2fvr$sea$1@sea.gmane.org' \
    --to=freeandy@gmail.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.