AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20090126175104.399d4185@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:exch1.onstor.net
NSV:
SSH:
R:<brian.stark@onstor.com>,<narayan.venkat@onstor.com>,<dl-Leopard@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@exch1.onstor.net/INBOX	0	2779531E7C760D4491C96305019FEEB51851D40E4D@exch1.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Mon, 26 Jan 2009 17:51:26 -0800
From: Andrew Sharp <andy.sharp@onstor.com>
To: Brian Stark <brian.stark@onstor.com>
Cc: Narayan Venkat <narayan.venkat@onstor.com>, dl-Leopard
 <dl-Leopard@onstor.com>
Subject: Re: Fujitsu JBOD update
Message-ID: <20090126175126.4fc65964@ripper.onstor.net>
In-Reply-To: <2779531E7C760D4491C96305019FEEB51851D40E4D@exch1.onstor.net>
References: <2779531E7C760D4491C96305019FEEB51851D40D6C@exch1.onstor.net>
	<2779531E7C760D4491C96305019FEEB51851D40E4D@exch1.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Mon, 26 Jan 2009 13:43:43 -0800 Brian Stark <brian.stark@onstor.com>
wrote:

> We moved 12 drives from the LSI JBOD into the Fujitsu JBOD and all 12
> drives were recognized with OpenSolaris and Nexenta.
> 
> I also just heard from Fujitsu that the drives in the Fujitsu JBOD
> are password protected and that's why they are not working for us.
> Our local contact found out about this over the weekend from Fujitsu
> Japan and was surprised to hear about it.  Also, Japan did not supply
> the password that is needed, although it's not clear how or where we
> would enter that password.

I believe it's just a protocol handshake at initialization time that
they added (Seagate added for them) so the drives will only work in a
Fujitsu environment. Not completely unheard of in the disk drive
world.  Since it's a JBOD and not in an otherwise Fujitsu environment,
I don't believe there is any way for us to "un-protect" them.  Fujitsu
will have to do it, or just send us a JBOD that's meant to work in a
heterogeneous environment.

> 
> Brian
> 
> 
> ________________________________
> From: Brian Stark
> Sent: Monday, January 26, 2009 10:11 AM
> To: Narayan Venkat; dl-Leopard
> Subject: RE: Fujitsu JBOD update
> 
> Some more news...
> 
> We noticed that the Fujitsu JBOD uses Seagate Barracuda ES drives,
> which we have in some LSI JBODs.  The only difference is the capacity
> - 500GB on Fujitsu and 750GB on LSI.  We swapped the drives between
> carriers, and we were able to see the 750GB drive from the LSI JBOD
> in the Fujitsu JBOD.  Note that the drive from the LSI JBOD had never
> been used in a Leopard system and was being tested as part of Cougar
> and Bobcat quals.  We're now going to move more of the drives from
> the LSI JBOD and run some additional tests.
> 
> This suggests the problem we're having with the Fujitsu JBOD is with
> the drives, not the JBOD.  I've asked Fujitsu for more information on
> this, but I think it likely indicates that it has something to do
> with the formatting of the drives in the Fujitsu JBOD.
> 
> 
> Brian
> 
> 
> ________________________________
> From: Narayan Venkat
> Sent: Friday, January 23, 2009 4:54 PM
> To: Brian Stark; dl-Leopard
> Subject: Re: Fujitsu JBOD update
> 
> 
> Thanks Brian. This is very helpful.
> 
> Narayan Venkat
> Tel: (408) 963-2404
> Cell: (408) 221-4297
> --------------------------
> Sent from my BlackBerry Wireless Handheld
> 
> ________________________________
> From: Brian Stark
> To: dl-Leopard
> Sent: Fri Jan 23 14:46:04 2009
> Subject: Fujitsu JBOD update
> Pat, John, and I ran an experiment today where we connected the
> Fujitsu JBOD to an OpenSolaris server.  As with Leopard, OpenSolaris
> does *not* recognize any of the Fujitsu disks.  We repeated the same
> experiment with the LSI JBOD, and the 12 drives were immediately
> seen.  This indicates that the problem with connecting Leopard to
> Fujitsu is on the Fujitsu side.
> 
> I'm in touch with Fujitsu on next steps to further debug this.
> 
> 
> Brian
> 
