From owner-freebsd-hardware@FreeBSD.ORG Mon Oct 29 19:22:42 2012 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5B458CBA for ; Mon, 29 Oct 2012 19:22:42 +0000 (UTC) (envelope-from nate.keegan@gmail.com) Received: from mail-vc0-f182.google.com (mail-vc0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id E07C98FC14 for ; Mon, 29 Oct 2012 19:22:41 +0000 (UTC) Received: by mail-vc0-f182.google.com with SMTP id fw7so7139413vcb.13 for ; Mon, 29 Oct 2012 12:22:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=8Baw0Q/n1Cy1JlbAh9LxpR/raLuhr67vepVf/sUKrBI=; b=H4WJa6w128wanLgiXD156B8wf9Xkxib0GuXxGUZwHM1gt6wLJ2NylBFHWwzGiGYLz3 tWzsQCy0TTPcLrJ4i8rNFqO20f+WwuOYN5iQu6hgr8CvYOjqofWwHDT9j7uXFfn3f2je gyV/iUIc+wcL2KHK0e0mXljHumKtp0kg8mLkDxrlIlO842z6Bhf4t3sV4B18h9Osq/vx gJwNkHkoGUZWXnEijWIqKuojujq5CC6H/EQm8AiI76BNAjDLqZLDFamWMWyrqsJNlDJh Us4WVHLEuoxxznJwWXo2w9bGodwrPnSdH1Tp45TderfZHdyjal7AGQ8YRN1RAeb0gonK U7gA== MIME-Version: 1.0 Received: by 10.221.2.76 with SMTP id nt12mr10145493vcb.12.1351538561127; Mon, 29 Oct 2012 12:22:41 -0700 (PDT) Received: by 10.58.240.42 with HTTP; Mon, 29 Oct 2012 12:22:41 -0700 (PDT) In-Reply-To: <20121029104329.GA58203@server.rulingia.com> References: <20121029104329.GA58203@server.rulingia.com> Date: Mon, 29 Oct 2012 12:22:41 -0700 Message-ID: Subject: Re: SSD dropping off bus From: nate keegan To: Peter Jeremy Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-hardware@freebsd.org X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2012 19:22:42 -0000 I tried all sorts of things and the solution for me was to ditch Crucial SSD for straight SATA disks. http://lists.freebsd.org/pipermail/freebsd-hardware/2012-October/007135.html On Mon, Oct 29, 2012 at 3:43 AM, Peter Jeremy wrote: > Several months ago, I added a OCZ Agility4 SSD to my 8.3 system. It > had been running without problem but yesterday the system reported: > > Oct 28 08:54:36 server kernel: ahcich3: Timeout on slot 25 port 0 > Oct 28 08:54:36 server kernel: ahcich3: is 00000000 cs 00000000 ss ffc1ffff rs ffc1ffff tfd 50 serr 00000800 cmd 0004b017 > Oct 28 08:57:40 server kernel: ahcich3: AHCI reset: device not ready after 31000ms (tfd = 000000d0) > Oct 28 08:57:40 server kernel: ahcich3: Timeout on slot 16 port 0 > Oct 28 08:57:40 server kernel: ahcich3: is 00000000 cs 00010000 ss 00000000 rs 00010000 tfd d0 serr 00000000 cmd 0004b017 > Oct 28 08:57:40 server kernel: ahcich3: AHCI reset: device not ready after 31000ms (tfd = 000000d0) > Oct 28 08:57:40 server kernel: ahcich3: Timeout on slot 16 port 0 > Oct 28 08:57:40 server kernel: ahcich3: is 00000000 cs 00010000 ss 00000000 rs 00010000 tfd d0 serr 00000000 cmd 0004b017 > Oct 28 08:57:40 server kernel: (ada6:ahcich3:0:0:0): lost device > Oct 28 08:57:40 server kernel: ahcich3: AHCI reset: device not ready after 31000ms (tfd = 000000d0) > Oct 28 08:57:40 server kernel: ahcich3: Timeout on slot 16 port 0 > Oct 28 08:57:40 server kernel: ahcich3: is 00000000 cs ffff07ff ss ffff07ff rs ffff07ff tfd d0 serr 00000000 cmd 0004b017 > > Power-cycling the SSD recovered it and smartctl shows no problems. > This makes me suspect it's an incompatibility between the SSD and > the SATA controller or FreeBSD driver. > > The SSD is directly connected to a ATI IXP600 (one of the onboard > ports on my Gigabyte GA-MA770-DS3) and is partitioned 3 ways: > - a mirror in my ZFS root > - ZIL for tha main data pool > - L2ARC for tha main data pool > > Has anyone else seen this behaviour? > > The SSD firmware is currently 1.4.1.3 but the latest firmware on the > OCZ site is 1.5.2 (though the release notes don't describe the > differences). Has anyone tried either firmware version? > > -- > Peter Jeremy