Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rutgers!sri-spam!mordor!lll-tis!dgis!generous
From: generous@dgis.UUCP (Curtis Generous)
Newsgroups: comp.unix.wizards,comp.unix.questions
Subject: Re: How to recover from fsck "Cannot read block"?
Message-ID: <254@dgis.UUCP>
Date: Tue, 14-Jul-87 11:10:05 EDT
Article-I.D.: dgis.254
Posted: Tue Jul 14 11:10:05 1987
Date-Received: Thu, 16-Jul-87 05:42:49 EDT
References: <412@acornrc.UUCP>
Reply-To: generous@dgis.UUCP (Curtis Generous)
Organization: Defense Gateway Info. System, Alexandria, VA
Lines: 31
Keywords: disk, fsck, help!
Xref: mnetor comp.unix.wizards:3242 comp.unix.questions:3192

In article <412@acornrc.UUCP> bob@acornrc.UUCP (Bob Weissman) writes:
>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.
>-- 
>Bob Weissman
>Internet:	bob@acornrc.UUCP
>UUCP:		...!{ ames | decwrl | oliveb | apple }!acornrc!bob
>Arpanet:	bob%acornrc.UUCP@AMES.ARPA

How about providing a bit more background information on this problem, such as:
 
	[] Host type (i.e. VAX 11/780, PDP, etc...)
	[] OS type (i.e. UNIX 4.2BSD, Ultrix, etc...)
	[] Disk drive type (i.e. 9766, eagle, etc...)
	[] Controller type.
	[] Driver used.
	[] Partition in which problem occurs (slice a, b, c, etc..)

		   etc...

We have experienced a similar 'symptom' here, but without further info, 
cannot say if these problems are related.

--curtis
Curtis C. Generous
Lawrence Livermore National Labs
ARPA: generous@lll-tis.ARPA
UUCP: {seismo,vrdxhq}!dgis!generous