Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP
id AA6071 ; Mon, 04 Jan 93 17:20:49 EST
Path: sserve!manuel.anu.edu.au!munnari.oz.au!uunet!pipex!bnr.co.uk!uknet!axion!rtf.bt.co.uk!duplain
From: duplain@rtf.bt.co.uk (Andy Duplain)
Newsgroups: comp.unix.bsd
Subject: Re: [386BSD] corrupt files
Message-ID: <1993Jan6.132839.15621@rtf.bt.co.uk>
Date: 6 Jan 93 13:28:39 GMT
References: <56750001@acf3.NYU.EDU>
Organization: BT Customer Systems, Brighton, UK
Lines: 28
In article <56750001@acf3.NYU.EDU> chapman@acf3.NYU.EDU (Gary W. Chapman, , , ) writes:
>After downloading 386BSD from agate.berkeley.edu (and from another place
>as well), I get
>
>bin01.02 is corrupt
>bin01.03 is corrupt
>
>when doing 'extract'. What can I do?
They may not actually be corrupt! I had this problem (with different
bin01.xx files) and it was caused by the kernel from dist.fs not
reporting errors on my ESDI drives. I resolved this problem by getting
a kernel from a guy in Germany that reports these errors, relabelling
the disk's with bad144-style "sector forwarding" ('sf' in /etc/disktab)
then running "dd if=/dev/wd0c of=/dev/null bs=<bytesize of 1 cyl.>".
Write down the bad sector reports and then use bad144 to mark them as
bad. This takes a while (though it looks worse than it really is, as
the kernel reports the same bad sector about 5 times). Once you have
done this you can restart the installation.
BTW if you're stuck for a kernel, I can build you one that reports
errors to whatever spec you like.
--
Andy Duplain, BT Customer Systems, Brighton, UK. duplain@rtf.bt.co.uk
#define DISCLAIMER My views and opinions are my own, and not my company's