From owner-freebsd-questions@freebsd.org Sat Nov 12 16:42:45 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CFAB7C3D5DB for ; Sat, 12 Nov 2016 16:42:45 +0000 (UTC) (envelope-from jmc-freebsd2@milibyte.co.uk) Received: from avasout07.plus.net (avasout07.plus.net [84.93.230.235]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "Bizanga Labs SMTP Client Certificate", Issuer "Bizanga Labs CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6D58B11DC for ; Sat, 12 Nov 2016 16:42:44 +0000 (UTC) (envelope-from jmc-freebsd2@milibyte.co.uk) Received: from curlew.milibyte.co.uk ([80.229.31.82]) by avasout07 with smtp id 74ib1u0021mJoLY014icnQ; Sat, 12 Nov 2016 16:42:36 +0000 X-CM-Score: 0.00 X-CNFS-Analysis: v=2.2 cv=TLMHcBta c=1 sm=1 tr=0 a=cd0K7rcWwnZFf6xQxRobyA==:117 a=cd0K7rcWwnZFf6xQxRobyA==:17 a=kj9zAlcOel0A:10 a=MKtGQD3n3ToA:10 a=L24OOQBejmoA:10 a=dik7HMQjudEA:10 a=ZZnuYtJkoWoA:10 a=pGLkceISAAAA:8 a=akTGFlKJmygPTxPz0NEA:9 a=CjuIK1q_8ugA:10 a=6kGIvZw6iX1k4Y-7sg4_:22 Received: from curlew.lan ([192.168.1.13]) by curlew.milibyte.co.uk with esmtp (Exim 4.87) (envelope-from ) id 1c5bNz-0000do-8V for freebsd-questions@freebsd.org; Sat, 12 Nov 2016 16:42:35 +0000 Date: Sat, 12 Nov 2016 16:42:35 +0000 From: Mike Clarke To: freebsd-questions@freebsd.org Message-ID: <20161112164235.755f31a6@curlew.lan> In-Reply-To: References: <20161109222002.7995b1c9@curlew.lan> <20161110163546.7b9d4105@curlew.lan> <55557ac1-1b6e-ada0-f5fa-7830e976b910@holgerdanske.com> <20161111132429.720bd97b@curlew.lan> X-Mailer: Claws Mail 3.14.0 (GTK+ 2.24.29; amd64-portbld-freebsd11.0) MIME-Version: 1.0 X-SA-Exim-Connect-IP: 192.168.1.13 X-SA-Exim-Mail-From: jmc-freebsd2@milibyte.co.uk X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on curlew.lan X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham autolearn_force=no version=3.4.1 Subject: Re: SSD drive appears to have been "downgraded" from SATA 2 to SATA 1 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on curlew.milibyte.co.uk) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Nov 2016 16:42:45 -0000 On Fri, 11 Nov 2016 20:57:34 -0600 Adam Vande More wrote: > There is roughly a 0% chance this has anything to do with your partitioning > scheme or your cables. Agreed, but cables were easy to eliminate just in case. I can't imagine how partitioning could directly affect it but the fact that the problem arose after erasing and partitioning does suggest it might be related to something which I did at the time. > To the best of my knowledge this is basically only > alterable by BIOS settings(ahci), drive firmware settings or a jumper, > settings listed in ahci(4), and sata controller version. There's been no BIOS changes, apart from adjusting the boot priority order after moving drives between SATA ports. The BIOS has no settings which could affect the performance of just one drive. There's been no firmware updates and no settings have been changed. -- Mike Clarke