From owner-freebsd-hardware@freebsd.org Thu Nov 1 05:21:27 2018 Return-Path: Delivered-To: freebsd-hardware@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 82B68112ACB0 for ; Thu, 1 Nov 2018 05:21:27 +0000 (UTC) (envelope-from rcv-c3BhbWxlc3NAbWFpbC1vbi51cwBAMTU0MTA0OTI0NQ==@vfemail.net) Received: from smtp102-3.vfemail.net (onethreeseven.vfemail.net [199.16.11.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 13800845AC for ; Thu, 1 Nov 2018 05:21:26 +0000 (UTC) (envelope-from rcv-c3BhbWxlc3NAbWFpbC1vbi51cwBAMTU0MTA0OTI0NQ==@vfemail.net) DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=vfemail.net; h= mime-version:content-type:content-transfer-encoding:date:from:to :subject:message-id; s=2018; bh=WE/0cFsEG8RMNNvyk7C2+Hb1pXv5BRQl yzV6siy0w0s=; b=clPmEjLXlzNleMmyxTGUS9lvmzDKn3jfakgEcHTzYv7/SXQT 9zOJPXDRfFf2OjTFNzDgpMJRowB4ldWQlf9M2ZHdC5ui1E//H78GtD3Tx3IzNYWg fiTEtgpp0/ycFHu0cnUAx097T0SA4IRs7V+d2FgzOozeGncFy9z7iai9jlE= Received: (qmail 20835 invoked by uid 89); 1 Nov 2018 05:14:05 -0000 Received: by simscan 1.4.0 ppid: 20829, pid: 20832, t: 0.0694s scanners:none Received: from unknown (HELO dmZlbWFpbC5uZXRAMTU0MTA0OTI0NQ==) (c3BhbWxlc3NAbWFpbC1vbi51c0AxNTQxMDQ5MjQ1@MTcyLjE2LjEwMC4xMzdAMTU0MTA0OTI0NQ==) by 172.16.100.62 with ESMTPA; 1 Nov 2018 05:14:05 -0000 Received: from nMqyba29AuQvd9tA4ctaDuyqxjlih+cf9tfnA5eSw4fzqMzUpWC6x45v24+SiqNY (ShvNmg1AvGGoyJojO8X1/14nWEYEzcgk) by vfemail.net with HTTP (HTTP/1.1 POST); Thu, 01 Nov 2018 00:14:35 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Wed, 31 Oct 2018 22:14:35 -0700 From: spamless@mail-on.us To: freebsd-hardware Subject: When is sataIII actually sataIII? Message-ID: <032dec6a280136b4b80d77715b0b1b17@mail-on.us> X-Sender: spamless@mail-on.us User-Agent: Roundcube Webmail/1.2.4 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2018 05:21:27 -0000 Hi all, I picked out, and put together some hardware for a new FreeBSD powered box. I chose a WD blue drive I knew was pretty zippy. But I was quite disappointed to discover that FreeBSD wouldn't support it @6Gb. The following output from dmesg(8): GEOM: new disk ada0 ada0: ACS-3 ATA SATA 3.x device ada0: Serial Number WD-WCC6Y3CJCTDC ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada0: Command Queueing enabled ada0: 953869MB (1953525168 512 byte sectors) My hardware supports it; both drive, and controller. Yet for some reason FreeBSD will only *acknowledge* the capabilities. Do I need to impose some quirk, or something. Thanks! -- Chris out... From owner-freebsd-hardware@freebsd.org Thu Nov 1 11:18:43 2018 Return-Path: Delivered-To: freebsd-hardware@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0FACC10EBA1E for ; Thu, 1 Nov 2018 11:18:43 +0000 (UTC) (envelope-from frank2@fjl.co.uk) Received: from bs1.fjl.org.uk (bs1.fjl.org.uk [84.45.41.196]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "bs1.fjl.org.uk", Issuer "bs1.fjl.org.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 90E04709E1 for ; Thu, 1 Nov 2018 11:18:42 +0000 (UTC) (envelope-from frank2@fjl.co.uk) Received: from [192.168.1.43] (host31-49-127-57.range31-49.btcentralplus.com [31.49.127.57]) (authenticated bits=0) by bs1.fjl.org.uk (8.14.4/8.14.4) with ESMTP id wA1B063w075025 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO) for ; Thu, 1 Nov 2018 11:00:06 GMT (envelope-from frank2@fjl.co.uk) Date: Thu, 01 Nov 2018 10:59:57 +0000 User-Agent: K-9 Mail for Android In-Reply-To: <032dec6a280136b4b80d77715b0b1b17@mail-on.us> References: <032dec6a280136b4b80d77715b0b1b17@mail-on.us> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: When is sataIII actually sataIII? To: freebsd-hardware@freebsd.org From: "Frank Leonhardt (M)" Message-ID: <441037E6-67AD-49A9-9151-3F617A7AE1AE@fjl.co.uk> X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2018 11:18:43 -0000 On 1 November 2018 05:14:35 GMT+00:00, spamless@mail-on=2Eus wrote: >Hi all, >I picked out, and put together some hardware for a new FreeBSD >powered box=2E I chose a WD blue drive I knew was pretty zippy=2E >But I was quite disappointed to discover that FreeBSD wouldn't >support it @6Gb=2E >The following output from dmesg(8): >GEOM: new disk ada0 >ada0: ACS-3 ATA SATA 3=2Ex device >ada0: Serial Number WD-WCC6Y3CJCTDC >ada0: 300=2E000MB/s transfers (SATA 2=2Ex, UDMA6, PIO 8192bytes) >ada0: Command Queueing enabled >ada0: 953869MB (1953525168 512 byte sectors) > >My hardware supports it; both drive, and controller=2E Yet for >some reason FreeBSD will only *acknowledge* the capabilities=2E >Do I need to impose some quirk, or something=2E > >Thanks! That is saying it will do transfers at 300 Megabytes/second on the interfa= ce=2E You'll be lucky to get that from a WD desktop drive due to mechanical= limitations=2E WD blues at 1Tb tend to do 125-150MBps tops, and the range = released a couple of years back (2015?) seem slower than the previous gener= ation, although the spindle speeds vary=2E 6G vs=2E 3G is only interesting talking to silicone drives or a SATA expan= der=2E But an interesting question - why does it say SATA2 instead of SATA3? --=20 Sent from my Android device with K-9 Mail=2E Please excuse my brevity=2E From owner-freebsd-hardware@freebsd.org Thu Nov 1 13:46:10 2018 Return-Path: Delivered-To: freebsd-hardware@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A7B0010F358A for ; Thu, 1 Nov 2018 13:46:10 +0000 (UTC) (envelope-from rcv-c3BhbWxlc3NAbWFpbC1vbi51cwBAMTU0MTA3OTkyOQ==@vfemail.net) Received: from smtp102-3.vfemail.net (onethreeseven.vfemail.net [199.16.11.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46EC976B1B for ; Thu, 1 Nov 2018 13:46:10 +0000 (UTC) (envelope-from rcv-c3BhbWxlc3NAbWFpbC1vbi51cwBAMTU0MTA3OTkyOQ==@vfemail.net) DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=vfemail.net; h= mime-version:content-type:content-transfer-encoding:date:from:to :cc:subject:in-reply-to:references:message-id; s=2018; bh=ZWp029 OBh+RtQocfEavBxgotSkZ3EaMGEHJ6xFDp8ow=; b=FG4Wj+mGIJ8Jn/z3P4haos 8Kf0dmZawPJt2RONmucF+KW/Dq0PWwr1sY5yJEzAGq9vT3MQ3np0X2ndZL7jhO08 zyiL8jdaLrhBSmzyfD/3rIjjYapQBEITFwvtOHmlZ4ObW8ciphzceg2pRS1y3/dl F9x6EaMSSw4wL+HMmChWk= Received: (qmail 3501 invoked by uid 89); 1 Nov 2018 13:45:29 -0000 Received: by simscan 1.4.0 ppid: 3495, pid: 3498, t: 0.0778s scanners:none Received: from unknown (HELO dmZlbWFpbC5uZXRAMTU0MTA3OTkyOQ==) (c3BhbWxlc3NAbWFpbC1vbi51c0AxNTQxMDc5OTI5@MTcyLjE2LjEwMC4xMzdAMTU0MTA3OTkyOQ==) by 172.16.100.62 with ESMTPA; 1 Nov 2018 13:45:29 -0000 Received: from lqodwbar16GxfOrf1N4uc9aQuh0/ecB0GFZ1g+UPaHrqr+p2B9Rcq1DsgymBn5Kf (uQrne7kl1mwTCohntrci2tr5NCBC7hUz) by vfemail.net with HTTP (HTTP/1.1 POST); Thu, 01 Nov 2018 08:45:59 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Thu, 01 Nov 2018 06:45:59 -0700 From: spamless@mail-on.us To: "Frank Leonhardt (M)" Cc: freebsd-hardware@freebsd.org, owner-freebsd-hardware@freebsd.org Subject: Re: When is sataIII actually sataIII? In-Reply-To: <441037E6-67AD-49A9-9151-3F617A7AE1AE@fjl.co.uk> References: <032dec6a280136b4b80d77715b0b1b17@mail-on.us> <441037E6-67AD-49A9-9151-3F617A7AE1AE@fjl.co.uk> Message-ID: <96848c4e433f9c28a017bc467d10b232@mail-on.us> X-Sender: spamless@mail-on.us User-Agent: Roundcube Webmail/1.2.4 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2018 13:46:10 -0000 On 2018-11-01 03:59, Frank Leonhardt (M) wrote: > On 1 November 2018 05:14:35 GMT+00:00, spamless@mail-on.us wrote: >> Hi all, >> I picked out, and put together some hardware for a new FreeBSD >> powered box. I chose a WD blue drive I knew was pretty zippy. >> But I was quite disappointed to discover that FreeBSD wouldn't >> support it @6Gb. >> The following output from dmesg(8): >> GEOM: new disk ada0 >> ada0: ACS-3 ATA SATA 3.x device >> ada0: Serial Number WD-WCC6Y3CJCTDC >> ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) >> ada0: Command Queueing enabled >> ada0: 953869MB (1953525168 512 byte sectors) >> >> My hardware supports it; both drive, and controller. Yet for >> some reason FreeBSD will only *acknowledge* the capabilities. >> Do I need to impose some quirk, or something. >> >> Thanks! > > That is saying it will do transfers at 300 Megabytes/second on the > interface. You'll be lucky to get that from a WD desktop drive due to > mechanical limitations. WD blues at 1Tb tend to do 125-150MBps tops, > and the range released a couple of years back (2015?) seem slower than > the previous generation, although the spindle speeds vary. > > 6G vs. 3G is only interesting talking to silicone drives or a SATA > expander. > > But an interesting question - why does it say SATA2 instead of SATA3? Thanks for your reply, Frank! Be that as it may. As platters go. I bought this 1Tb WD blue, because all the stats for it indicated it was faster that all the major competitors, and interestingly, faster than their "high-end" Black counterpart. I also bought it, because it was quieter than all the others. That said; given that the port it runs off of, and the drive is truly a Sata 3 (3.1). Why won't FreeBSD treat it as such. Why does it penalize the drive? I have another Sata 3 drive on the second Sata 3 port, that FreeBSD actually treats as what it is: ada1 at ahcich1 bus 0 scbus1 target 0 lun 0 ada1: ACS-2 ATA SATA 3.x device ada1: Serial Number W1F55VT9 ada1: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes) ada1: Command Queueing enabled ada1: 2861588MB (5860533168 512 byte sectors) ada1: quirks=0x1<4K> note the "quirks" - is that good, or bad? In the end, it appears that I have to purchase a slower rated (Sata 3) drive to get FreeBSD to treat it as a Sata 3 drive? It makes no sense to me. Which is why I came here; in hopes of finding out *why* it appears as it does. :) Thanks again, Frank! Oh! In case it matters; this is on 12 (CURRENT) -- Chris out... From owner-freebsd-hardware@freebsd.org Thu Nov 1 16:24:07 2018 Return-Path: Delivered-To: freebsd-hardware@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C130610F7A41 for ; Thu, 1 Nov 2018 16:24:07 +0000 (UTC) (envelope-from josh@tcbug.org) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 70DD67E0DA for ; Thu, 1 Nov 2018 16:24:07 +0000 (UTC) (envelope-from josh@tcbug.org) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id D3D6221FEC for ; Thu, 1 Nov 2018 12:24:06 -0400 (EDT) Received: from web2 ([10.202.2.212]) by compute1.internal (MEProxy); Thu, 01 Nov 2018 12:24:06 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=O2b4aG+yrCB1X3emmmngFKZ21HJqrvRro1kfbpRE0 2I=; b=T7AF1oOYvvvj3fh2mAOwuhqoM43GsM9hJfY0p5jkHktKy6s1SocWAEg9J IOXGih/BTAq//VxFB81mEbz2P/eWURGfZzLc/fkEpA7J62gR0UQTaAz2VHg1rYMd c+JJ0EqJD0/HF3Sge1N6hQe8HWF07OJnrI7UT7VSkP/f2qIZvcGoKqQhae01uZR3 nkFN4ZhraymUTRW46h51cq+RzU+0Lc1uiOK9dt7r4yVjhRKxznLR1yqbB/c8fJ2M GMBjOo1np0sUHOf7jpLMl/objCo1Bp9x/l5IyWQrDShTc4h14R7SDzrsS4TLRxgd BrRD91Fuqm+IqBcbhaIVVljppmKDA== X-ME-Sender: X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 6BA96622A8; Thu, 1 Nov 2018 12:24:06 -0400 (EDT) Message-Id: <1541089446.3446788.1562395368.3456C3CC@webmail.messagingengine.com> From: Josh Paetzel To: freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-21384fa2 Date: Thu, 01 Nov 2018 11:24:06 -0500 References: <032dec6a280136b4b80d77715b0b1b17@mail-on.us> <441037E6-67AD-49A9-9151-3F617A7AE1AE@fjl.co.uk> <96848c4e433f9c28a017bc467d10b232@mail-on.us> In-Reply-To: <96848c4e433f9c28a017bc467d10b232@mail-on.us> Subject: Re: When is sataIII actually sataIII? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2018 16:24:07 -0000 On Thu, Nov 1, 2018, at 8:45 AM, spamless@mail-on.us wrote: > I have another Sata 3 drive on the second Sata 3 port, that FreeBSD > actually treats as what it is: > ada1 at ahcich1 bus 0 scbus1 target 0 lun 0 > ada1: ACS-2 ATA SATA 3.x device > ada1: Serial Number W1F55VT9 > ada1: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes) > ada1: Command Queueing enabled > ada1: 2861588MB (5860533168 512 byte sectors) > ada1: quirks=0x1<4K> > > note the "quirks" - is that good, or bad? > > In the end, it appears that I have to purchase a slower rated (Sata 3) > drive > to get FreeBSD to treat it as a Sata 3 drive? It makes no sense to me. > Which > is why I came here; in hopes of finding out *why* it appears as it does. > :) > > Thanks again, Frank! > > Oh! In case it matters; this is on 12 (CURRENT) > > -- > Chris out... > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" A full dmesg would be useful. A dmesg from a verbose boot even more useful. As well as the make and model of the motherboard. The most common problem is the controller the drive is plugged into isn't actually capable of SATA 3. -- Thanks, Josh Paetzel From owner-freebsd-hardware@freebsd.org Fri Nov 2 00:49:04 2018 Return-Path: Delivered-To: freebsd-hardware@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E923610DEFFA for ; Fri, 2 Nov 2018 00:49:03 +0000 (UTC) (envelope-from frank2@fjl.co.uk) Received: from bs1.fjl.org.uk (bs1.fjl.org.uk [84.45.41.196]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "bs1.fjl.org.uk", Issuer "bs1.fjl.org.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7D5BE6EB70 for ; Fri, 2 Nov 2018 00:49:03 +0000 (UTC) (envelope-from frank2@fjl.co.uk) Received: from roundcube.fjl.org.uk (localhost [127.0.0.1]) by bs1.fjl.org.uk (8.14.4/8.14.4) with ESMTP id wA20mt5R030877 for ; Fri, 2 Nov 2018 00:48:57 GMT (envelope-from frank2@fjl.co.uk) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Fri, 02 Nov 2018 00:48:55 +0000 From: Frank Leonhardt To: freebsd-hardware@freebsd.org Subject: Re: When is sataIII actually =?UTF-8?Q?sataIII=3F?= Organization: FJL Microsystems In-Reply-To: <1541089446.3446788.1562395368.3456C3CC@webmail.messagingengine.com> References: <032dec6a280136b4b80d77715b0b1b17@mail-on.us> <441037E6-67AD-49A9-9151-3F617A7AE1AE@fjl.co.uk> <96848c4e433f9c28a017bc467d10b232@mail-on.us> <1541089446.3446788.1562395368.3456C3CC@webmail.messagingengine.com> Message-ID: X-Sender: frank2@fjl.co.uk User-Agent: Roundcube Webmail/0.9.2 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2018 00:49:04 -0000 On 2018-11-01 16:24, Josh Paetzel wrote: > On Thu, Nov 1, 2018, at 8:45 AM, spamless@mail-on.us wrote: > >> I have another Sata 3 drive on the second Sata 3 port, that FreeBSD >> actually treats as what it is: >> ada1 at ahcich1 bus 0 scbus1 target 0 lun 0 >> ada1: ACS-2 ATA SATA 3.x device >> ada1: Serial Number W1F55VT9 >> ada1: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes) >> ada1: Command Queueing enabled >> ada1: 2861588MB (5860533168 512 byte sectors) >> ada1: quirks=0x1<4K> >> >> note the "quirks" - is that good, or bad? >> >> In the end, it appears that I have to purchase a slower rated (Sata 3) >> drive >> to get FreeBSD to treat it as a Sata 3 drive? It makes no sense to me. >> Which >> is why I came here; in hopes of finding out *why* it appears as it >> does. >> :) >> >> Thanks again, Frank! >> >> Oh! In case it matters; this is on 12 (CURRENT) >> >> -- >> Chris out... > A full dmesg would be useful. A dmesg from a verbose boot even more > useful. > As well as the make and model of the motherboard. > > The most common problem is the controller the drive is plugged into > isn't actually capable of SATA 3. Also, I guess you know that 12-CURRENT is the riskiest one to be testing on. You didn't mention that before :-) Boot from an 11.2-RELEASE CD and see what it has to say. I take what people say about computing equipment and its performance with a pinch of salt. would be surprised that WDs blurb says it's cheap blue series is faster than the enterprise versions, if anything manufacturers said surprised me any more. Gotta link? Regards, Frank. From owner-freebsd-hardware@freebsd.org Fri Nov 2 05:59:36 2018 Return-Path: Delivered-To: freebsd-hardware@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C090810E9E26; Fri, 2 Nov 2018 05:59:36 +0000 (UTC) (envelope-from freebsd.ed.lists@sumeritec.com) Received: from mx12-out3.antispamcloud.com (mx12-out3.antispamcloud.com [46.165.232.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4FC6477790; Fri, 2 Nov 2018 05:59:35 +0000 (UTC) (envelope-from freebsd.ed.lists@sumeritec.com) Received: from [153.92.8.106] (helo=srv31.niagahoster.com) by mx64.antispamcloud.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1gIQhy-000AWq-DW; Fri, 02 Nov 2018 05:05:20 +0100 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sumeritec.com; s=default; h=Content-Transfer-Encoding:Content-Type: MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=4nLqFA7zaO9JZtCyL6Wk2BKJVkowqKyPrDBo4zjDcYw=; b=LJtXpix2wAcwK8Tcg6OBegbZiV Biohe2wrob7cN35o2ZpXXZaRp3E+zes9xvTKy3MGFQaaZPuQimnAM6jHDPBPScgvTMxGtYT5PAn+0 Dlfwe+censNcu5Bzc0ED5CbcEHk39c+M3tZk5lx/9lDgQRcwNECrefuJ7An25gKKMDPYhl+zK73s1 q0OJ8Gh7BdyuSqXvT2mL6UUQ3Z+2yjRwmduk9Da4g9dHcdVbXHMkjjNaAGe3i3lCPbXBSOiZXy5eR mvpErgHW/zeOusZ2psfJ2um0Lb696CIN9s3WDJkUDTCF6MRFc2Mg8LppQugx61eN/Xz3TVYjm1fRR kQx714NQ==; Received: from [114.125.70.82] (port=59040 helo=X220.sumeritec.com) by srv31.niagahoster.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91) (envelope-from ) id 1gIQh9-0001FR-Tv; Fri, 02 Nov 2018 11:04:30 +0700 Date: Fri, 2 Nov 2018 12:04:25 +0800 From: Erich Dollansky To: spamless@mail-on.us Cc: "Frank Leonhardt (M)" , owner-freebsd-hardware@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: When is sataIII actually sataIII? Message-ID: <20181102120425.1eac52a6.freebsd.ed.lists@sumeritec.com> In-Reply-To: <96848c4e433f9c28a017bc467d10b232@mail-on.us> References: <032dec6a280136b4b80d77715b0b1b17@mail-on.us> <441037E6-67AD-49A9-9151-3F617A7AE1AE@fjl.co.uk> <96848c4e433f9c28a017bc467d10b232@mail-on.us> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-OutGoing-Spam-Status: No, score=-1.0 X-AuthUser: freebsd.ed.lists@sumeritec.com X-Originating-IP: 153.92.8.106 X-Spampanel-Domain: out.niagahoster.com X-Spampanel-Username: niaga Authentication-Results: antispamcloud.com; auth=pass (login) smtp.auth=niaga@out.niagahoster.com X-Spampanel-Outgoing-Class: unsure X-Spampanel-Outgoing-Evidence: Combined (0.33) X-Recommended-Action: accept X-Filter-ID: EX5BVjFpneJeBchSMxfU5hgi3EreTnrGtPkjI834S0d602E9L7XzfQH6nu9C/Fh9KJzpNe6xgvOx q3u0UDjvO+EaZ0GbijHxRcz4oP8/IcLrXqzbCjEbfJcqXRzelCwdJYatjgJunsRNfMQFfYnhxhIm J5L8JocZ7jvPcgMkCMV3VX5A48T6P4xubSjFh0hwl7WsDxTYdI14JuFmYmLrCXdVfkDjxPo/jG5t KMWHSHC+ISrFe72eyO6n5th9UY3qpE0KurALx3gZEUL+kkQtfNfwYErb4UK8xFf97EoF4gz1QeyV xVRA9dztHGwWW2LHO8DwfkFdMffakKgrcPlJVeu7dvKRLva/AIIO8eOYXd4gEYh/T53XX75pHgh4 pvdG6kWj/oTmSjq0cPzQCt37wMIzUpqvZq13ZdV+Dz2qnPrSnpRQJQZtOYs+WpieyK5FYxCXQdz/ yY6aVFc655KhQLMwcEc3vNONPjeXjGqV6cX/H4cUFSfpzkoM4YQhwp+FboZD5vPFe84pJQGk5dfb FPdfcXgLzsY3kBHC+ZTZl3RnfVPTqI4dkGNDDD1o0bE1+PPsFj6ib/rQkXcCYXtbCsB9K/tfe8pL mJg0fcGy9gwRLqjTJeBPrTCjLL/wN7uMRUcRfS0hzbGRZdtpa0UZ/x9JJ5TIDkE1afsdX6NhD5se Ap+VO4oFSk8mBIBXo2BFn1XwgQVNqOZrXojH570PbJjbEksSRvq4Ne9nSwTkw0MHmFDqewO9xyOq CYO8P1aH5QN1pbH809GVckHaDoCpXXo4cWULbQ7n4oHCN8vAOSyzZP4WsPyMiNT0QIPYGQDkmITc ejG7wMdK1E502JTuVj8f4c9vM4DS96zDbei4qnRy2DNwOgV373pfDhBQ21Odu5oPzYTjEFnVmuJd 2kIIOrAxbi1c8P9QQRXgktvJsTJU8juKnz9wuBfd0E2e+rEPGJdimYZGouioJWKkMaVHGrOzr+Hl BNv4rXAGTFZjslUYQV5S2tL01oGmO4has73rVGkGolmtL78gKYrUH0FYKWmLg7MtquaU1JUdAqYs iGzeYbKNKdqhCvbyyx+iMF8Pa6P2ogp9kacJnWQ52TaV/A== X-Report-Abuse-To: spam@quarantine1.antispamcloud.com X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2018 05:59:37 -0000 Hi, On Thu, 01 Nov 2018 06:45:59 -0700 spamless@mail-on.us wrote: > On 2018-11-01 03:59, Frank Leonhardt (M) wrote: > > On 1 November 2018 05:14:35 GMT+00:00, spamless@mail-on.us wrote: > >> Hi all, > >> I picked out, and put together some hardware for a new FreeBSD > >> powered box. I chose a WD blue drive I knew was pretty zippy. > >> But I was quite disappointed to discover that FreeBSD wouldn't > >> support it @6Gb. > >> The following output from dmesg(8): > >> GEOM: new disk ada0 > >> ada0: ACS-3 ATA SATA 3.x device > >> ada0: Serial Number WD-WCC6Y3CJCTDC > >> ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) > >> ada0: Command Queueing enabled > >> ada0: 953869MB (1953525168 512 byte sectors) > >> > >> My hardware supports it; both drive, and controller. Yet for > >> some reason FreeBSD will only *acknowledge* the capabilities. > >> Do I need to impose some quirk, or something. > >> > >> Thanks! > > > > That is saying it will do transfers at 300 Megabytes/second on the > > interface. You'll be lucky to get that from a WD desktop drive due > > to mechanical limitations. WD blues at 1Tb tend to do 125-150MBps > > tops, and the range released a couple of years back (2015?) seem > > slower than the previous generation, although the spindle speeds > > vary. > > > > 6G vs. 3G is only interesting talking to silicone drives or a SATA > > expander. > > > > But an interesting question - why does it say SATA2 instead of > > SATA3? > > Thanks for your reply, Frank! > Be that as it may. As platters go. I bought this 1Tb WD blue, because > all > the stats for it indicated it was faster that all the major > competitors, and interestingly, faster than their "high-end" Black > counterpart. I also > bought it, because it was quieter than all the others. > That said; given that the port it runs off of, and the drive is truly > a Sata 3 (3.1). Why won't FreeBSD treat it as such. Why does it > penalize the drive? > I have another Sata 3 drive on the second Sata 3 port, that FreeBSD > actually treats as what it is: > ada1 at ahcich1 bus 0 scbus1 target 0 lun 0 > ada1: ACS-2 ATA SATA 3.x device > ada1: Serial Number W1F55VT9 > ada1: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes) > ada1: Command Queueing enabled > ada1: 2861588MB (5860533168 512 byte sectors) > ada1: quirks=0x1<4K> > > note the "quirks" - is that good, or bad? > > In the end, it appears that I have to purchase a slower rated (Sata > 3) drive > to get FreeBSD to treat it as a Sata 3 drive? It makes no sense to > me. Which > is why I came here; in hopes of finding out *why* it appears as it > does. :) > > Thanks again, Frank! > > Oh! In case it matters; this is on 12 (CURRENT) > forget about the marketing bullshit. You might have a very basic problem: the cable. Just change cables randomly. If you see then changes on a drive, you have to expect that there is a problem with the cable. Erich From owner-freebsd-hardware@freebsd.org Fri Nov 2 13:36:58 2018 Return-Path: Delivered-To: freebsd-hardware@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A710E10F7211 for ; Fri, 2 Nov 2018 13:36:58 +0000 (UTC) (envelope-from frank2@fjl.co.uk) Received: from bs1.fjl.org.uk (bs1.fjl.org.uk [84.45.41.196]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "bs1.fjl.org.uk", Issuer "bs1.fjl.org.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3F0C16AEA2 for ; Fri, 2 Nov 2018 13:36:57 +0000 (UTC) (envelope-from frank2@fjl.co.uk) Received: from roundcube.fjl.org.uk (localhost [127.0.0.1]) by bs1.fjl.org.uk (8.14.4/8.14.4) with ESMTP id wA2DaeUt073497 for ; Fri, 2 Nov 2018 13:36:44 GMT (envelope-from frank2@fjl.co.uk) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Fri, 02 Nov 2018 13:36:40 +0000 From: Frank Leonhardt To: freebsd-hardware@freebsd.org Subject: Fwd: Re: When is sataIII actually =?UTF-8?Q?sataIII=3F?= Organization: FJL Microsystems Message-ID: X-Sender: frank2@fjl.co.uk User-Agent: Roundcube Webmail/0.9.2 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2018 13:36:58 -0000 On Thu, Nov 1, 2018, at 8:45 AM, spamless@mail-on.us wrote: > I have another Sata 3 drive on the second Sata 3 port, that FreeBSD > actually treats as what it is: > ada1 at ahcich1 bus 0 scbus1 target 0 lun 0 > ada1: ACS-2 ATA SATA 3.x device > ada1: Serial Number W1F55VT9 > ada1: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes) > ada1: Command Queueing enabled > ada1: 2861588MB (5860533168 512 byte sectors) > ada1: quirks=0x1<4K> > > note the "quirks" - is that good, or bad? > Forgot to mention (and then the power went off) - the quirks mechanism is to allow work-arounds for flawed implementations of protocols from specific devices. For example, if a particular drive always returns the same serial number to satisfy the protocol, it's a quirk and the driver won't make use of the query serial number command for that type of drive. Regards, Frank. From owner-freebsd-hardware@freebsd.org Fri Nov 2 13:50:01 2018 Return-Path: Delivered-To: freebsd-hardware@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3963F10F7771; Fri, 2 Nov 2018 13:50:01 +0000 (UTC) (envelope-from frank2@fjl.co.uk) Received: from bs1.fjl.org.uk (bs1.fjl.org.uk [84.45.41.196]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "bs1.fjl.org.uk", Issuer "bs1.fjl.org.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CCA9E6B946; Fri, 2 Nov 2018 13:50:00 +0000 (UTC) (envelope-from frank2@fjl.co.uk) Received: from roundcube.fjl.org.uk (localhost [127.0.0.1]) by bs1.fjl.org.uk (8.14.4/8.14.4) with ESMTP id wA2Dnvnt076221; Fri, 2 Nov 2018 13:49:57 GMT (envelope-from frank2@fjl.co.uk) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Fri, 02 Nov 2018 13:49:57 +0000 From: Frank Leonhardt To: spamless@mail-on.us Cc: freebsd-hardware@freebsd.org, owner-freebsd-hardware@freebsd.org Subject: Re: When is sataIII actually =?UTF-8?Q?sataIII=3F?= Organization: FJL Microsystems In-Reply-To: <96848c4e433f9c28a017bc467d10b232@mail-on.us> References: <032dec6a280136b4b80d77715b0b1b17@mail-on.us> <441037E6-67AD-49A9-9151-3F617A7AE1AE@fjl.co.uk> <96848c4e433f9c28a017bc467d10b232@mail-on.us> Message-ID: X-Sender: frank2@fjl.co.uk User-Agent: Roundcube Webmail/0.9.2 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2018 13:50:01 -0000 On 2018-11-01 13:45, spamless@mail-on.us wrote: > On 2018-11-01 03:59, Frank Leonhardt (M) wrote: >> On 1 November 2018 05:14:35 GMT+00:00, spamless@mail-on.us wrote: >>> Hi all, >>> I picked out, and put together some hardware for a new FreeBSD >>> powered box. I chose a WD blue drive I knew was pretty zippy. >>> But I was quite disappointed to discover that FreeBSD wouldn't >>> support it @6Gb. >>> The following output from dmesg(8): >>> GEOM: new disk ada0 >>> ada0: ACS-3 ATA SATA 3.x device >>> ada0: Serial Number WD-WCC6Y3CJCTDC >>> ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) >>> ada0: Command Queueing enabled >>> ada0: 953869MB (1953525168 512 byte sectors) >>> >>> My hardware supports it; both drive, and controller. Yet for >>> some reason FreeBSD will only *acknowledge* the capabilities. >>> Do I need to impose some quirk, or something. >>> >>> Thanks! >> >> That is saying it will do transfers at 300 Megabytes/second on the >> interface. You'll be lucky to get that from a WD desktop drive due to >> mechanical limitations. WD blues at 1Tb tend to do 125-150MBps tops, >> and the range released a couple of years back (2015?) seem slower than >> the previous generation, although the spindle speeds vary. >> >> 6G vs. 3G is only interesting talking to silicone drives or a SATA >> expander. >> >> But an interesting question - why does it say SATA2 instead of SATA3? > > Thanks for your reply, Frank! > Be that as it may. As platters go. I bought this 1Tb WD blue, because > all > the stats for it indicated it was faster that all the major > competitors, > and interestingly, faster than their "high-end" Black counterpart. I > also > bought it, because it was quieter than all the others. > That said; given that the port it runs off of, and the drive is truly > a Sata 3 (3.1). Why won't FreeBSD treat it as such. Why does it > penalize > the drive? > I have another Sata 3 drive on the second Sata 3 port, that FreeBSD > actually treats as what it is: > ada1 at ahcich1 bus 0 scbus1 target 0 lun 0 > ada1: ACS-2 ATA SATA 3.x device > ada1: Serial Number W1F55VT9 > ada1: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes) > ada1: Command Queueing enabled > ada1: 2861588MB (5860533168 512 byte sectors) > ada1: quirks=0x1<4K> Another point comes to mind. As Erich pointed out, changing cables about randomly is a known trouble-shooting method, but the cables are theoretically identical, and all good for 1m in length. *theoretically*. But, SATA 3 is backwards compatible with SATA 2. This works by the controller and the drive deciding whether both sides are SATA 3, and if one disagrees they'll fall back to SATA 2 (or SATA 1). This could easily be an incompatibility at the hardware level. Have you checked that ALL the sockets on your motherboard are SATA 3? It's quite possible there are some slower ones for attaching optical drives etc. Is it restricted in the motherboard hardware settings? (sometimes called BIOS settings). Regards, Frank.