From owner-freebsd-questions  Mon Oct  6 11:23:58 1997
Return-Path: <owner-freebsd-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id LAA16908
          for questions-outgoing; Mon, 6 Oct 1997 11:23:58 -0700 (PDT)
          (envelope-from owner-freebsd-questions)
Received: from dan.emsphone.com (dan@dan.emsphone.com [199.67.51.101])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA16898
          for <freebsd-questions@FreeBSD.ORG>; Mon, 6 Oct 1997 11:23:54 -0700 (PDT)
          (envelope-from dan@dan.emsphone.com)
Received: (from dan@localhost)
	by dan.emsphone.com (8.8.6/8.8.6) id NAA25271;
	Mon, 6 Oct 1997 13:17:32 -0500 (CDT)
Message-ID: <19971006131732.39400@emsphone.com>
Date: Mon, 6 Oct 1997 13:17:32 -0500
From: Dan Nelson <dnelson@emsphone.com>
To: Leif Neland <leifn@swimsuit.roskildebc.dk>
Cc: freebsd-questions@FreeBSD.ORG
Subject: Re: can't find 3. scsi-disk.
References: <006_9710061212@swimsuit.roskildebc.dk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.82e
In-Reply-To: <006_9710061212@swimsuit.roskildebc.dk>; from "Leif Neland" on Mon Oct  6 08:47:29 GMT 1997
X-OS: FreeBSD 2.2-970701-RELENG
Sender: owner-freebsd-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

In the last episode (Oct 06), Leif Neland said:
> My system (486) runs dos nicely with an ancient adaptec (with bios,
> but apearently without a modelnumber). The adapter installs the first
> two drives as C: and D: and I must use an ASPI-driver for the 3.
> drive. Works ok.
> 
> Now I want to install FBSD on the 3. drive, but when I boot (from
> dos, fbsdboot.exe and kernel from install-floppy) the 3. disk is not
> found. It comes up as:
>
> (aha0:3:0)) "unknown unknown ?????" type 13 fixed scsi 0
> uk0(aha:3:0): unknown
> 
> Any clues why?
> 
> In dos it gets reported as "Maxtor xt-3280"

The problem is that your disk doesn't claim to be either SCSI-1 or
SCSI-2, and the scsi driver won't assign a device it can't get a
version on.  My 4-year-old Fujitsu MO drive does the same thing, even
though the documentation claims it's SCSI-2 compliant.

My solution was to edit /sys/scsi/scsiconf.c (search for SID_ANSII),
and just make the
			if ((inqbuf->version & SID_ANSII) > 0) {
line say
			if (1) {
. That'll force it to assign devices with no SCSI version.

	-Dan Nelson
	dnelson@emsphone.com