From owner-freebsd-stable Fri Jan 29 20:39:16 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA12301 for freebsd-stable-outgoing; Fri, 29 Jan 1999 20:39:16 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from bogon.net (206-100-6-26.bayarea.net [206.100.6.26]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA12293 for ; Fri, 29 Jan 1999 20:39:15 -0800 (PST) (envelope-from wespop@bogon.net) Received: from kryten.bogon.net (kryten.bogon.net [10.0.0.2]) by bogon.net (8.9.2/8.9.1) with SMTP id UAA06541; Fri, 29 Jan 1999 20:39:12 -0800 (PST) (envelope-from wespop@bogon.net) Message-Id: <4.1.19990129203522.00a832a0@mail.bogon.net> Message-Id: <4.1.19990129203522.00a832a0@mail.bogon.net> X-Sender: wespop@mail.bogon.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Fri, 29 Jan 1999 20:40:14 -0800 To: Wes Santee , freebsd-stable@FreeBSD.ORG From: Wes Santee Subject: Solution: Re: 2nd SCSI drive not detected. Why? In-Reply-To: <199901291959.LAA01704@bogon.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just FYI. I'm not sure which or both of these did the trick, but after doing the following, the drive was detected by the OS: 1) Turn off SCAM on the adapter. 2) Manually set the SCSI ID on the new drive to 1 (was being SCAM'd to ID 15). The termination settings, as it turns out, were all correct. Thanks for your suggestions everyone. The original message is listed below for reference. I didn't mention SCAM because I didn't think it was a big deal. Cheers, -Wes ---------- Hi all. I wanted to kill 2 birds with one stone last night so I upgraded my 3.0-release to 3.0-stable and installed a new hard drive. The stable upgrade was fairly smooth, but adding the new drive didn't go so well. I'm not sure if this is a -stable thing, or I need to do something else. The drives are hooked up to an Adaptec 2940UW. The main drive is hooked up to the SCSI-2 (50-pin) internal connector at SCSI ID 0, while the new drive is a Seagate 9.1GB SCSI-3 hooked up to the 68-pin internal connector at SCSI ID 15. The controller detects the drive just fine. The OS, on the other hand, doesn't. While FreeBSD is booting it detects that a cable is present on both internal connectors. It also detects that there are 3 BIOS drives (floppy, both SCSI drives), but it fails to actually map da1 to the drive itself. Is there something else I need to be doing here to get the OS to recognize the drive correctly? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message