Path: utzoo!utgpu!watserv1!watmath!att!att!bu.edu!rpi!zaphod.mps.ohio-state.edu!usc!csun!mx.csun.edu!mrs
From: mrs@mx.csun.edu (Mike Stump)
Newsgroups: comp.sys.next
Subject: OD and fsck and read errors
Message-ID: <1990Oct30.025902.20285@csun.edu>
Date: 30 Oct 90 02:59:02 GMT
Sender: news@csun.edu (News Administrator)
Reply-To: mrs@ms.secs.csun.edu (Mike Stump)
Organization: School of Engineering and Computer Science, CSU Northridge
Lines: 24

Ok, I have a problem.  When I run fsck on my OD, it come back with:
** /dev/od0a

CANNOT READ: BLK 246672
CONTINUE?  yes

THE FOLLOWING SECTORS COULD NOT BE READ: 246672, 246673,
#

I can run it again and again, it does not ``continue.''  It leaves the
disk in the same state it found it.  I have run into this type of
problem before, and it worked the way I thought it should.  I can dd
the whole thing into /dev/null, and not get any read errors.  Help, I
don't have the raw disk space to dd the whole thing to a real disk,
and fsck it there.   I don't accually have a backup of it, as it is of
low importance, but I would like to recover most (if not all) of the disk.

Suggestiong?   Please e-mail any postings to me at mrs@ms.secs.csun.edu as
I do not read this newsgroup ``real'' often anymore.
--
If I can get mail to you via a legally registered fully qualified
domain name, you could be on Saturn for all I care.

		-- quote by Bob Sutterfield <bob@MorningStar.Com>