From owner-freebsd-questions@freebsd.org Fri Nov 11 13:24:44 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 BF1CBC3B4FA for ; Fri, 11 Nov 2016 13:24:44 +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 5EEC1132E for ; Fri, 11 Nov 2016 13:24:43 +0000 (UTC) (envelope-from jmc-freebsd2@milibyte.co.uk) Received: from curlew.milibyte.co.uk ([80.229.31.82]) by avasout07 with smtp id 6dQY1u00A1mJoLY01dQZTY; Fri, 11 Nov 2016 13:24:33 +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=ZubcGFkXAAAA:8 a=InJrZTXqAAAA:8 a=M3sCYeuqPuhJxP9h_XwA:9 a=CjuIK1q_8ugA:10 a=kUx6feENxpTNjkNjdsbW:22 a=WwJ7OKCui7YMbFU4sWpb:22 Received: from curlew.lan ([192.168.1.13]) by curlew.milibyte.co.uk with esmtp (Exim 4.87) (envelope-from ) id 1c5Bok-0000T0-8f for freebsd-questions@freebsd.org; Fri, 11 Nov 2016 13:24:32 +0000 Date: Fri, 11 Nov 2016 13:24:29 +0000 From: Mike Clarke To: freebsd-questions@freebsd.org Message-ID: <20161111132429.720bd97b@curlew.lan> In-Reply-To: <55557ac1-1b6e-ada0-f5fa-7830e976b910@holgerdanske.com> References: <20161109222002.7995b1c9@curlew.lan> <20161110163546.7b9d4105@curlew.lan> <55557ac1-1b6e-ada0-f5fa-7830e976b910@holgerdanske.com> 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: Fri, 11 Nov 2016 13:24:44 -0000 On Thu, 10 Nov 2016 18:42:50 -0800 David Christensen wrote: > On 11/10/2016 08:35 AM, Mike Clarke wrote: > > Is there any way I can use camcontrol (or any other utility) to > > restore this? > > Put the drive in a Windows machine, download and install manufacturer > diagnostic (SanDisk SSD Dashboard), and see what it offers: > > http://kb.sandisk.com/app/answers/detail/a_id/15108/kw/x210 I tried that yesterday. Although Windows 7 could see the drive SSD Dashboard failed to detect it. This morning I discovered that camcontrol probably isn't the culprit. The next step in rebuilding my ZFS pool was to delete everything on the second drive and re partition it to match the new layout. Instead of using "camcontrol security" for this drive I mounted the ZFS system on /mnt and used "rm -r" to delete all the contents then "zfs destroy -r" to get rid of the filesystem and all the snapshots, followed by "zpool destroy" to remove the pool. Up to this point the second drive had been running at 300MB/s but after rebooting it came up at 150MB/s like the other drive. For my next step I'll delete the GPT partitioning scheme from this empty drive and try formatting it with Windows 7 to see if that makes it visible to SSD Dashboard. -- Mike Clarke