From owner-freebsd-hardware@FreeBSD.ORG Tue Oct 28 12:22:57 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4F6661065684; Tue, 28 Oct 2008 12:22:57 +0000 (UTC) (envelope-from fbsd@dannysplace.net) Received: from mail.dannysplace.net (mail.dannysplace.net [213.133.54.210]) by mx1.freebsd.org (Postfix) with ESMTP id 061268FC26; Tue, 28 Oct 2008 12:22:56 +0000 (UTC) (envelope-from fbsd@dannysplace.net) Received: from 203-206-171-212.perm.iinet.net.au ([203.206.171.212] helo=[192.168.10.10]) by mail.dannysplace.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1Kunb0-000Kjp-Pr; Tue, 28 Oct 2008 22:22:55 +1000 Message-ID: <4907041E.4050705@dannysplace.net> Date: Tue, 28 Oct 2008 22:22:54 +1000 From: Danny Carroll User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: Jeremy Chadwick References: <20081026125017.GA88016@icarus.home.lan> <4906EF86.7050702@dannysplace.net> <20081028121425.GA48941@icarus.home.lan> In-Reply-To: <20081028121425.GA48941@icarus.home.lan> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Authenticated-User: danny X-Authenticator: plain X-Sender-Verify: SUCCEEDED (sender exists & accepts mail) X-Exim-Version: 4.69 (build at 08-Jul-2008 08:59:40) X-Date: 2008-10-28 22:22:51 X-Connected-IP: 203.206.171.212:3814 X-Message-Linecount: 68 X-Body-Linecount: 54 X-Message-Size: 2690 X-Body-Size: 1971 X-Received-Count: 1 X-Recipient-Count: 3 X-Local-Recipient-Count: 3 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 X-SA-Exim-Connect-IP: 203.206.171.212 X-SA-Exim-Rcpt-To: koitsu@FreeBSD.org, spork@bway.net, freebsd-hardware@freebsd.org X-SA-Exim-Mail-From: fbsd@dannysplace.net X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on ferrari.dannysplace.net X-Spam-Level: X-Spam-Status: No, score=0.2 required=8.0 tests=ALL_TRUSTED,TVD_RCVD_IP autolearn=disabled version=3.2.5 X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail.dannysplace.net) Cc: Charles Sprickman , freebsd-hardware@freebsd.org Subject: Re: PCI-X SATA Card + Server Recommendation X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: fbsd@dannysplace.net List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2008 12:22:57 -0000 Jeremy Chadwick wrote: > Re: SATAII: if the product data sheet or the user manual states the card > supports SATA300, then yes. > > Re: NCQ: the user manual probably answers this question, or a FAQ/KB > article. I hope you're not planning on disabling write caching on your > disks (as people often ask if controllers or drives supports command > queueing so they can do this. NCQ does not provide the amount of > performance increase like SCSI command queuing does. On the other > hand, TCQ (often found on SAS drives) does.) That's a good point about the cache, I forgot about the one on the drives. > I have no idea. I suppose it would have to support pass(4), or provide > the functionality itself (Areca controllers do the latter). 3ware as well I am told. > I recommend avoiding Adaptec. I will repeat that: avoid Adaptec. I appreciate the comment, can you tell me why or is it a personal preference? > You are not going to find a SATA card that has non-RAID capability with > that amount of ports. Besides, it shouldn't matter to you if the card > has RAID capability, because nothing forces you to use it. All that > should matter to you is the following: > > * Is the card version/model supported under FreeBSD? > * Does the card supports disks in a JBOD fashion (not part of an array)? > * Can I get SMART stats from the drive (or via CLI; see below)? > * Is there a native FreeBSD CLI binary for controlling features of the > controller if I need it? Yup. > >> There is not much out there and it's all expensive. > > But neither of these are FreeBSD problems. The same would apply if you > were using any operating system. No, I agree it is not a Freebsd problem. It's everything to do with demand at the moment. > I have not seen these on any of our systems. Chances are they're ACPI > or AML errors which can be fixed by the vendor with a BIOS upgrade. > I would recommend asking about this on freebsd-acpi instead. Thanks! -D