From owner-freebsd-questions@FreeBSD.ORG Sun May 11 17:38:46 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7E2797F0 for ; Sun, 11 May 2014 17:38:46 +0000 (UTC) Received: from outbound-queue-1.mail.thdo.gradwell.net (outbound-queue-1.mail.thdo.gradwell.net [212.11.70.34]) by mx1.freebsd.org (Postfix) with ESMTP id 4281225B0 for ; Sun, 11 May 2014 17:38:45 +0000 (UTC) Received: from outbound-edge-2.mail.thdo.gradwell.net (bonnie.gradwell.net [212.11.70.2]) by outbound-queue-1.mail.thdo.gradwell.net (Postfix) with ESMTP id 78C0E224F3 for ; Sun, 11 May 2014 18:38:37 +0100 (BST) Received: from cpc7-jarr12-2-0-cust882.16-2.cable.virginm.net (HELO amd.asgard.uk) (92.238.71.115) (smtp-auth username fbsd%pop3.dgmm.net, mechanism plain) by outbound-edge-2.mail.thdo.gradwell.net (qpsmtpd/0.83) with ESMTPA; Sun, 11 May 2014 18:38:37 +0100 From: Dave To: freebsd-questions@freebsd.org Subject: Re: Disk errors Date: Sun, 11 May 2014 18:38:33 +0100 Message-ID: <2475443.JNnX4JR3n2@amd.asgard.uk> User-Agent: KMail/4.12.4 (FreeBSD/9.2-RELEASE-p5; KDE/4.12.5; amd64; ; ) In-Reply-To: <1399459712.98648.YahooMailNeo@web126202.mail.ne1.yahoo.com> References: <1399459712.98648.YahooMailNeo@web126202.mail.ne1.yahoo.com> MIME-Version: 1.0 X-Gradwell-MongoId: 536fb59d.b4b5-1b67-2 X-Gradwell-Auth-Method: mailbox X-Gradwell-Auth-Credentials: fbsd@pop3.dgmm.net Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 May 2014 17:38:46 -0000 On Wednesday 07 May 2014 03:48:32 Leonardo M.=20 Ram=E9 via freebsd-questions wrote: > 199 UDMA_CRC_Error_Count 0x0032 200 200 =20 000 Old_age =20 > Always - 4455 CRC error counts usually indicate bad SATA cables IME. It could be the drive or the system board, but that's far=20 less likely in my experience than a bad data cable.