Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 11 Nov 2016 13:24:29 +0000
From:      Mike Clarke <jmc-freebsd2@milibyte.co.uk>
To:        freebsd-questions@freebsd.org
Subject:   Re: SSD drive appears to have been "downgraded" from SATA 2 to SATA 1
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>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 10 Nov 2016 18:42:50 -0800
David Christensen <dpchrist@holgerdanske.com> 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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20161111132429.720bd97b>