ESANCHEZ@udlapvms.pue.udlap.mx (06/20/91)
---------------------------------------------------------------------------- EnDate sent: 20-JUN-1991 09:19:32 ---------------------------------------------------------------------------- Enrique Sanchez Universidad de las Americas esanchez@udlapvms (Bitnet) Depto. de Redes y Telecom. esanchez@udlapvms.pue.udlap.mx (Internet) Sta. Catarina Martir root@cca.pue.udlap.mx Cholula Puebla (22) 47-43-21 ---------------------------------------------------------------------------- From: IN%"Unix-Wizards@BRL.MIL" 18-JUN-1991 14:04:06.61 To: Enrique Sanchez Lara <ESANCHEZ@UDLAPVMS.PUE.UDLAP.MX> CC: Subj: CAN NOT READ BLK xxxxx is fsck Received: from Jnet-Daemon by UDLAPVMS.PUE.UDLAP.MX; Tue, 18 Jun 91 13:57 CST Received: From TECMTYVM(MAILER) by UDLAPVMS with Jnet id 6616 for ESANCHEZ@UDLAPVMS; Tue, 18 Jun 1991 13:57 CST Received: by TECMTYVM (Mailer R2.07) id 6615; Tue, 18 Jun 91 13:54:41 CST Date: Tue, 18 Jun 1991 15:10:11 EDT From: Marshall Feldman <RLN101@URIACC.BITNET> Subject: CAN NOT READ BLK xxxxx is fsck Sender: Unix-Wizards Mailing List <UNIX-WIZ@NDSUVM1.BITNET> To: Enrique Sanchez Lara <ESANCHEZ@UDLAPVMS.PUE.UDLAP.MX> Reply-to: Unix-Wizards@BRL.MIL Message-id: <5B033125C29F200126@UDLAPVMS.PUE.UDLAP.MX> X-Envelope-to: ESANCHEZ 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? I am running SCO OpenDesktop Unix V 3.2 with an Ultrastor controller and a micropolis ESDI-1647-7 (150 MB) fixed disk). Marsh Feldman Community Planning 204 Rodman Hall University of Rhode Island Kingston, RI 02881-0815 (rln101 @ uriacc.uri.edu) 401/792-2248 Just answer "yes" to salvage question and that's all. At least, I have 21 Sparcs and sometimes I got that messages ( When the light goes down and the machines stops without the "shutdown") and I answer yes to any message I got. Only one time a message like "Inode Truncated" I answered "no" to clear and reboot the machine, the I got the same message and I answered "yes" and the machine crashed forever and I had to re-install the operating system. If you answer "no" to messages like "salvage", "clear", "fix", you will obtain the same message the next time. Good luck and don't worry ..... ---------------------------------------------------------------------------- En
adf@crosfield.co.uk (alex france) (06/24/91)
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, >I have 21 Sparcs and sometimes I got that messages ( When the light >goes down and the machines stops without the "shutdown") and I answer yes > ........ Seems to me like the man has already tried this, with no success. I have found, in the past, that it is possible to get real hard disk errors on SCSI disks which leave unreadable (but writeable) disk sectors. The controller thinks it wrote the block OK, but 5 minutes later you cannot read it. So, endless typing of 'Y' to fsck does not improve matters. Also, some device drivers do not automatically perform 'grown defect mapping' on SCSI disks. Given the large number of blocks it thinks are missing from the free list, my guess would be that you are losing an inode block, although you don't say you are getting any messages about missing files. Anyway, and unfortunately, the only way to resurrect such a problem is to find something that will scan your disk and add grown defects (this remaps unreadable sectors onto spare sectors in the same cylinder). Usually this is found within disk diagnostics or formatter programs, but I don't know where this might be in SCO Unix (anyone else?). You may find that you have to do a full reformat and surface scan on the disk to clear the problem - a long and painfull business if you have to back everything up first. Hope this helps. Alex France, Crosfield Electronics, | Phone: +44 442 230000 xt.3541 Hemel Hempstead, HP2 7RH, England. | Fax: +44 442 232301 adf@crosfield.co.uk or mcsun!cel!adf@uunet.uu.net
greywolf@unisoft.UUCP (The Grey Wolf) (06/28/91)
* 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