From owner-freebsd-questions@freebsd.org Mon Aug 17 19:20:38 2015 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 D43BA9BC289 for ; Mon, 17 Aug 2015 19:20:38 +0000 (UTC) (envelope-from dweimer@dweimer.net) Received: from webmail.dweimer.net (24-240-198-187.static.stls.mo.charter.com [24.240.198.187]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.dweimer.net", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B03BF10C1 for ; Mon, 17 Aug 2015 19:20:38 +0000 (UTC) (envelope-from dweimer@dweimer.net) Received: from webmail.dweimer.local (webmail [192.168.5.2]) by webmail.dweimer.net (8.15.2/8.15.2) with ESMTPS id t7HJKb96082783 (version=TLSv1.2 cipher=DHE-RSA-CHACHA20-POLY1305 bits=256 verify=NO); Mon, 17 Aug 2015 14:20:37 -0500 (CDT) (envelope-from dweimer@dweimer.net) Received: (from www@localhost) by webmail.dweimer.local (8.15.2/8.15.2/Submit) id t7HJKbZ9082782; Mon, 17 Aug 2015 14:20:37 -0500 (CDT) (envelope-from dweimer@dweimer.net) X-Authentication-Warning: webmail.dweimer.local: www set sender to dweimer@dweimer.net using -f To: PK1048 Subject: Re: Quick Hard Drive Error Question X-PHP-Script: www.dweimer.net/webmail/index.php for 71.86.41.122, 192.168.5.3 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Mon, 17 Aug 2015 14:20:37 -0500 From: dweimer Cc: FreeBSD Questions Organization: dweimer.net Reply-To: dweimer@dweimer.net Mail-Reply-To: dweimer@dweimer.net In-Reply-To: <6E95ACB0-EB0A-471E-9815-7B791DC25F67@pk1048.com> References: <46e87057b2ac9672e581dcd794bf1111@dweimer.net> <6E95ACB0-EB0A-471E-9815-7B791DC25F67@pk1048.com> Message-ID: <258b0fe633fac36a6c78798be616c778@dweimer.net> X-Sender: dweimer@dweimer.net User-Agent: Roundcube Webmail/1.1.2 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Aug 2015 19:20:39 -0000 On 2015-08-17 1:05 pm, PK1048 wrote: > On Aug 17, 2015, at 8:56, dweimer wrote: > >> I have an external SATA drive dock that I use to write backups to, I >> have steadily been getting more parity/CRC errors over the last couple >> of weeks. >> >> Aug 17 00:14:14 freebsd kernel: (ada4:ahcich5:0:0:0): >> WRITE_FPDMA_QUEUED. ACB: 61 00 70 e7 53 40 85 00 00 01 00 00 >> Aug 17 00:14:14 freebsd kernel: (ada4:ahcich5:0:0:0): CAM status: >> Uncorrectable parity/CRC error >> Aug 17 00:14:14 freebsd kernel: (ada4:ahcich5:0:0:0): Retrying command >> Aug 17 00:14:14 freebsd kernel: (ada4:ahcich5:0:0:0): >> READ_FPDMA_QUEUED. ACB: 60 70 d0 c6 1c 40 84 00 00 00 00 00 >> Aug 17 00:14:14 freebsd kernel: (ada4:ahcich5:0:0:0): CAM status: >> Uncorrectable parity/CRC error >> Aug 17 00:14:14 freebsd kernel: (ada4:ahcich5:0:0:0): Retrying command >> >> I have ran smart tests on the drives, they report no errors, hers the >> most recent summary line from the currently mounted drive. > > Are there any port multipliers involved ? When I had 4 SATA drives > behind a port multiplier I had these type of errors frequently under > high load. I was using ZFS so dialed back the outstanding queue depth > from 10 to 2 to reduce load and the errors went away. I have since > gone to one port per drive (and went back to the default queue depth > of 10) and have not had the problem recur… > > But, I have seen a “finicky-ness” between eSATA ports and cables. > Certain cables work on certain ports but not on others. Have you tried > substituting the eSATA cable ? A different eSATA port perhaps ? No multipliers, 1 drive on the port, don't have another eSATA cable just the one that currently in use. It was running fine over five months on the current cables. I did disconnect and reconnect the cables to make sure it wasn't just a lose cable. They are not regularly moved around, which could lead to material fatigue. Of course the disks are swapped weekly, so it could be the docks connection to the disk that is the week point. I have periodically seen an error or two like this, if they are frequent I dismount and re-seat the disk then all would clear up. That's not working now and the errors are happening more frequently. Hopefully once installed I will be OK, if not, at least I have gained the SATA III performance and I can start looking into other possibilities. -- Thanks, Dean E. Weimer http://www.dweimer.net/