Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!yarrina.connect.com.au!classic.iinet.com.au!news.uoknor.edu!news.ecn.uoknor.edu!paladin.american.edu!gatech!news.sprintlink.net!hookup!noc.tor.hookup.net!noc.tor.hookup.net!not-for-mail
From: gschmidt@noc.tor.hookup.net (Greg Schmidt)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Utility to check for bad sectors?
Date: 21 May 1995 16:02:18 -0400
Organization: HookUp Communication Corporation, Oakville, Ontario, CANADA
Lines: 50
Message-ID: <3po68a$i5l@noc.tor.hookup.net>
References: <3pm5q5$mct@noc.tor.hookup.net> <3pmvcr$2m9@agate.berkeley.edu> <3pnlel$ar@iii1.iii.net>
NNTP-Posting-Host: noc.tor.hookup.net
In article <3pnlel$ar@iii1.iii.net>, HD Associates <hdslip@iii1.iii.net> wrote:
>In article <3pmvcr$2m9@agate.berkeley.edu>,
>Jordan K. Hubbard <jkh@violet.berkeley.edu> wrote:
>>In article <3pm5q5$mct@noc.tor.hookup.net>,
>>Greg Schmidt <gschmidt@noc.tor.hookup.net> wrote:
>>>Oh, here's a couple of lines from the messages log which may be useful:
>>> kernel: fd0: Seek to cyl 0, but not really there (ST3 = 20<drdy>)
>>> kernel: fd0: recal failed ST0 70<abnrml,seek_cmplt,equ_chck> cyl 0
>>
>>That's your floppy drive. There's nothing wrong with your hard disk.. :-)
Ok, that was a red herring (it was late). I still think there's something
wrong with my hard disk. I will describe the symptoms, since there is no
log file entry that shows them.
First off, I had two directories which could not be removed. A listing of
the directory turned up nothing ("ls -a"), but trying to remove it ("rmdir")
gave me the old "directory not empty" message. "rm -rf" gave the same result.
There was also something about ". not valid" or some such. I did finally get
rid of them with "clri" and a couple of "fsck"s.
Now, I am having a different problem. I have a gzipped file (call it x.gz).
I can zcat it, with correct results. I can redirect the output from this to
a file, so that both the compressed and uncompressed versions are present.
I can also gunzip the file. However, when I try to re-gzip the file, the
result is something like 27 bytes long (just a header), and of course the
uncompressed version is gone. This kind of lossy data compression is less
than ideal...
>"What color is your Gatweay 2000?"
>
>This looks like the "2.0R boot floppy bug" which was fixed in all later snaps.
>It is present on the Micronics motherboard used in some Gateways, as well
>as other systems. If you have a spare floppy controller then disable the
>motherboard one and install, or get a newer boot snap.
I don't have a Gateway 2000. I have a 386 clone from 1990. The manual
doesn't say who the motherboard is made by (yes, I bought the cheapest one
I could find at the time). The BIOS is AMI, if that helps. I could open it
up, but I don't know if that would help.
The boot snap I have is whatever was current at the beginning of April. I'm
not sure of the version (and I can't check right now, as I am posting this
from DOS since I haven't been able to get cu or kermit working properly yet).
------------------------------------------------------------------------------
Greg Schmidt (gschmidt@hookup.net / hookup.net!large!gregs)
"And lo, it shall come to pass, that when the user typeth 'ls', a directory
listing shall spring forth upon the standard output, and its form shall be
governed by options, and the options shall be as follows..."
- excerpt from "The Gospel According to POSIX, Revision 2.0"