From owner-freebsd-questions@freebsd.org Mon Aug 27 11:46:39 2018 Return-Path: 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 5CB081085D32 for ; Mon, 27 Aug 2018 11:46:39 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 08E6C8BCC8 for ; Mon, 27 Aug 2018 11:46:38 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 70FC621BFD; Mon, 27 Aug 2018 07:46:38 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Mon, 27 Aug 2018 07:46:38 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=5JHjv9PewhmpUtKTKButYhPJRFxls sTv/s6k8Ov9vXA=; b=K2y1V2ZvaGteMxy5JlEMfJif/9OPJqacIuEWEioms+Dc4 It7HIS6BE4Ho+f7qtwqnrO1EFWjAbDo24FzsQOkaIrkXcEwidIpv6/tWWoBSnvHk da5V2nE4vvfPmC76sSacKUkzrk7mV3nPD4ppCcSV1yk9b+iz4tQdWGGW5ak6ivCo uiYezlhsHPspFysTfTGSaguYxrGCyOUu5+XpqKkI+1ympbn0RL6r3/rSu43hlpDa D/EM7yUImbS651j57T862WL6jJ3sj6LPo5PGSmhx9Bzha+IVII3D1cfFLJHwAyZH dhcjqQv86y6mHs9mZn66JwpAQCk6Y8y9fbGShAJGw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=5JHjv9 PewhmpUtKTKButYhPJRFxlssTv/s6k8Ov9vXA=; b=F1yUuTGwClEJIG7KmcBDNP asS5ew8Yemp7gabKQ1gpJYgZUz0+K3QpMf7Sm0O1BFZ3mv5j9jtvIYt+CKBT5JeH QtYIdMQLfV3XUchW0ukU0s6MNbWkJHTPdN/jDT104R2iA4FgHMnQ5fdocd8W9T5d hOrBsMSSdF+19vcmFrhRbh1ugBsxGb1s9zKgNpngpPefS/RLfUwuBB6f5N19Rdak XdHqzCtY2kc9Yp8QXq4RxRDEi7hoMfJU952SxW0tR/tkZsYz8elNvJS6AxSA3Cfx 2SiwOYBEEEw9u4uTzi87YNMuRO28/xAeLXNP6n2axPDBnr4ptUapTBKWt/OzYitw == X-ME-Proxy: X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id C4E1210288; Mon, 27 Aug 2018 07:46:37 -0400 (EDT) Subject: Re: disk or cable error? (CAM status: ATA Status Error) To: ixbug@riseup.net, FreeBSD Questions References: From: tech-lists Organization: none Message-ID: Date: Mon, 27 Aug 2018 12:46:36 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Aug 2018 11:46:39 -0000 On 26/08/2018 16:01, ixbug@riseup.net wrote: > 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) these values: 5 Reallocated_Sector_Ct 196 Reallocated_Event_Count 197 Current_Pending_Sector 198 Offline_Uncorrectable are all zero for both disks, so if these remain zero after a successful long test with *no LBA errors* then that would seem to me at least to indicate there's no problems with the disks themselves. If, in the face of those results, this persisted: > (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 08 90 a4 aa 40 1d 00 00 00 00 00 > (ada1:ahcich1:0:0:0): CAM status: ATA Status Error > (ada1:ahcich1:0:0:0): ATA status: 41 (DRDY ERR), error: 10 (IDNF ) then yeah I'd say bad cable/bad interface -- J.