From owner-freebsd-questions@freebsd.org  Fri Aug 31 07:38:08 2018
Return-Path: <owner-freebsd-questions@freebsd.org>
Delivered-To: freebsd-questions@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id B64BBF768B2
 for <freebsd-questions@mailman.ysv.freebsd.org>;
 Fri, 31 Aug 2018 07:38:08 +0000 (UTC)
 (envelope-from ixbug@riseup.net)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "*.riseup.net",
 Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 502BF86610
 for <freebsd-questions@freebsd.org>; Fri, 31 Aug 2018 07:38:08 +0000 (UTC)
 (envelope-from ixbug@riseup.net)
Received: from cotinga.riseup.net (cotinga-pn.riseup.net [10.0.1.164])
 (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "*.riseup.net",
 Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK))
 by mx1.riseup.net (Postfix) with ESMTPS id 8C08F1A0492
 for <freebsd-questions@freebsd.org>; Fri, 31 Aug 2018 00:38:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak;
 t=1535701081; bh=1L/IgYNilhIRfnX99lZK5r0c2vGRBmgjKQSSVfVBhUw=;
 h=Subject:To:References:From:Date:In-Reply-To:From;
 b=At74cZ5liUwfCwKBQM2PaP+H7WtbT4AdE9lyyFREsjj7BIlQ0F+of4k8YtbMssm1A
 En8/9pzLfF83WXxqjt6hbucYH1rFBlR/gi4MJtdw6o/5B50s24KGGSYQ1Fow3ap8xJ
 jVRFThVHdjR3sOl7G621ppqTaSxP8Q6cM3EZXEe0=
X-Riseup-User-ID: A7A6D9342D2A0A9ADEB821AA1E3C04AB37C7AFBFF0613D4F01E09A037578C89F
Received: from [127.0.0.1] (localhost [127.0.0.1])
 by cotinga.riseup.net with ESMTPSA id 68C8A66FFA
 for <freebsd-questions@freebsd.org>; Fri, 31 Aug 2018 00:37:59 -0700 (PDT)
Subject: Re: disk or cable error? (CAM status: ATA Status Error) [solved]
To: freebsd-questions@freebsd.org
References: <c9124cc8-7be9-a0ad-62f3-2ebebbd00a9b@riseup.net>
From: ixbug@riseup.net
Message-ID: <6559e016-94fc-9653-ba5b-104f5fc37366@riseup.net>
Date: Fri, 31 Aug 2018 07:37:00 +0000
MIME-Version: 1.0
In-Reply-To: <c9124cc8-7be9-a0ad-62f3-2ebebbd00a9b@riseup.net>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Aug 2018 07:38:08 -0000

> Do any of these errors provide hints as to whether this is a disk error affecting both at the same time
> or broken cable? (both disks are connected to the mainboard via the same cable)

for the record:

after replacing the cable that connected both disks to the mainboard
everything is fine again.

thanks for your input!