From owner-freebsd-bugs@FreeBSD.ORG Tue Mar 13 16:47:56 2012 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8FB341065672 for ; Tue, 13 Mar 2012 16:47:56 +0000 (UTC) (envelope-from markm-lists@intellasoft.net) Received: from mail.mystoragebox.com (mail.mystoragebox.com [64.27.7.19]) by mx1.freebsd.org (Postfix) with ESMTP id 7C1278FC16 for ; Tue, 13 Mar 2012 16:47:56 +0000 (UTC) Received: from cpe-67-240-79-210.nycap.res.rr.com ([67.240.79.210] helo=[192.168.35.110]) by mail.mystoragebox.com with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from ) id 1S7UZB-0007PX-7i for freebsd-bugs@freebsd.org; Tue, 13 Mar 2012 12:27:17 -0400 Message-ID: <4F5F7A3B.1010309@intellasoft.net> Date: Tue, 13 Mar 2012 12:47:55 -0400 From: Mark Murawski User-Agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: freebsd-bugs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Promise SATA 300 TX4 Problem X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Mar 2012 16:47:56 -0000 I'm having drive problems with my sata controller. I've seen something very similar to this bug reported in the way back: http://forums.freebsd.org/showthread.php?t=17642 http://lists.freebsd.org/pipermail/freebsd-stable/2011-April/062428.html It's not a hardware problem. The same hardware running linux has no problems at all (same hard drives, sata cables, promise board and everything) Usually during zfs resilvering I'll see something like this. ata2: timeout waiting to issue command ata2: error issuing ATA_IDENTIFY command ata2: SIGNATURE: ffffffff ata2: timeout waiting to issue command ata2: error issuing ATA_IDENTIFY command ata2: SIGNATURE: ffffffff I have 5 mirrors in a zfs pool. Throughout the day, one drive in each mirror, one by one will drop out with those errors, and eventually get removed from the pool. Rebooting "fixes" the problem until the drives start timing out again.