From owner-freebsd-stable@FreeBSD.ORG Wed Feb 15 10:19:38 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8C269106564A for ; Wed, 15 Feb 2012 10:19:38 +0000 (UTC) (envelope-from tevans.uk@googlemail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 41C798FC0C for ; Wed, 15 Feb 2012 10:19:38 +0000 (UTC) Received: by vbbfa15 with SMTP id fa15so889766vbb.13 for ; Wed, 15 Feb 2012 02:19:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=HSWzjGsQgdnHkeFN3inTgHNyYMvnOCcGQXLEUSpE92o=; b=Dz2r3B4ZSEsFAt6I+0zXA9IBwKZxR2h2E7pK8fftJsh7sxwUXYXSPI0L+mbusly6bI HgIEh4Mkzuar91GP8asyf3CuVFPUMlcAfepNlIpfmFtMfUr3R4gkVizdx4Ki/hLmZBCD w6Q+adp9B6yLPkC9OgHpDe2XfWPn9z3Cign+k= MIME-Version: 1.0 Received: by 10.52.94.33 with SMTP id cz1mr10785786vdb.132.1329301177727; Wed, 15 Feb 2012 02:19:37 -0800 (PST) Received: by 10.52.91.210 with HTTP; Wed, 15 Feb 2012 02:19:37 -0800 (PST) In-Reply-To: <20120214195255.GA5064@icarus.home.lan> References: <20120214091909.GP2010@equilibrium.bsdes.net> <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> <20120214195255.GA5064@icarus.home.lan> Date: Wed, 15 Feb 2012 10:19:37 +0000 Message-ID: From: Tom Evans To: Jeremy Chadwick Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: Harald Schmalzbauer , Claudius Herder , freebsd-stable@freebsd.org, Oscar Prieto , Martin Sugioarto Subject: Re: problems with AHCI on FreeBSD 8.2 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Feb 2012 10:19:38 -0000 On Tue, Feb 14, 2012 at 7:52 PM, Jeremy Chadwick 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 with > SMART requests, pulling attribute data down and parsing it. =C2=A0I belie= ve > your model is fine for this, but for similar Samsung models, I must > strongly advise against this. =C2=A0There are well-documented problems wi= th > Samsung firmwares and SMART behaviour which can result in data loss (yes > you read that right). =C2=A0Please see smartmontools' Wiki page on the ma= tter > for full details. =C2=A0Just make sure you're running a fixed firmware: > > http://sourceforge.net/apps/trac/smartmontools/wiki/SamsungF4EGBadBlocks > 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. Cheers Tom