3ware raid question

3ware raid question

[Raz Ben-Jehuda(caro)]

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 ? 
-- 
Raz
Long Live the Penguin

Re: 3ware raid question

[Dan Stromberg]

[-- Attachment #1: Type: text/plain, Size: 584 bytes --]

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).


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: 3ware raid question

[Mike Dresser]

On Tue, 2 Aug 2005, 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 ?

It's a feature on the 9500S's.  You have to unlock the drive to be able to 
use it in another machine.  Protects you from accidentally wiping out a 
raid volume disk.

Mike

Re: 3ware raid question

[Raz Ben Jehuda]

"unlock the drive" ?

On Wed, 2005-08-03 at 10:26 -0400, Mike Dresser wrote:
> On Tue, 2 Aug 2005, 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 ?
> 
> It's a feature on the 9500S's.  You have to unlock the drive to be able to 
> use it in another machine.  Protects you from accidentally wiping out a 
> raid volume disk.
> 
> Mike
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
-- 
Raz
Long live the penguin

Re: 3ware raid question

[Mike Dresser]

On Wed, 3 Aug 2005, Raz Ben Jehuda wrote:

> "unlock the drive" ?

http://www.3ware.com/KB/article.aspx?id=13502&cNode=8Q3U2U

Re: 3ware raid question

[Jason Leach]

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).

Re: 3ware raid question

[Raz Ben Jehuda]

I know that some raid management information is save on the disks.
But I am using 250 GB disks at minimum dd'ing this amount
would be too long. Has know the exact position of where to
dd ?
On Tue, 2005-08-02 at 13:27 -0700, Jason Leach wrote:
> 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).
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
-- 
Raz
Long live the penguin