From owner-freebsd-stable@FreeBSD.ORG Mon Feb 13 22:12:43 2012 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 56F16106566C for ; Mon, 13 Feb 2012 22:12:43 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from mail.digiware.nl (mail.ip6.digiware.nl [IPv6:2001:4cb8:1:106::2]) by mx1.freebsd.org (Postfix) with ESMTP id D8E708FC08 for ; Mon, 13 Feb 2012 22:12:42 +0000 (UTC) Received: from rack1.digiware.nl (localhost.digiware.nl [127.0.0.1]) by mail.digiware.nl (Postfix) with ESMTP id 58B20153434; Mon, 13 Feb 2012 23:12:41 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.nl Received: from mail.digiware.nl ([127.0.0.1]) by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kreoVUjkjySI; Mon, 13 Feb 2012 23:12:40 +0100 (CET) Received: from [192.168.10.10] (vaio [192.168.10.10]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.digiware.nl (Postfix) with ESMTPSA id D596D153433; Mon, 13 Feb 2012 23:12:40 +0100 (CET) Message-ID: <4F398AD8.7010609@digiware.nl> Date: Mon, 13 Feb 2012 23:12:40 +0100 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: Jeremy Chadwick References: <4F2940C1.10901@digiware.nl> <20120201143942.GA96012@icarus.home.lan> <4F2960A7.8040705@digiware.nl> <20120201163556.GA97343@icarus.home.lan> <4F297FD5.7090809@digiware.nl> <4F39372E.5030105@digiware.nl> <20120213162810.GA75832@icarus.home.lan> In-Reply-To: <20120213162810.GA75832@icarus.home.lan> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "stable@freebsd.org" Subject: Re: Troube with SSD 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: Mon, 13 Feb 2012 22:12:43 -0000 On 13-2-2012 17:28, Jeremy Chadwick wrote: > On Mon, Feb 13, 2012 at 05:15:42PM +0100, Willem Jan Withagen wrote: >> On 2012-02-01 19:09, Willem Jan Withagen wrote: >>> On 2012-02-01 17:35, Jeremy Chadwick wrote: > The SATA PHY counters for the disk, kept in GP log area 0x11, look > perfectly fine. The 11 you see at offset 0xa are completely fine; > nothing to worry about there. > > Sadly the SSD does not support GP log area 0x04. > > Overall I see no real problems with the drive itself given the > information above, which is literally all I can go off of. Sorry I > can't be of more assistance past this point; honestly your drive looks > fine given what I can tell. Only Corsair would be able to help at this > point, but it's unlikely any Tier 1 individual would know how to > troubleshoot this kind of thing. I'll let it run, until it disconnects again, and I'll check to see what the SATA stats are. Perhaps there is something that triggers. But that might take a few days.... Last time it took 23 days under my regular load to be dropped from the bus. --WjW