From owner-freebsd-questions@FreeBSD.ORG Fri Jan 21 02:02:42 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 93AA416A4CE for ; Fri, 21 Jan 2005 02:02:42 +0000 (GMT) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 32F3643D1D for ; Fri, 21 Jan 2005 02:02:42 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from [192.168.1.3] (pool-68-160-236-186.ny325.east.verizon.net [68.160.236.186]) by pi.codefab.com (8.12.11/8.12.11) with ESMTP id j0L22Y38041911 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 20 Jan 2005 21:02:36 -0500 (EST) Message-ID: <41F06325.1000001@mac.com> Date: Thu, 20 Jan 2005 21:04:21 -0500 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041217 X-Accept-Language: en-us, en MIME-Version: 1.0 To: David.Bear@asu.edu References: <20050121002113.GH6843@asu.edu> In-Reply-To: <20050121002113.GH6843@asu.edu> X-Enigmail-Version: 0.90.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=1.9 required=5.5 tests=AWL,RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL autolearn=disabled version=3.0.1 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on pi.codefab.com cc: freebsd-questions@freebsd.org Subject: Re: hard drive errors X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 02:02:42 -0000 David Bear wrote: > I am receiving the following errors on my hard drive. This appears to > affect some file in /var/log. My question is twofold. 1) shouldn't ufs > notice this sector as being unuseable and mark it offlimites? 2) if > not, is there a way to mark it so manually? Sure, by default, modern drives will notice and replace failing sectors using spare ones. The error message you are seeing very probably indicates that the drive has enough bad sectors that it has run out of spares and is going to completely fail very soon. Back up your data ASAP.... -- -Chuck