Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 15 Feb 2012 11:57:33 +0100
From:      Harald Schmalzbauer <h.schmalzbauer@omnilan.de>
To:        Jeremy Chadwick <freebsd@jdc.parodius.com>
Cc:        Tom Evans <tevans.uk@googlemail.com>, freebsd-stable@freebsd.org, Oscar Prieto <oscarmpp@googlemail.com>, Martin Sugioarto <martin@sugioarto.com>, Claudius Herder <claudius@ambtec.de>
Subject:   Re: problems with AHCI on FreeBSD 8.2
Message-ID:  <4F3B8F9D.6070907@omnilan.de>
In-Reply-To: <20120215104205.GA19734@icarus.home.lan>
References:  <20120214100513.GA94501@icarus.home.lan>	<20120214135435.GQ2010@equilibrium.bsdes.net>	<20120214141601.GA98986@icarus.home.lan>	<4F3A83DE.3000200@ambtec.de>	<20120214165029.GA1852@icarus.home.lan>	<4F3A971F.9040407@omnilan.de>	<20120214192319.44ff7aff@zelda.sugioarto.com>	<CAK9wqRpjRXtkBqL%2BgX5gY3foqz-O5mT-qg7Z=_t2m=Q3rZizJg@mail.gmail.com>	<20120214195255.GA5064@icarus.home.lan>	<CAFHbX1KY9vAPFXiEQXv=M%2BqQQg17TU8BUc_P8M9FiB-gJ0FpvQ@mail.gmail.com> <20120215104205.GA19734@icarus.home.lan>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig1576C785B7FE08F3CAF7759E
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

 schrieb Jeremy Chadwick am 15.02.2012 11:42 (localtime):
> On Wed, Feb 15, 2012 at 10:19:37AM +0000, Tom Evans wrote:
>> On Tue, Feb 14, 2012 at 7:52 PM, Jeremy Chadwick
>> <freebsd@jdc.parodius.com> wrote:
>>> On Tue, Feb 14, 2012 at 08:31:23PM +0100, Oscar Prieto wrote:
>>>> I used to had tons of ahci errors in my 4 disk raidz1 worth of
>>>> HD154UIs when the rig was built a year ago or so (with 8.0 Release),=

>>>> but they dissapeared after tuning ZFS.
>>>>
>>>> Sadly i also got a new timeout days ago followed with smartcl erros =
i
>>>> still keep unchecked but i guess they cold be legit, i still have to=

>>>> test/swap cables and give it a try.
>> Interesting. I have 9 SAMSUNG HD154UI 1AG01118 in my raidz setup,
>> haven't had a problem with any of them yet (touch wood).
>>
>>> Further details which pertain to Samsung drives:
>>>
>>> In your case, you run smartd(8), which periodically hits the drive wi=
th
>>> SMART requests, pulling attribute data down and parsing it. ??I belie=
ve
>>> your model is fine for this, but for similar Samsung models, I must
>>> strongly advise against this. ??There are well-documented problems wi=
th
>>> Samsung firmwares and SMART behaviour which can result in data loss (=
yes
>>> you read that right). ??Please see smartmontools' Wiki page on the ma=
tter
>>> for full details. ??Just make sure you're running a fixed firmware:
>>>
>>> http://sourceforge.net/apps/trac/smartmontools/wiki/SamsungF4EGBadBlo=
cks
>>>
>> Yikes, I have just this week installed a HD204UI. From that page,
>> drives manufactured after December 2010 should not be affected, which
>> is fortunate as the linked firmware page doesn't seem to exist
>> anymore, Samsung no longer seem to offer support for their drives and
>> point you at Seagate, whose site (of course!) only has downloads for
>> current Seagate drives.
>>
>>
>> Hmm reading later on in the thread there is a patch to mark certain
>> drives as having flaky NCQ - in the patch it is for the SAMSUNG
>> HD154UI. As I mentioned before, I have 9 SAMSUNG HD154UI, all of which=

>> use ahci(4) and NCQ, and all work perfectly, no timeouts. This is
>> using 9-STABLE.
>>
>> I suspect that there may be more going on than 'flaky NCQ', and that
>> perhaps disabling NCQ masks the real issue.
> It could simply be a firmware bug in the drive, which is what some
> others have eluded to (and I'm in agreement with).  I would love to say=

> "compare firmware versions on your drives", except there is real
> in-the-field proof that firmware version strings often do not get
> updated/changed between firmwares (at least in the case of some Seagate=

> and Western Digital disks).  Furthermore, NCQ can "play differently" wi=
th
> different AHCI controllers.
>
> That said, the disks / firmware versions mentioned by people involved i=
n
> this thread / referenced threads are:
>
> * Victor Balada Diaz  -- SAMSUNG HD154UI, firmware 1AG01118
> * Claudius Herder     -- SAMSUNG HD753LJ, firmware 1AA01118
> * Oscar Prieto        -- SAMSUNG HD154UI, firmware 1AG01118
>   - NOTE: In Oscar's case, his drives exhibit other problems.  I
>     would provide a link but the web archive for freebsd-stable does
>     not show my mail which contains analysis of the situation
> * Harald Schmalzbauer -- not provided, but hints at Samsung EG drives
              --  SAMSUNG HD154UI, firmware 1AG01118
I still have them for "outsourcing" in one server, where they idle all
the time.

Thanks,

-Harry



--------------enig1576C785B7FE08F3CAF7759E
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (FreeBSD)

iEYEARECAAYFAk87j50ACgkQLDqVQ9VXb8jfvACfevOKSoyJ+X6zfC1O4P9O9w0k
9QYAn246EXO3a01NlbZvhhKzIemcG612
=g2ZR
-----END PGP SIGNATURE-----

--------------enig1576C785B7FE08F3CAF7759E--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F3B8F9D.6070907>