From owner-freebsd-hackers Mon Feb 26 22:02:40 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA00184 for hackers-outgoing; Mon, 26 Feb 1996 22:02:40 -0800 (PST) Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id WAA00177 for ; Mon, 26 Feb 1996 22:02:38 -0800 (PST) Received: (from julian@localhost) by ref.tfs.com (8.7.3/8.6.9) id WAA14498; Mon, 26 Feb 1996 22:02:10 -0800 (PST) Message-Id: <199602270602.WAA14498@ref.tfs.com> Subject: Re: SCSI error code 83 and 84, medium errors To: taob@io.org (Brian Tao) Date: Mon, 26 Feb 1996 22:02:09 -0800 (PST) From: "JULIAN Elischer" Cc: freebsd-hackers@freebsd.org In-Reply-To: from "Brian Tao" at Feb 27, 96 00:06:09 am X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org Precedence: bulk The AWRE and ARRE bits only replace a block if it can recover the data. one way of doing this it to write to the block, because the drive figures (correctly) that if you are over-writing the block, the old data doesn't matter and can be considered recovered and deleted.. > > sd8(ncr2:2:0): error code 84 > sd8(ncr2:2:0): MEDIUM ERROR info:1af3b asc:14,1 Record not found field replaceable unit: 2 [...] > have gone away after a newfs (I tested it by dd'ing /dev/zero to a > file on that partition, filling it up, then reading the file back in). > The disk is a Seagate Medallist 1GB SCSI-2 drive, the last drive on > the third NCR53c810 controller. Is there anything I should be > worried about now? > keep a spare drive handy?