From owner-freebsd-questions Mon Jun 2 07:49:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA22346 for questions-outgoing; Mon, 2 Jun 1997 07:49:34 -0700 (PDT) Received: from hda.hda.com (hda-bicnet.bicnet.net [207.198.1.121]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA22341 for ; Mon, 2 Jun 1997 07:49:30 -0700 (PDT) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id KAA06397; Mon, 2 Jun 1997 10:46:03 -0400 (EDT) From: Peter Dufault Message-Id: <199706021446.KAA06397@hda.hda.com> Subject: Re: Reprobing the scsi bus. In-Reply-To: <19970602145910.53303@pavilion.net> from Josef Karthauser at "Jun 2, 97 02:59:10 pm" To: joe@pavilion.net (Josef Karthauser) Date: Mon, 2 Jun 1997 10:45:59 -0400 (EDT) Cc: freebsd-questions@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Does any body know how to reprobe the scsi bus during runtime? > I've got a 2.2.2 machine with a disk on sd0, sd1 and sd2. > I've just added a drive on sd3, but the kernel doesn't know > about it because it wasn't there when the system booted. > > scsi(8) talks about a /dev/super/scsi device, but I can't find > the node numbers for it anywhere. Apply the reprobe to any of the existing scsi control devices (e.g., /dev/rsd0.ctl). That super device is/was supposed to be a back door for a bus with nothing present at power up. Whether or not the reprobe works or hangs your system is a function of host adapter and OS release, and so you are better off with a reboot unless you know it works. -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval