Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!elroy.jpl.nasa.gov!lll-winken!uunet!unisoft!greywolf
From: greywolf@unisoft.UUCP (The Grey Wolf)
Newsgroups: comp.unix.wizards
Subject: Re: CAN NOT READ BLK xxxxx is fsck
Message-ID: <3541@unisoft.UUCP>
Date: 28 Jun 91 02:32:23 GMT
References: <27262@adm.brl.mil> <10387@suns7.crosfield.co.uk>
Reply-To: greywolf@unisoft.UUCP (The Grey Wolf)
Organization: Foo Bar and Grill
Lines: 25


 * In article <27262@adm.brl.mil> ESANCHEZ@udlapvms.pue.udlap.mx writes:
 * 
 * >When doing  "fsck /dev/rusr1", I get three messages like the following:
 * >   CAN NOT READ BLK 31993
 * >Two occur in Phase 1, then in Phase 5 I get another CAN NOT READ message,
 * >followed by a message saying
 * >   4437 BLK(S) MISSING
 * >   BAD FREE LIST
 * >   SALVAGE? y <---------
 * > 
 * >No matter how much I try running fsck, I keep getting these errors.  Does
 * >anyone out there have suggestions how to fix this?
 * > 
 * 	Just answer "yes" to salvage question and that's all. At least,
 *

This almost looks like a controller problem I once had; check the integrity
of your controller.  You may also have to do a backup, surface scan and
reformat of your drive.  Given that it's SCO unix, you might have a more
difficult time of this than, say, SunOS.

-- 
# "Religion is a weapon invented by the sheep to keep the wolves in line."
# greywolf@unisoft.com