From owner-freebsd-fs@FreeBSD.ORG  Thu Feb 20 14:20:39 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 889508B7
 for <fs@freebsd.org>; Thu, 20 Feb 2014 14:20:39 +0000 (UTC)
Received: from smtp.digiware.nl (unknown [IPv6:2001:4cb8:90:ffff::3])
 (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 4392D1642
 for <fs@freebsd.org>; Thu, 20 Feb 2014 14:20:39 +0000 (UTC)
Received: from rack1.digiware.nl (unknown [127.0.0.1])
 by smtp.digiware.nl (Postfix) with ESMTP id B46C31534D1;
 Thu, 20 Feb 2014 15:20:37 +0100 (CET)
X-Virus-Scanned: amavisd-new at digiware.nl
Received: from smtp.digiware.nl ([127.0.0.1])
 by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id MN1UqqRlNMDP; Thu, 20 Feb 2014 15:20:35 +0100 (CET)
Received: from [192.168.101.102] (vpn.ecoracks.nl [31.223.170.173])
 (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits))
 (No client certificate requested)
 by smtp.digiware.nl (Postfix) with ESMTPSA id E48AB153448;
 Thu, 20 Feb 2014 15:20:33 +0100 (CET)
Message-ID: <53060F37.7030203@digiware.nl>
Date: Thu, 20 Feb 2014 15:20:39 +0100
From: Willem Jan Withagen <wjw@digiware.nl>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Steven Hartland <killing@multiplay.co.uk>, fs@freebsd.org
Subject: Re: What types of SSDs to use.....
References: <5305F8B0.1060308@digiware.nl>
 <783388CA2911497B98479F1187F49915@multiplay.co.uk>
 <53060C89.8040500@digiware.nl>
 <C68493DE8E7C4C269F7B4A076CC98CA5@multiplay.co.uk>
In-Reply-To: <C68493DE8E7C4C269F7B4A076CC98CA5@multiplay.co.uk>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Feb 2014 14:20:39 -0000

On 20-2-2014 15:15, Steven Hartland wrote:
> 
> ----- Original Message ----- From: "Willem Jan Withagen" <wjw@digiware.nl>
> 
> 
>> On 20-2-2014 14:06, Steven Hartland wrote:
>>> The "disconnect" issue is generally related to Sandforce based devices.
>>>
>>> Its a lot better on later devices / firmware and does depend on the
>>> controller / MB they are connected to.
>>
>> Any easy way to detect these? Or is it just a matter of reading the
>> specsheets? Hoping that the controller chipset is mentioned.
> 
> Its worse that that, its literally a try it an see.

Seeing is:
	The devices just drops of the Sata-channel??

That is what happens with me with certain older Corsair stuff.

--WjW