*BSD News Article 65475


Return to BSD News archive

Newsgroups: comp.unix.bsd.freebsd.misc
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!news.ecn.uoknor.edu!paladin.american.edu!gatech!swrinde!elroy.jpl.nasa.gov!lll-winken.llnl.gov!fnnews.fnal.gov!unixhub!argus.SLAC.Stanford.EDU!kls
From: kls@argus.SLAC.Stanford.EDU (Karl L. Swartz)
Subject: "device not configured" during install
Message-ID: <DpLz5D.G64@unixhub.SLAC.Stanford.EDU>
Sender: news@unixhub.SLAC.Stanford.EDU
Organization: Stanford Linear Accelerator Center
Date: Tue, 9 Apr 1996 18:53:37 GMT
Lines: 28

I'm trying to install a FreeBSD 2.1 system (off the CDROM) but can't
get the disk configuration onto the disk.  The salient bits of hard-
ware include an AMD 486DX4-100 CPU on a MTech PCI motherboard, an
Adaptec 2940 SCSI controller, and a Seagate ST41340N disk.  The CDROM
is on another system (I'll be reading it over the net) so there are
no other devices on the SCSI bus.

When I boot from the floppy (a floppy that I've used successfully to
load several other FreeBSD systems) it sees disk and reads all of its
geometry and whatnot just fine, so there don't appear to be any major
SCSI problems.

However, when the system tries to write to the disk, it pops up a
window saying it can't swap to /dev/sd0s1b because the device is not
configured.  When it tries to run newfs, the disk chatters a bit and
then another window pops up, telling me that newfs failed and I think
it again says something about a device not being configured.

The only thing I could think of was that the drive might be write-
protected, but I checked that and it isn't.

Any clues?

-- 
Karl Swartz		|INet	kls@unixhub.slac.stanford.edu
SLAC Computing Services	|	   or kls@chicago.com
1-415/926-3630		|UUCP	uunet!lll-winken!unixhub!kls  -or-  ditka!kls
(SLAC and the US Dept. of Energy don't necessarily agree with my opinions.)