From owner-freebsd-stable@FreeBSD.ORG Sun Mar 11 17:12:24 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 99ABD106566B for ; Sun, 11 Mar 2012 17:12:24 +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 194148FC12 for ; Sun, 11 Mar 2012 17:12:24 +0000 (UTC) Received: from rack1.digiware.nl (localhost.digiware.nl [127.0.0.1]) by mail.digiware.nl (Postfix) with ESMTP id E15B515346A for ; Sun, 11 Mar 2012 18:12:22 +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 ESWArIhmWFdd for ; Sun, 11 Mar 2012 18:12:22 +0100 (CET) Received: from [192.168.10.67] (opteron [192.168.10.67]) by mail.digiware.nl (Postfix) with ESMTP id 191CC153433 for ; Sun, 11 Mar 2012 18:12:22 +0100 (CET) Message-ID: <4F5CDCF5.5050906@digiware.nl> Date: Sun, 11 Mar 2012 18:12:21 +0100 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: "stable@freebsd.org" References: <4F2940C1.10901@digiware.nl> In-Reply-To: <4F2940C1.10901@digiware.nl> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: 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: Sun, 11 Mar 2012 17:12:24 -0000 On 2012-02-01 14:40, Willem Jan Withagen wrote: > Hi, > > I have this ZFS server up for about 27 days, and about 3 weeks ago (was > not really paying attention) it turns out it lost its SSD that I'm using > for log and cache. There is also a poor and lonely memory stick for log. > So the box did not really suffer file loss. > > system is running: > FreeBSD zfs.digiware.nl 8.2-STABLE FreeBSD 8.2-STABLE #58: Thu Nov 17 > 09:43:46 CET 2011 > root@zfs.digiware.nl:/home/obj/usr/src/src8/src/sys/ZFS amd64 > > more info like dmesg, pciconf, kernconf, zpool iostat at: > http://www.tegenbosch28.nl/FreeBSD/systems/ZFS/ > > But it is weird to just lose a SSD from the bus. And it has happened > before. And you can see that AHCI really banged on the frontdoor... > > The device is a Corsair 60Gb Force GT. And thusfar I have not found any > suggestions that that serie of devices is prone to doing this. > > It was a real dead device, the only way to get it back: > powercycle the device by pulling it, and stick it back > then camcontrol rescan > > I've now upgrade it to a 120Gb Corsair, to see if that has the same problem. > > Other FreeBSD-ers have like problems? > > Regards, > --WjW > > > Jan 7 10:04:24 zfs kernel: ahcich3: Timeout on slot 27 port 0 > Jan 7 10:04:24 zfs kernel: ahcich3: is 00000000 cs 20000000 ss 38000000 > rs 38000000 tfd c0 serr 00000000 cmd 0004dd17 > Jan 7 10:04:56 zfs kernel: ahcich3: AHCI reset: device not ready after > 31000ms (tfd = 00000080) > Jan 7 10:05:26 zfs kernel: ahcich3: Timeout on slot 29 port 0 > Jan 7 10:05:26 zfs kernel: ahcich3: is 00000000 cs 20000000 ss 00000000 > rs 20000000 tfd 80 serr 00000000 cmd 0004dd17 > Jan 7 10:05:57 zfs kernel: ahcich3: AHCI reset: device not ready after > 31000ms (tfd = 00000080) > Jan 7 10:06:27 zfs kernel: ahcich3: Timeout on slot 29 port 0 > Jan 7 10:06:27 zfs kernel: ahcich3: is 00000000 cs 20000000 ss 00000000 > rs 20000000 tfd 80 serr 00000000 cmd 0004dd17 > Jan 7 10:06:27 zfs kernel: (ada2:ahcich3:0:0:0): lost device > Jan 7 10:06:58 zfs kernel: ahcich3: AHCI reset: device not ready after > 31000ms (tfd = 00000080) > Jan 7 10:07:28 zfs kernel: ahcich3: Timeout on slot 29 port 0 > Jan 7 10:07:28 zfs kernel: ahcich3: is 00000000 cs e0000000 ss e0000000 > rs e0000000 tfd 80 serr 00000000 cmd 0004dd17 > Jan 7 10:08:16 zfs kernel: ahcich3: AHCI reset: device not ready after > 31000ms (tfd = 00000080) > Jan 7 10:08:16 zfs kernel: ahcich3: Poll timeout on slot 31 port 0 > Jan 7 10:08:16 zfs kernel: ahcich3: is 00000000 cs 80000000 ss 00000000 > rs 80000000 tfd 80 serr 00000000 cmd 0004df17 > Jan 7 10:08:46 zfs kernel: ahcich3: Timeout on slot 31 port 0 > Jan 7 10:08:46 zfs kernel: ahcich3: is 00000000 cs 80000000 ss 00000000 > rs 80000000 tfd 80 serr 00000000 cmd 0004df17 > Jan 7 10:08:48 zfs kernel: (ada2:ahcich3:0:0:0): removing device entry > Jan 7 10:09:33 zfs kernel: ahcich3: AHCI reset: device not ready after > 31000ms (tfd = 00000080) > Jan 7 10:09:33 zfs kernel: ahcich3: Poll timeout on slot 31 port 0 > Jan 7 10:09:33 zfs kernel: ahcich3: is 00000000 cs 80000000 ss 00000000 > rs 80000000 tfd 80 serr 00000000 cmd 0004df17 Just as a followup. I reported the above problem.... Today it occurred again. But this time I was able to find a firmware upgrade for the Corsair Force GT from 1.2 to 1.3.3 (Need Win7 to be able to upgrade....) Hopefully that helps, and it does not disconnect about every 4 weeks. Ciao, --WjW