From owner-freebsd-questions@freebsd.org Sat Nov 12 02:57:37 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 DB61FC3CB9D for ; Sat, 12 Nov 2016 02:57:37 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 70903D0E for ; Sat, 12 Nov 2016 02:57:37 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: by mail-wm0-x234.google.com with SMTP id t79so9409663wmt.0 for ; Fri, 11 Nov 2016 18:57:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=6f4RUAar8P4bcDhvEco3N26b2P0jISfn+sZbRlK8dco=; b=PM4AM9RZGk8KEV4nqTkGwAW2UGDzHdqQSaiv1KQOevGjNMsvMFKPbrbjVwbF1ftfuD AVvsrwVTI9CNsEm9V5cTGluEWb3Y6C8garckHjVMQYhakc+hFtHQV1nYJDyL7io3RnlE YsuEeyheSSVNXLiAGcDGzWcK/W3JE4Iwso/4Lc4RjusUz+nzwbbuYhIpRpETxBSaVQUI kzwEvrRQkhSO0AAfk/kuvGzKoK6DyZQKTH/sMEMavk1FtgJlKVyRKLDqQZYPjoFzwK7Z D1i8VhfHI7xnNkvsslzmOy+j6ooFNhoCj1ZL3jhyc+NBGBhpCE3ur7G+neJZBLYVbhBC IAFA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=6f4RUAar8P4bcDhvEco3N26b2P0jISfn+sZbRlK8dco=; b=Kk4ZRr0rlFYMFRYWUMJbfv5lG3sDxJc4hsNTEfRYrJknM2tUYfs8LDk4yBW2Gn/HEo AwXmHBLTpHcWiMfQYkn01tJKZ7kaYjgD+kiEY4xpgsg5v6pHnAkT+qWkXngFbv/e390o 9p4x65vrxf904A2lkytgEq8DZzdllhIvqIxLtRB6cdrC8VU2jpG3EJ65baAJ99H1OWrc FFX+OVZi8bNbJIF+uNw+5caFndSE4Ci6cK1utvZIGfwDbctaYh4I3nufTa+1hqVCR1H7 YwhCJKrHxGQGRIx1ilZmutvUNGHFKqnGhiSXELQlEPb6KqmTnBjxrEQaV7E1gM2wcgn1 Rfhw== X-Gm-Message-State: ABUngvcvoMMLNnf9Y/BWGziBo//OwGHvbT1O2rDnIvvsXhzdhL+TIBrg77jZOpbism0rpQfgt9KlbXScrd580Q== X-Received: by 10.194.177.231 with SMTP id ct7mr706718wjc.221.1478919455397; Fri, 11 Nov 2016 18:57:35 -0800 (PST) MIME-Version: 1.0 Received: by 10.80.179.119 with HTTP; Fri, 11 Nov 2016 18:57:34 -0800 (PST) In-Reply-To: <20161111132429.720bd97b@curlew.lan> References: <20161109222002.7995b1c9@curlew.lan> <20161110163546.7b9d4105@curlew.lan> <55557ac1-1b6e-ada0-f5fa-7830e976b910@holgerdanske.com> <20161111132429.720bd97b@curlew.lan> From: Adam Vande More Date: Fri, 11 Nov 2016 20:57:34 -0600 Message-ID: Subject: Re: SSD drive appears to have been "downgraded" from SATA 2 to SATA 1 To: Mike Clarke Cc: FreeBSD Questions Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 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 02:57:38 -0000 On Fri, Nov 11, 2016 at 7:24 AM, Mike Clarke wrote: > 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. -- Adam