From owner-freebsd-questions@FreeBSD.ORG Tue Oct 19 23:01:57 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3A09716A4CE for ; Tue, 19 Oct 2004 23:01:57 +0000 (GMT) Received: from mta01-svc.ntlworld.com (mta01-svc.ntlworld.com [62.253.162.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id 98A1A43D53 for ; Tue, 19 Oct 2004 23:01:56 +0000 (GMT) (envelope-from scott@fishballoon.org) Received: from llama.fishballoon.org ([81.104.197.225]) by mta01-svc.ntlworld.comESMTP <20041019230110.OLED13844.mta01-svc.ntlworld.com@llama.fishballoon.org>; Wed, 20 Oct 2004 00:01:10 +0100 Received: from scott by llama.fishballoon.org with local (Exim 4.42 (FreeBSD)) id 1CK2zL-000Bcf-AW; Wed, 20 Oct 2004 00:01:55 +0100 Date: Wed, 20 Oct 2004 00:01:55 +0100 From: Scott Mitchell To: luke Message-ID: <20041019230154.GA42775@llama.fishballoon.org> References: <5fee5e30041018140451b31d6@mail.gmail.com> <1098135925.2229.6.camel@localhost> <5fee5e3004101819175f701744@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5fee5e3004101819175f701744@mail.gmail.com> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 4.9-RELEASE-p4 i386 Sender: Scott Mitchell cc: arden cc: freebsd Subject: Re: hot swap scsi drive X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Oct 2004 23:01:57 -0000 On Mon, Oct 18, 2004 at 09:17:55PM -0500, luke wrote: > > Is this box designed do be hot pluggable? the IBM p-series servers I use > > at work have a back plane that allows this and sets the address > > the drives are designed to be hot pluggable they are in removable > trays that slide in and out. i'm just asking if there is a > freebsd-specific action that i should take before pulling a drive. > thx, I guess it will depend a lot on the hardware you have, but you probably want to try one or both of 'camcontrol stop' or 'camcontrol eject' before pulling the drive. One of these should spin the drive down and leave it in a safe state to be removed. Again, when plugging a new drive in, it might be recognised automatically, or you might need a 'camcontrol rescan' or 'camcontrol start' to get it to appear. Note that all of these commands expect to be given a bus or device number to work on - you can find the right numbers with 'camcontrol devlist'. I assume you're in a position to try a few things out before you put this machine into production? The Intel L440GX+ boards we have here are quite happy for you to stop a drive then pull it, and new drives come up all by themselves when plugged in, but your hardware might need some extra incantations to make it work - you really need to try a few of these commands and see what happens. Cheers, Scott -- =========================================================================== Scott Mitchell | PGP Key ID | "Eagles may soar, but weasels Cambridge, England | 0x54B171B9 | don't get sucked into jet engines" scott at fishballoon.org | 0xAA775B8B | -- Anon