From owner-freebsd-questions@FreeBSD.ORG Wed Jun 6 16:43:29 2007 Return-Path: X-Original-To: questions@freebsd.org 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 314B316A478 for ; Wed, 6 Jun 2007 16:43:29 +0000 (UTC) (envelope-from lists@stringsutils.com) Received: from zoraida.natserv.net (p65-147.acedsl.com [66.114.65.147]) by mx1.freebsd.org (Postfix) with ESMTP id 65B4413C4C3 for ; Wed, 6 Jun 2007 16:43:28 +0000 (UTC) (envelope-from lists@stringsutils.com) Received: by zoraida.natserv.net (Postfix, from userid 58) id 8B3B1C2F2; Wed, 6 Jun 2007 12:22:40 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on zoraida.natserv.net X-Spam-Level: X-Spam-Status: No, score=-1.4 required=4.0 tests=ALL_TRUSTED, DK_POLICY_SIGNSOME autolearn=disabled version=3.1.8 X-Spam-Report: * 0.0 DK_POLICY_SIGNSOME Domain Keys: policy says domain signs some mails * -1.4 ALL_TRUSTED Passed through trusted hosts only via SMTP Received: from 35st.simplicato.com (static-71-249-233-130.nycmny.east.verizon.net [71.249.233.130]) by zoraida.natserv.net (Postfix) with ESMTP id B2327C2E3; Wed, 6 Jun 2007 12:22:37 -0400 (EDT) References: <52060.69.129.174.18.1176828969.squirrel@email.polands.org> <20070417130653.a07b6c1c.wmoran@potentialtech.com> Message-ID: X-Mailer: http://www.courier-mta.org/cone/ From: Francisco Reyes To: Bill Moran Date: Wed, 06 Jun 2007 12:22:37 -0400 Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="US-ASCII" Content-Disposition: inline Content-Transfer-Encoding: 7bit Cc: Doug Poland , questions@freebsd.org Subject: Re: Exercising ATA disks in hopes of revealing 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: Wed, 06 Jun 2007 16:43:29 -0000 Bill Moran writes: > Check with the vendors, though. Many drive manufacturers have utilities > you can download specifically to check their drives. If the drives are somewhat recent you can try using SMART to check them. In particular you can use the smartmontools port. You may need to enable SMART on the motherboard. SMART = Self-Monitoring, Analysis, and Reporting Technology (S.M.A.R.T.) http://en.wikipedia.org/wiki/Self-Monitoring%2C_Analysis%2C_and_Reporting_Te chnology Syntax is smartctl -t short /dev/ad0[1] smartctl -t long /dev/ad0[2] smartctl -l selftest /dev/ad0[3] [1] If the short fails you know there are problems. Still no guarantee. Still worth to do quick tests first. [2] If it fails, there is a good chance the drive has some sort of problems. [3] Use that to check the result.