SSD drive appears to have been "downgraded" from SATA 2 to SATA 1

Adam Vande More amvandemore at
Sat Nov 12 02:57:38 UTC 2016

On Fri, Nov 11, 2016 at 7:24 AM, Mike Clarke <jmc-freebsd2 at>

> 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

There is roughly a 0% chance this has anything to do with your partitioning
scheme or your cables.  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.


More information about the freebsd-questions mailing list