From owner-freebsd-questions@FreeBSD.ORG Tue Jul 24 18:10:13 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D68151065674 for ; Tue, 24 Jul 2012 18:10:13 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from email2.allantgroup.com (email2.emsphone.com [199.67.51.116]) by mx1.freebsd.org (Postfix) with ESMTP id 74D318FC0C for ; Tue, 24 Jul 2012 18:10:13 +0000 (UTC) Received: from dan.emsphone.com (dan.emsphone.com [172.17.17.101]) by email2.allantgroup.com (8.14.4/8.14.4) with ESMTP id q6OI4LJe084912 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 24 Jul 2012 13:04:21 -0500 (CDT) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (smmsp@localhost [127.0.0.1]) by dan.emsphone.com (8.14.5/8.14.5) with ESMTP id q6OI4L9K098315 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 24 Jul 2012 13:04:21 -0500 (CDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.14.5/8.14.5/Submit) id q6OI4LN9098314; Tue, 24 Jul 2012 13:04:21 -0500 (CDT) (envelope-from dan) Date: Tue, 24 Jul 2012 13:04:21 -0500 From: Dan Nelson To: dweimer@dweimer.net Message-ID: <20120724180421.GF38393@dan.emsphone.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-OS: FreeBSD 8.3-PRERELEASE User-Agent: Mutt/1.5.21 (2010-09-15) X-Virus-Scanned: clamav-milter 0.97.2 at email2.allantgroup.com X-Virus-Status: Clean X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.6 (email2.allantgroup.com [172.17.19.78]); Tue, 24 Jul 2012 13:04:22 -0500 (CDT) X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,T_RP_MATCHES_RCVD autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on email2.allantgroup.com X-Scanned-By: MIMEDefang 2.68 on 172.17.19.78 Cc: FreeBSD Questions Subject: Re: Disk Errors X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jul 2012 18:10:13 -0000 In the last episode (Jul 24), dweimer said: > I have three 1TB disks I use for backup, two of them are Western Digital > drives I bought specifically for this purpose. One is a Seagate drive > that came out of a barebones PC that I replaced with a couple smaller > drives in a stripe to gain performance. I use the drives in an external > SATA dock, using geom eli encryption, the western digital drives give me > no problems, but the seagate drive gives me a lot of the following errors > under load. > > ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=817755328 > ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=837397120 > ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=879786112 > ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=882931200 > ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=890542016 > ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=902767296 > ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=904071296 If you install the sysutils/smartmontools port, you can run "smartctl -x /dev/ad4" to dump the drive's SMART attribute table and error logs. Those should give you an indication of whether the drive is going bad. If the drive is logging those write errors in its internal log, then you know it's not a cabling issue. If it's not logging errors, I suppose you might have a loose SATA plug on the drive itself, which would explain why the problem follows the drive around. > dmesg info about the drive at connection time: > ad4: 953869MB at ata2-master UDMA100 SATA > 3Gb/s > > dmesg info about one of the western digital drives: > ad4: 953869MB at ata2-master UDMA100 > SATA 3Gb/s > > Before I scrap the drive I just wanted to see if anyone could either > say for sure its hardware, or if something else could possibly cause > this. I don't suspect the controller, cable or dock as the problems > would likely occur with the western Digital drives as well if one of > them were involved. -- Dan Nelson dnelson@allantgroup.com