Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!gatech!bloom-beacon!husc6!cmcl2!beta!hc!ames!acornrc!bob
From: bob@acornrc.UUCP (Bob Weissman)
Newsgroups: comp.unix.wizards,comp.unix.questions
Subject: Re: How to recover from fsck "Cannot read block"?
Message-ID: <415@acornrc.UUCP>
Date: Tue, 14-Jul-87 13:09:51 EDT
Article-I.D.: acornrc.415
Posted: Tue Jul 14 13:09:51 1987
Date-Received: Thu, 16-Jul-87 06:20:26 EDT
References: <412@acornrc.UUCP> <254@dgis.UUCP>
Organization: Acorn Research Centre, Palo Alto, CA
Lines: 34
Keywords: disk, fsck, help!
Summary: More specifics
Xref: mnetor comp.unix.wizards:3244 comp.unix.questions:3193

In article <254@dgis.UUCP>, generous@dgis.UUCP (Curtis Generous) writes:
> 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.
> 
> 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..)

Yes, I should have been more specific.
	Host: 		VAX 11/750
	OS:		Unix 4.2bsd
	Disk:		Eagle
	Controller: 	?  I dunno about these.
	Driver:		?
	Partition:	/dev/hp1h

df output:
Filesystem    kbytes    used   avail capacity  Mounted on
/dev/hp1h     140564  117733    8774    93%    /util


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