*BSD News Article 53342


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.uwa.edu.au!classic.iinet.com.au!swing.iinet.net.au!news.uoregon.edu!news.emf.net!overload.lbl.gov!lll-winken.llnl.gov!uwm.edu!homer.alpha.net!pacifier!usenet.eel.ufl.edu!newsfeed.internetmci.com!netnews.nwnet.net!news.u.washington.edu!olsenc
From: olsenc@kodiak.ee.washington.edu (Clint Olsen)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: A few very strange errors
Date: 26 Oct 1995 09:22:00 GMT
Organization: University of Washington, Seattle
Lines: 34
Message-ID: <46njvo$qn7@nntp5.u.washington.edu>
References: <cheema.814606457@nntp.msstate.edu>
NNTP-Posting-Host: smokey.ee.washington.edu

In article <cheema.814606457@nntp.msstate.edu>,
Mubashir Cheema <cheema@Jupiter.SPARCO.Com> wrote:
>I am running FreeBSD 2.1.0-950928-SNAP  on Zeos P-90 PCI
>with a 1.6GB Maxtor IDE Hard Drive and 64MB of memory. I 
>noticed a very strange happening a few minutes ago.  My machine
>rebooted itself automatically while I was in the middle editing 
>a file using vi.
>
>/var/log/messages says the following happened at that time :
>
>Oct 25 02:02:24 Moon /kernel: wd1a: wdintr: timeout waiting for
>status reading fsbn 738175 of 738174-738175 (wd1 bn 738175; cn 366 
>tn 5 sn 4)wd1: status d8<busy,seekdone,drq> error 0

This here likes like a disk I/O error.  The numbers appear to
refer to a block number, track number, and sector number.  Perhaps
you have a bad block?

Avoid Maxtor drives at all costs.  They are very troublesome.
Our 540 went out on an Intel machine.  It was not pretty.  It
pretty much trashed the whole system.

>Oct 21 05:44:14 Moon named[63]: Lame server on 'barton.net.au' 
>(in 'barton.NET.AU'?): [203.12.80.1].53 'ns.skeeve.net': learnt (A =203.12.80.1,NS=192.189.54.33)
>Oct 21 05:45:29 Moon named[63]: Lame server on 'webdreams.net.au' 
>(in 'webdreams.NET.AU'?): [203.12.80.1].53 'ns.skeeve.net': learnt (A=203.12.80.1,NS=192.65.182.30)

Dunno about this one.  Is this a name server machine?  If not, it
shouldn't be running named.  If you don't know what a name server
is, you definitely should not be running it :)

Good luck.

-Clint