From owner-freebsd-scsi Mon Dec 2 14:20:27 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 45B8537B407 for ; Mon, 2 Dec 2002 14:20:24 -0800 (PST) Received: from russell.hamline.edu (russell.hamline.edu [138.192.24.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id 52F7143EEC for ; Mon, 2 Dec 2002 14:20:17 -0800 (PST) (envelope-from rjohanne@piper.hamline.edu) Received: from piper.hamline.edu (piper.hamline.edu [138.192.2.101]) by russell.hamline.edu (8.11.6+Sun/8.11.6) with ESMTP id gB2MJxD04734; Mon, 2 Dec 2002 16:20:00 -0600 (CST) Received: from mendeleev.hamline.edu (mendeleev [138.192.2.109]) by piper.hamline.edu (8.12.6/8.12.6) with ESMTP id gB2MK4aP006937; Mon, 2 Dec 2002 16:20:05 -0600 (CST) Received: from localhost (rjohanne@localhost) by mendeleev.hamline.edu (8.9.1b+Sun/8.9.1) with ESMTP id QAA28697; Mon, 2 Dec 2002 16:18:34 -0600 (CST) X-Authentication-Warning: mendeleev.hamline.edu: rjohanne owned process doing -bs Date: Mon, 2 Dec 2002 16:18:34 -0600 (CST) From: Robert Johannes X-X-Sender: rjohanne@mendeleev.hamline.edu To: Daniel Geske Cc: freebsd-scsi@FreeBSD.ORG Subject: RE: fsck: PLEASE RERUN FSCK - does not fix problem :-( In-Reply-To: <000001c299f6$c7341900$a52efea9@Bowman> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 Have you tried mounting it read-only? That's worked for me lately when I couldn't mount a filesystem because it was 'dirty'. mount -o ro /dev/dxxxx /mnt robert On Mon, 2 Dec 2002, Daniel Geske wrote: > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message