*BSD News Article 26768


Return to BSD News archive

Newsgroups: comp.os.386bsd.questions
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!decwrl!decwrl!netcomsv!delfin.com!mike
From: mike@delfin.com (Mike Wlodarczyk)
Subject: NetBSD-0.9 install problem
Message-ID: <1994Feb1.012707.3649@delfin.com>
Summary: Can't install on WD1007/Maxtor combo.
Keywords: NetBSD WD Maxtor MXT
Organization: Delfin Systems
X-Newsreader: TIN [version 1.2 PL2]
Date: Tue, 1 Feb 1994 01:27:07 GMT
Lines: 27

I recently tried to install NetBSD-0.9 on my 486 but ran into a fatal problem.
This machine has a WD1007-SE2 ESDI controller and a MXT-8670E ESDI drive.

The problem is that I get "wdc0: extra interrupt" messages during execution
of 'disklabel' and 'newfs', which doesn't appear to cause problems until I
reboot from the floppies. In other words, these programs run, filesystems
appear to be created, and the files on the inst1 floppy appear to get copied
to the hard disk. But, when rebooting from the kcopy disk, the wd driver
fails to detect a label on the hard drive and because of this can't check or
mount any filesystems there. So copying a kernel to the hard disk fails, too.

I've fiddled around with whatever I could think of, including manually
running disklabel and newfs, but haven't been able to get anything to work.

I also tried installing FreeBSD, but while it didn't emit any
"extra interrupt" messages, it did mark a dozen or so complete *tracks* as
bad, before it failed making filesystems and then halted itself.

I'll also point out that I run a commercial UNIX on this same machine and
it occasionally gets a "HD: interrupt with no request queued" message on 
bootup, but runs fine otherwise (and has for three years). So perhaps there's
a hardware problem somewhere, but it isn't a fatal one.

Any suggestions ?
-- 
Mike Wlodarczyk ............................... "A mind is a thing to waste."
mike@delfin.com ...................................... - The OverLoad Himself