From owner-freebsd-hackers@freebsd.org Mon Mar 13 00:48:54 2017 Return-Path: Delivered-To: freebsd-hackers@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 BD2A3D075AC for ; Mon, 13 Mar 2017 00:48:54 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 9AA641537 for ; Mon, 13 Mar 2017 00:48:54 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: by mailman.ysv.freebsd.org (Postfix) id 9740FD075AB; Mon, 13 Mar 2017 00:48:54 +0000 (UTC) Delivered-To: hackers@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 952C0D075AA for ; Mon, 13 Mar 2017 00:48:54 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: from mail-qk0-x22f.google.com (mail-qk0-x22f.google.com [IPv6:2607:f8b0:400d:c09::22f]) (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 4DC481536 for ; Mon, 13 Mar 2017 00:48:54 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: by mail-qk0-x22f.google.com with SMTP id y76so212525138qkb.0 for ; Sun, 12 Mar 2017 17:48:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=longcount-org.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=nTLiKYQT0w8DL0wP2IoGs9372L8OtFE+lBbir1KYjss=; b=iMQ7FH7fhyU19UntcJnhQAlbEXAkuHsAJwtRB+bEOV1QWB4yHLKiNRyzlBZQvLpZIM B3BC/Ghy0kGqdkTdmEZ/oFMy9YpPdngHsqYYI02UwyX5ZFHcurSVEAYXw2FxQaRfRF5x 6ABJDPEr+ZjVV3SWiNGhN62ikgMFQWvE6DRZHZ2pDbBHmpYenZyf5uwKpE3zabQJWRYZ Xa0zbav3XgpKdqjwR8i4CYeMVS1A5EiOWGlj+pDzgl+Wem2TS36PEEUkhJspnjxw1d4M m6tRQWt8VaNbik0q+rlvxyTL235hqjRv0IoU32j+a6Z4j1Vo/VlSczeAM/ytqi/hyCFg lv1g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=nTLiKYQT0w8DL0wP2IoGs9372L8OtFE+lBbir1KYjss=; b=hcAPSsu7JqaIbJ6GSU62yunQey+EkomqN5cPcmz5tpnsIH0UylZrS027V7k0OZLLsZ uvjPhlNPnA/c/wT6AxKrPqkqrWYJrDR+p7k6a+3MGdzID0Gr21eL5dE+wkD0UbEyfEAY UIhTKHQ6wNfWVMyLrKBH4JMTXjm0i3HIUdYcHxat89Ej02JAdLTf8y2Ts994/FXEY8gp FcmhAJmmDaYeSiH6/WHhCRRakDdvEUvdjJY7EviaUg5tY3YlOFTEi3I0OvbCkirirrj8 jqviQg3L4vKOaH2ItPUsf/oEVd410VHc5kyfsNiSJNUvZB5FIdhXlxStQvdzTG+2QX5K Fgnw== X-Gm-Message-State: AMke39lAzmJAk+YPH5YhXcAkJ0uGc4MXvQhDpGZ3nmsDm9t+mul7jYkYUI+T0SKu72hOEA== X-Received: by 10.55.72.7 with SMTP id v7mr30887857qka.47.1489366132643; Sun, 12 Mar 2017 17:48:52 -0700 (PDT) Received: from [192.168.1.3] (ool-4351f21a.dyn.optonline.net. [67.81.242.26]) by smtp.gmail.com with ESMTPSA id 53sm11167518qtm.69.2017.03.12.17.48.51 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 12 Mar 2017 17:48:51 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: Mini sas forward/ reverse cables ? From: Mark Saad X-Mailer: iPhone Mail (14D27) In-Reply-To: Date: Sun, 12 Mar 2017 20:48:50 -0400 Cc: hackers@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <4AF2C082-2494-42DE-B2C2-9C750BF39F76@longcount.org> To: Michael Fuckner X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Mar 2017 00:48:54 -0000 > On Mar 12, 2017, at 5:02 PM, Michael Fuckner wrote: >=20 >> On 3/12/2017 9:54 PM, Mark Saad wrote: >> All >> I read this post on zfs corruption and there is an interesting comment a= bout cable types . >>=20 >> http://changelog.complete.org/archives/9769-silent-data-corruption-is-rea= l >> The part of the story I found interesting was how the disks didn't show u= p in the controller bios . > > I have that issue with a similar card on this server . So has anyone > e= ver seen this cabling issue ? Is it worth changing? How do I know > > which cable I have ? >=20 >=20 > it's pretty straight forward- if your controller is multilane and backplan= e single- you need a straight cable. This is the default! >=20 > If your controller is single and your backplane is multilane, your cable n= eeds to be cross over. If it is working, there is no need to change. >=20 What sort of markings would I look for ? Are the connections different ? Als= o the post indicated it was something they overlooked on their initial build= out that gave them a working ( albeit poorly ) setup . > Regards, > Michael! >=20 >=20 >=20 --- Mark Saad | nonesuch@longcount.org=