Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!ut-sally!utah-cs!utah-gr!hoosier!mjb From: mjb%hoosier.uucp@utah-gr.UUCP (Mark J. Bradakis) Newsgroups: comp.unix.wizards,comp.unix.questions Subject: Re: How to recover from fsck "Cannot read block"? Message-ID: <2084@utah-gr.UUCP> Date: Tue, 14-Jul-87 14:49:19 EDT Article-I.D.: utah-gr.2084 Posted: Tue Jul 14 14:49:19 1987 Date-Received: Thu, 16-Jul-87 06:40:35 EDT References: <412@acornrc.UUCP> <254@dgis.UUCP> Sender: news@utah-gr.UUCP Reply-To: mjb%hoosier.UUCP@utah-gr.UUCP (Mark J. Bradakis) Organization: Univ of Utah CS Dept Lines: 31 Keywords: disk, fsck, help! Xref: mnetor comp.unix.wizards:3245 comp.unix.questions:3194 In article <412@acornrc.UUCP> bob@acornrc.UUCP (Bob Weissman) writes: >Argh! fsck tells us "CANNOT READ: BLK 291344". According to the fsck >... Why, just last week I had the same problem. This was on an HP 9000 model 350, with a 7945 disk drive. Under 5.22 HP-UX, I got: CANNOT READ: BLK 123456 (or some such) CONTINUE? I answered yes, then got CANNOT SEEK: BLK 123456 CONTINUE? I answered yes again, and continued the fsck. It turned out that some of the disk was saved, but a few dirs (unreferenced dir, name=/bin remove?) disappeared. I had originally thought it was a hardware error, but now the disk is fine. Of course, after I finally got what I could from the disk I did a reinit and built a new filesystem on it just in case. The disk works fine now. mjb. --------------- mjb%hoosier@cs.utah.edu "I take this medicine as prescribed, I'll sleep when I'm dead. It don't matter if I get a little tired, I'll sleep when I'm dead." Warren "Excitable" Zevon