linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Leach <jason.leach@gmail.com>
To: linux-raid@vger.kernel.org
Subject: Re: 3ware raid question
Date: Tue, 2 Aug 2005 13:27:22 -0700	[thread overview]
Message-ID: <602f2f2b05080213272aec2685@mail.gmail.com> (raw)
In-Reply-To: <3800555526607650241@unknownmsgid>

Raz:
 
 The 3ware (at least my 9500S-8) keeps the info about the disk and how
it fits into the RAID array on the disk;  I think in the DCB is used
for this.  You can (and I have) unplug the disks, then connect them to
different ports and the array will still work fine.
 
 When you are adding a disk from a different array it probably has the
DCB from that array.  This is conflicting with your new array. I would
do as the Dan suggests, and clear the disk.
 
 Jason.

On 8/2/05, Dan Stromberg <strombrg@dcs.nac.uci.edu> wrote: On Tue,
2005-08-02 at 13:52 +0300, Raz Ben-Jehuda(caro) wrote:

> i have encountered a weired feature of 3ware raid.
> When i try to put inside an existing raid a disk which
> belonged to a different 3ware raid if fail. 
> Any idea anyone ?

Two thoughts:

1) Maybe test the disk in another machine and see if it's still good

2) Maybe wipe the disk clean in another machine with something like:

        dd if=/dev/zero of=/dev/sdb 

...but be very careful to get the right disk (IE, you may not
need /dev/sdb, you might need /dev/hdd or a number of other
possibilities).

       reply	other threads:[~2005-08-02 20:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3800555526607650241@unknownmsgid>
2005-08-02 20:27 ` Jason Leach [this message]
2005-08-03  6:50   ` 3ware raid question Raz Ben Jehuda
2005-08-02 10:52 Raz Ben-Jehuda(caro)
2005-08-02 19:10 ` Dan Stromberg
2005-08-03 14:26 ` Mike Dresser
2005-08-03 14:39   ` Raz Ben Jehuda
2005-08-03 15:50     ` Mike Dresser

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=602f2f2b05080213272aec2685@mail.gmail.com \
    --to=jason.leach@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 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).