From owner-freebsd-questions@freebsd.org Thu Nov 10 16:35:52 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 ECB76C3A753 for ; Thu, 10 Nov 2016 16:35:52 +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 8DB27A78 for ; Thu, 10 Nov 2016 16:35:51 +0000 (UTC) (envelope-from jmc-freebsd2@milibyte.co.uk) Received: from curlew.milibyte.co.uk ([80.229.31.82]) by avasout07 with smtp id 6Gbn1u0051mJoLY01GbohW; Thu, 10 Nov 2016 16:35:48 +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=D7rCoLxHAAAA:8 a=tE1Fxce_aoG8XxpfViUA:9 a=CjuIK1q_8ugA:10 a=P3xHhOtoK6rroZ9zpUER:22 Received: from curlew.lan ([192.168.1.13]) by curlew.milibyte.co.uk with esmtp (Exim 4.87) (envelope-from ) id 1c4sKI-0000hn-Ma for freebsd-questions@freebsd.org; Thu, 10 Nov 2016 16:35:47 +0000 Date: Thu, 10 Nov 2016 16:35:46 +0000 From: Mike Clarke To: freebsd-questions@freebsd.org Message-ID: <20161110163546.7b9d4105@curlew.lan> In-Reply-To: <20161109222002.7995b1c9@curlew.lan> References: <20161109222002.7995b1c9@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: Thu, 10 Nov 2016 16:35:53 -0000 On Wed, 9 Nov 2016 22:20:02 +0000 Mike Clarke wrote: > Could there be any way that the system could at some time have forced > the drive down to SATA 1, in which case how do I revert it? Or is it > more likely that I have a faulty SSD drive? I've now managed to establish that the drive had been functioning in SATA 2 300MB/s mode until yesterday when I re-partitioned it to overcome a problem which had been preventing me from booting from it. Copies of /var/run/dmesg.boot from my backups show that the drive was performing as SATA 2 300MB/s until yesterday. Before re-partitioning the drive I used camcontrol to clear its contents and mark all cells empty with: camcontrol security ada0 -s buhbyesweetdata -e buhbyesweetdata I'm now only seeing SATA2 150MB/s for that drive. curlew:/home/mike% camcontrol identify ada0 | head -2 pass1: ATA8-ACS SATA 3.x device pass1: 150.000MB/s transfers (SATA 1.x, UDMA5, PIO 512bytes) It looks as though the camcontrol security command has somehow also caused the drive to drop down to SATA 1 mode. Is there any way I can use camcontrol (or any other utility) to restore this? -- Mike Clarke