Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!zaphod.mps.ohio-state.edu!darwin.sura.net!sgiblab!news.cs.indiana.edu!mikes@cs.indiana.edu From: "Michael Squires" <mikes@cs.indiana.edu> Subject: Re: Installation.. arghhhhhh!!! Message-ID: <1993Mar19.121721.20041@news.cs.indiana.edu> Organization: Indiana University Computer Science, Bloomington References: <1993Mar9.012445.555@antioc.antioch.edu> <1obhmgINN6rv@hrd769.brooks.af.mil> Date: Fri, 19 Mar 1993 12:17:12 -0500 Lines: 27 In article <1obhmgINN6rv@hrd769.brooks.af.mil> burgess@hrd769.brooks.af.mil (Dave Burgess) writes: >In article <1993Mar9.012445.555@antioc.antioch.edu> baker@antioc.antioch.edu writes: >>BSD is driving me crazy. Everytime I try to go and install the >>bin01.* disks I find that my file bin01.41 and bin01.56 are >>corrupted. Has anyone had these problems before??? I have I had similar problems with an ESDI drive with lots of bad spots. One workaround if there are not too many bad spots is to rename the corrupted files to bad.01, bad.02, etc, and then copy the files again. In my case I had to bring up 386 BSD with bad144 sector remapping before the disk would work. If you are using the 0.1 pl 0 boot disks go get the dist.fs and fixit.fs disks with the 0.1 or 0.2 patchkits installed, this at least turns on the WD error reporting. (Sytem uses WD1007V with an old Miniscribe 660MB ESDI, works fine with home-brew disktab entry and bad144 remapping turned on). I've also seen problems with tar archives created using ftp under 386 BSD. The same spot will be corrupted repeatedly. This seems to happen in large files. -- Mike Squires (mikes@cs.indiana.edu) 812 855 3974 (w) 812 333 6564 (h) mikes@cs.indiana.edu 546 N Park Ridge Rd., Bloomington, IN 47408