From owner-freebsd-scsi Mon Dec 2 3:38:24 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A7F9737B401 for ; Mon, 2 Dec 2002 03:38:22 -0800 (PST) Received: from rly-ip03.mx.aol.com (rly-ip03.mx.aol.com [64.12.138.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id A241F43EB2 for ; Mon, 2 Dec 2002 03:38:21 -0800 (PST) (envelope-from danielgeske@gmx.net) Received: from logs-mtc-ta.proxy.aol.com (logs-mtc-ta.proxy.aol.com [64.12.105.5]) by rly-ip03.mx.aol.com (v89.10) with ESMTP id RELAYIN1-1202063745; Mon, 02 Dec 2002 06:37:45 1900 Received: from Bowman (ACA23663.ipt.aol.com [172.162.54.99]) by logs-mtc-ta.proxy.aol.com (8.10.0/8.10.0) with ESMTP id gB2BbCq137675; Mon, 2 Dec 2002 06:37:13 -0500 (EST) From: "Daniel Geske" To: , "'Daniel Geske'" Cc: Subject: RE: fsck: PLEASE RERUN FSCK - does not fix problem :-( Date: Mon, 2 Dec 2002 12:34:15 +0100 Organization: - Message-ID: <000001c299f6$c7341900$a52efea9@Bowman> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal In-Reply-To: <20021130133520.GA83659@walton.maths.tcd.ie> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Apparently-From: BigOnLRAR@aol.com Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi David, I checked all my drives 1) if AWRE = 1 and ARRE = 1 Result: enabled on all 2) for defects Result: no defects on any drive. Now, the information on that drive is somewhat valuable to me. Interestingly, fsck shows me the number and overall size of the files the slice contains. So the files are still there. Can they be made accessible? How can I mount the filesystem without cleaning it, so I can copy the good files before wiping the slice? Normally, mount on a dirty disk gives "Operation not permitted". Is there a way to manually mark the fs clean? Greetings Daniel > -----Original Message----- > From: dwmalone@maths.tcd.ie [mailto:dwmalone@maths.tcd.ie] > Sent: Saturday, November 30, 2002 2:35 PM > To: Daniel Geske > Cc: 'Daniel Geske'; freebsd-scsi@FreeBSD.ORG > Subject: Re: fsck: PLEASE RERUN FSCK - does not fix problem :-( > > > On Sat, Nov 30, 2002 at 12:29:20PM +0100, Daniel Geske wrote: > > Thanks for your reply. Is there anything I can do like make > the disk > > skip the bad parts and keep on using the parts that are still good? > > As I unserstand it, the "MEDIUM ERROR" is the disk saying > that it tried to read the requested block, but couldn't. SCSI > Drives should be clever enough to be able to map these blocks > to spare blocks elsewhere on the disk, but this remapping can > only be done on a write. (This is usually enabeled by > default, but you may need to enable it with camcontrol.) > > So, if the information on the disk isn't too important you > can try rewriting the sectors on the disk to get the disk to > remap them. Something like "dd if=/dev/zero of=/dev/da1" > should work, but remember it will wipe the information on the disk. > > While this often works, if the disk is going bad you find > that it will quickly reach a state where you are loosing > blocks often enough that the disk is useless and you're > better off buying a new one. > > (On our busier disks we probably see one or two blocks go bad > a month, as shown by "camcontrol defects daX". Disks that are > going bad any faster than that should be backed up before they die...) > > David. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message