On Thu, Jun 10, 2010 at 04:04:42PM +0300, Pasi Kärkkäinen wrote:
> > Intel X25-M G1 firmware 8820 (80GB MLC)
> > Intel X25-M G2 firmware 02HD (160GB MLC)
> >
>
> What problems did you have with the X25-M models?
I'm not the OP, but I've had two X25M G2's (80 and 160 GByte)
suddenly die out me,
On Thu, Jun 10, 2010 at 05:46:19AM -0700, Peter Eriksson wrote:
> Just a quick followup that the same issue still seems to be there on our
> X4500s with the latest Solaris 10 with all the latest patches and the
> following SSD disks:
>
> Intel X25-M G1 firmware 8820 (80GB MLC)
> Intel X25-M G2 f
Just a quick followup that the same issue still seems to be there on our X4500s
with the latest Solaris 10 with all the latest patches and the following SSD
disks:
Intel X25-M G1 firmware 8820 (80GB MLC)
Intel X25-M G2 firmware 02HD (160GB MLC)
However - things seem to work smoothly with:
Inte
On Tue, 15 Sep 2009, Eric Schrock wrote:
> I don't have the ATA spec in front of me, but that that looks like pretty
> normal output to me. Glad to hear they addressed the issue.
Excellent; I reinstalled it in my test x4500, if no other issues show up I
can try to get my proposal to install them
On Sep 15, 2009, at 8:32 PM, Paul B. Henson wrote:
I updated to the new X25-E firmware, and I think it might have
resolved the
problem. smartctl under Linux no longer give a warning, and the
diskstat
check under Solaris no longer appears to have garbage. I attached
output
from smartctl, d
On Sun, 13 Sep 2009, Eric Schrock wrote:
> Actually, it's not one byte - the entire page is garbage (as we saw in
> the dtrace output). But I'm guessing that smartctl (and hardware SATL)
> is aborting on the first invalid record, while we keep going and blindly
> "translate" one form of garbage i
Now tested a firmware 8850 X25-E in one of our X4500:s and things look better:
> # /ifm/bin/smartctl -d scsi -l selftest /dev/rdsk/c5t7d0s0
> smartctl version 5.38 [i386-pc-solaris2.10] Copyright (C) 2002-8 Bruce Allen
> Home page is http://smartmontools.sourceforge.net/
>
> No self-tests have be
I can confirm that on an X4240 with the LSI (mpt) controller:
X25-M G1 with 8820 still returns invalid selftest data
X25-E G1 with 8850 now returns correct selftest data
(I haven't got any X25-M G2)
Going to replace an X25-E with the old firmware in one of our X4500s
soon and we'll see if things
On Sun, 13 Sep 2009, Mike Gerdts wrote:
> August 11 they released firmware revisions 8820, 8850, and 02G9,
> depending on the drive model.
Ooooh, cool, last time I checked they only had updates for the X25-M.
Thanks for the pointer.
___
zfs-discuss mail
On Sep 12, 2009, at 10:49 PM, Paul B. Henson wrote:
In any case, I agree with you that the firmware is buggy; however I
disagree with you as to the outcome of that bug. The drive is not
returning
random garbage, it has *one* byte wrong. Other than that all of the
data
seems ok, at least to
On Sep 12, 2009, at 11:14 PM, Paul B. Henson wrote:
On Sat, 12 Sep 2009, Paul B. Henson wrote:
On another note, my understanding is that the official Sun sold
and supported SSD for the x4540 is basically just an OEM'd Intel X25-
E. Did
Sun install their own fixed firmware on their version of
On Sun, Sep 13, 2009 at 1:14 AM, Paul B. Henson wrote:
> On Sat, 12 Sep 2009, Paul B. Henson wrote:
>
>> In any case, I agree with you that the firmware is buggy; however I
>> disagree with you as to the outcome of that bug. The drive is not
>> returning random garbage, it has *one* byte wrong. Ot
On Sat, 12 Sep 2009, Paul B. Henson wrote:
> In any case, I agree with you that the firmware is buggy; however I
> disagree with you as to the outcome of that bug. The drive is not
> returning random garbage, it has *one* byte wrong. Other than that all of
> the data seems ok, at least to my inexp
On Sat, 12 Sep 2009, Eric Schrock wrote:
> Also, were you ever able to get this disk behind a SAS transport (X4540,
> J4400, J4500, etc)? It would be interesting to see how hardware SATL
> deals with this invalid data. Output from 'smartctl -d sat' and
> 'smartctl -d scsi' on such a system would
On Sat, 12 Sep 2009, Eric Schrock wrote:
> Your statement that it is "just fine" is false:
I didn't say it worked "perfectly", I said it worked "fine". Yes, it gave a
*warning* that the "SMART Selective Self-Test Log Data Structure Revision
Number" was 0 instead of 1, **however** other than that
Carson Gaspar wrote:
Except you replied to me, not to the person who has SSDs. I have dead
standard hard disks, and the mpt driver is just not happy. After
applying 141737-04 to my Sol 10 system, things improved greatly, and
the constant bus resets went away. After upgrading to OpenSolaris 6/
James C. McPherson wrote:
On Thu, 10 Sep 2009 12:31:11 -0700
Carson Gaspar wrote:
Alex Li wrote:
We finally resolved this issue by change LSI driver. For details, please
refer to here
http://enginesmith.wordpress.com/2009/08/28/ssd-faults-finally-resolved/
Anyone from Sun have any knowledge o
On Thu, 10 Sep 2009 12:31:11 -0700
Carson Gaspar wrote:
> Alex Li wrote:
> > We finally resolved this issue by change LSI driver. For details, please
> > refer to here
> > http://enginesmith.wordpress.com/2009/08/28/ssd-faults-finally-resolved/
>
> Anyone from Sun have any knowledge of when the
Also, were you ever able to get this disk behind a SAS transport
(X4540, J4400, J4500, etc)? It would be interesting to see how
hardware SATL deals with this invalid data. Output from 'smartctl -d
sat' and 'smartctl -d scsi' on such a system would show both the ATA
data and the translated
On Sep 12, 2009, at 12:00 AM, Paul B. Henson wrote:
Well, I won't claim the drive firmware is completely innocent, but as
evidenced in
http://mail.opensolaris.org/pipermail/fm-discuss/2009-June/
000436.html
smartctl on a Linux box seems to work just fine. The exact same
model drive
also
On Fri, 11 Sep 2009, Eric Schrock wrote:
> It's clearly bad firmware - there's no bug in the sata driver. That
> drive basically returns random data, and if you're unlucky that
> randomness will look like a valid failure response. In the process I
> found one or two things that could be tightene
On Sep 11, 2009, at 8:48 PM, Paul B. Henson wrote:
x4500's have Marvell SATA controllers, not LSI. My issue with Intel
SSD's
being marked faulty in X4500's has yet to be resolved. The last time I
rebooted it fm started marking the SSD failed again due to invalid
self-check log data. I had so
On Thu, 10 Sep 2009, Alex Li wrote:
> We finally resolved this issue by change LSI driver. For details, please
> refer to here
> http://enginesmith.wordpress.com/2009/08/28/ssd-faults-finally-resolved/
I believe you hijacked my thread ;).
x4500's have Marvell SATA controllers, not LSI. My issue
Alex Li wrote:
We finally resolved this issue by change LSI driver. For details, please
refer to here
http://enginesmith.wordpress.com/2009/08/28/ssd-faults-finally-resolved/
Anyone from Sun have any knowledge of when the open source mpt driver will be
less broken? Things improved greatly for
We finally resolved this issue by change LSI driver. For details, please refer
to here http://enginesmith.wordpress.com/2009/08/28/ssd-faults-finally-resolved/
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensola
We found lots of SAS Controller Reset and errors to SSD on our servers
(OpenSolaris 2008.05 and 2009.06 with third-party JBOD and X25-E). Whenever
there is an error, the MySQL insert takes more than 4 seconds. It was quite
scary.
Eventually our engineer disabled the Fault Management SMART Pooli
26 matches
Mail list logo
