CAN NOT READ BLK xxxxx is fsck
The Grey Wolf
greywolf at unisoft.UUCP
Fri Jun 28 12:32:23 AEST 1991
* In article <27262 at adm.brl.mil> ESANCHEZ at 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 at unisoft.com
More information about the Comp.unix.wizards
mailing list