From owner-freebsd-questions@FreeBSD.ORG Tue Nov 23 03:45:54 2004 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 49F0016A4CE for ; Tue, 23 Nov 2004 03:45:54 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id E62AB43D39 for ; Tue, 23 Nov 2004 03:45:53 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.1) id iAN3jr1i080416; Mon, 22 Nov 2004 21:45:53 -0600 (CST) (envelope-from dan) Date: Mon, 22 Nov 2004 21:45:53 -0600 From: Dan Nelson To: "Ryan J. Cavicchioni" Message-ID: <20041123034553.GB48882@dan.emsphone.com> References: <41A2A7B2.4000601@confabulator.net> <20041123030351.GA31803@dan.emsphone.com> <41A2CCFA.4000408@confabulator.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41A2CCFA.4000408@confabulator.net> X-OS: FreeBSD 5.3-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: freebsd-questions@freebsd.org Subject: Re: SCSI Hard drive "MEDIUM ERROR" 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: Tue, 23 Nov 2004 03:45:54 -0000 In the last episode (Nov 22), Ryan J. Cavicchioni said: > AWRE (Auto Write Reallocation Enbld): 1 > ARRE (Auto Read Reallocation Enbld): 1 > TB (Transfer Block): 0 > RC (Read Continuous): 0 > EER (Enable Early Recovery): 0 > PER (Post Error): 0 > DTE (Disable Transfer on Error): 0 > Read Retry Count: 255 > Write Retry Count: 255 > > It seems to be enabled. Is there anything else that I can do? ARRE only works if the data is recoverable, and AWRE only works on writes, so if the bad block has already been assigned to a file, it's difficult to fix unless you know the filename. You can try doing a "tar xvfl /dev/null /mountpoint" and see where it stops, then dd /dev/zero onto the file to force a write. Another way is to get the drive to check all the blocks on the disk by running a Verify operation from your SCSI BIOS. -- Dan Nelson dnelson@allantgroup.com