Date: Wed, 4 Dec 2002 00:51:29 +0100 From: "Daniel Geske" <danielgeske@gmx.net> To: "'Robert Johannes'" <rjohanne@piper.hamline.edu> Cc: <freebsd-scsi@FreeBSD.ORG> Subject: RE: fsck: PLEASE RERUN FSCK - does not fix problem :-( Message-ID: <003201c29b26$ee79d6e0$6ef9a8c0@Bowman> In-Reply-To: <Pine.GSO.4.44.0212021616470.28694-100000@mendeleev.hamline.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Dear Robert: Yes, I have now mounted the FS RO to copy my data. Thanks for your tip. Pretty good, I only lost six files. From here, I will continue to investigate the failure and try to fix the problem. Don't really have ideas on how to go on though... I'll have to do some reading before, I guess. Greetings Daniel > -----Original Message----- > From: Robert Johannes [mailto:rjohanne@piper.hamline.edu] > Sent: Monday, December 02, 2002 11:19 PM > To: Daniel Geske > Cc: freebsd-scsi@FreeBSD.ORG > Subject: RE: fsck: PLEASE RERUN FSCK - does not fix problem :-( > > > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?003201c29b26$ee79d6e0$6ef9a8c0>