Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!library.ucla.edu!news.mic.ucla.edu!unixg.ubc.ca!acs.ucalgary.ca!cpsc.ucalgary.ca!xenlink!fsa.ca!news
From: hpeyerl@fsa.ca (Herb Peyerl)
Subject: Re: bad144 problem?
Message-ID: <1993Aug24.155920.19271@fsa.ca>
Sender: news@fsa.ca
Nntp-Posting-Host: newt.fsa.ca
Organization: Little Lizard City
References: <25asop$6h6@wzv.win.tue.nl> <1993Aug23.174252.27909@crash>
Date: Tue, 24 Aug 1993 15:59:20 GMT
Lines: 41
In article <1993Aug23.174252.27909@crash> warelock@crash.cts.com (Tom Zacharoff) writes:
>Well if that's true then how do I fix these disk errors? My unix box crashes
>and locks up after giving me the message "Hard error reading fsbn 6913".
Depending on which wd.c you've got (in terms of age and whether you're
running NetBSD or Patchkit)... There was a bug in the barsoom wd.c that
would have caused that problem. I also recall some wierd interactions
between kern__physio.c and wd.c which seemed to cause such problems...
Basically your process was sleeping in diskwait and consequently if
it was your root disk; nothing else could get a disk request through
thereby giving the impression that the machine is locked up (because it
is sort of)... Chris's new kern_physio.c seemed to eradicate that problem
for the most part and then Theo's reset/timing changes seemed to eradicate
most of the rest of the problems...
I suggest you wait for NetBSD 0.9 and try it again or if you're in more
of a hurry (and are currently running 0.8ish) then get the latest
wd.c and kern_physio.c (note; only 1 underscore) and see if that helps..
>Badsect won't allow me to create any bad files to mask the disk errors. It
>says that the filesystem is busy. I'm trying to follow the steps in the
>man page for badsect to the letter.
hmmmm... try this again with a new wd.c...
>I also get an error like this: "Error: C:1 H:6 S:26" about 100-200 times
>and maybe (just maybe) then it boots up. I hope this new release of NetBSD
>will handle these things better.
Try rewriting your boot floppy... Looks like a bad disk or something.. My
floppy drive is ker-fucked in that it does that when I try to boot off
it... Basically I've found that if I lightly hold my finger on the fly-
wheel on the underside; then it decreases the rate at which the errors
occur... I'm too lazy to adjust the speed and far too cheap to buy
a new floppy drive... "Herb's house of horrible hardware"...
--
hpeyerl@novatel.cuc.ab.ca (actual but UUCP) | NovAtel Commnications Ltd.
hpeyerl@fsa.ca <faster> | <nothing I say matters anyway>
<NetBSD: A drinking group with a serious computing problem!>