From owner-freebsd-stable@FreeBSD.ORG Thu Nov 17 11:03:30 2011 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 4AF47106564A for ; Thu, 17 Nov 2011 11:03:30 +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 D8F2A8FC08 for ; Thu, 17 Nov 2011 11:03:29 +0000 (UTC) Received: from rack1.digiware.nl (localhost.digiware.nl [127.0.0.1]) by mail.digiware.nl (Postfix) with ESMTP id 46D2C153434; Thu, 17 Nov 2011 12:03:29 +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 gVuTWNTImIzb; Thu, 17 Nov 2011 12:03:27 +0100 (CET) Received: from [192.168.10.67] (opteron [192.168.10.67]) by mail.digiware.nl (Postfix) with ESMTP id D5DA6153433; Thu, 17 Nov 2011 12:03:26 +0100 (CET) Message-ID: <4EC4E9FE.2060208@digiware.nl> Date: Thu, 17 Nov 2011 12:03:26 +0100 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: Peter Maloney References: <4EC3E0E4.5010704@digiware.nl> <4EC3F13B.4020700@brockmann-consult.de> In-Reply-To: <4EC3F13B.4020700@brockmann-consult.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: Trouble with SSD on SATA 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: Thu, 17 Nov 2011 11:03:30 -0000 On 2011-11-16 18:22, Peter Maloney wrote: > Willem, > > I can only guess, but... > > Is AHCI enabled in the bios? If you are not using 'fake-raid' for any > disks, you should [depending on FreeBSD version, HBA, etc.] probably > enable AHCI. Some servers actually come with SATA set in IDE mode. And > if you are using zfs, the controller optimally should not be RAID at > all. And if you have AHCI enabled already, try disabling it (losing hot > swapping ability, and some performance). ACHI is enabled otherwise I cannot used the last set of SATA connectors with this MB. Controller for these connectors is CH9. > What version of FreeBSD are you using? I had a terrible experience with > ZFS on FreeBSD 8.2 release, and 8.2-stable-April2011. I would recommend > upgrading to the latest 8-stable with cvsup. I'm at most 1 month behind on STABLE, since I just upgrade in about that frequency... Might vary a little on the amount of rumbling on the list. > This thread seems related: > http://forums.freebsd.org/showthread.php?t=24189 > > The guy was using 8.2 release, and he downgraded to an old version of > the driver to fix, saying that a patch also existed in 8-stable that > fixes the problem. > > Are you using an expander? No SATA expanders... > What HBA / hard disk controller are you using? A combi of CH9 and ARECA in PCI-X, disks are all exported a single disks. Thanx for the suggestions.... -_WjW > Am 16.11.2011 17:12, schrieb Willem Jan Withagen: >> Hi, >> >> I'm getting these: >> >> Nov 16 16:40:49 zfs kernel: ata6: port is not ready (timeout 15000ms) >> tfd = 00000080 >> Nov 16 16:40:49 zfs kernel: ata6: hardware reset timeout >> Nov 16 16:41:50 zfs kernel: ata6: port is not ready (timeout 15000ms) >> tfd = 00000080 >> Nov 16 16:41:50 zfs kernel: ata6: hardware reset timeout >> >> When inserting the tray with a SSD disk connected to that controller. >> >> Which is probably due to a BIOS upgrade.... >> At least it started after upgrading the BIOS. So I'm asking SuperMicro >> for an older version. >> >> When this happens, the system sometimes panics, haven't written the >> details yet down right now. somewhere in get_devices... >> >> After the panic I really need to powerdown the machine, otherwise it >> boots but stalls at finding any disks. It does not just find no disks, >> it "freezes" at the point it should report the found disks in the >> bios-boot. >> So apparently the ata controller are left in a very confused state. >> >> Why is the controller found at boot, and works as it should. >> And why later it just starts generating these hardware resets?? >> >> --WjW >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"