Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!husc6!cmcl2!beta!hc!ames!acornrc!bob
From: bob@acornrc.UUCP (Bob Weissman)
Newsgroups: comp.unix.wizards,comp.unix.questions
Subject: How to recover from fsck "Cannot read block"?
Message-ID: <412@acornrc.UUCP>
Date: Mon, 13-Jul-87 18:15:11 EDT
Article-I.D.: acornrc.412
Posted: Mon Jul 13 18:15:11 1987
Date-Received: Wed, 15-Jul-87 00:52:18 EDT
Organization: Acorn Research Centre, Palo Alto, CA
Lines: 13
Keywords: disk, fsck, help!
Xref: mnetor comp.unix.wizards:3233 comp.unix.questions:3180

Argh!  fsck tells us "CANNOT READ: BLK 291344".  According to the fsck
documentation, this is a "shouldn't happen" kind of error.  Great.  It
also says to call for a guru.  None of our local gurus know what do do
about this.  We could run badsect and just give up on the block, but we
don't know how to trnslate a block number to a sector number.

Thanks for any assistance.

-- 
Bob Weissman
Internet:	bob@acornrc.UUCP
UUCP:		...!{ ames | decwrl | oliveb | apple }!acornrc!bob
Arpanet:	bob%acornrc.UUCP@AMES.ARPA