Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!ll-xn!cit-vax!mangler
From: mangler@cit-vax.Caltech.Edu (System Mangler)
Newsgroups: comp.unix.wizards,comp.unix.questions
Subject: Re: How to recover from fsck "Cannot read block"?
Message-ID: <3225@cit-vax.Caltech.Edu>
Date: Mon, 13-Jul-87 22:35:25 EDT
Article-I.D.: cit-vax.3225
Posted: Mon Jul 13 22:35:25 1987
Date-Received: Wed, 15-Jul-87 02:25:58 EDT
References: <412@acornrc.UUCP> <3224@cit-vax.Caltech.Edu>
Organization: California Institute of Technology
Lines: 14
Keywords: disk, fsck, help!
Summary: fsck the raw device
Xref: mnetor comp.unix.wizards:3237 comp.unix.questions:3185

In article <412@acornrc.UUCP> bob@acornrc.UUCP (Bob Weissman) writes:
>Argh!	fsck tells us "CANNOT READ: BLK 291344".  According to the fsck

On a 4.[23] BSD VAX, that number is the last block-device block on a
standard "h" partition of 291346 sectors.  There aren't BLKDEV_IOSIZE
bytes left in the partition, so you get an error.  Make sure that you
fsck the raw device, not the block device.

In article <3224@cit-vax.Caltech.Edu>, sns@tybalt.caltech.edu (Samuel N. Southard) writes:
> I'm not really a guru,

Agreed.  Please accept my apologies for the misinformation from our site.

Don Speck   speck@vlsi.caltech.edu  {seismo,rutgers}!cit-vax!speck