From owner-freebsd-questions@FreeBSD.ORG Fri Dec 4 14:49:52 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EF9571065670 for ; Fri, 4 Dec 2009 14:49:52 +0000 (UTC) (envelope-from korvus@comcast.net) Received: from mx04.pub.collaborativefusion.com (mx04.pub.collaborativefusion.com [206.210.72.84]) by mx1.freebsd.org (Postfix) with ESMTP id BCDAE8FC0A for ; Fri, 4 Dec 2009 14:49:52 +0000 (UTC) Received: from [192.168.2.164] ([206.210.89.202]) by mx04.pub.collaborativefusion.com (StrongMail Enterprise 4.1.1.4(4.1.1.4-47689)); Fri, 04 Dec 2009 09:49:50 -0500 X-VirtualServerGroup: Default X-MailingID: 00000::00000::00000::00000::::151 X-SMHeaderMap: mid="X-MailingID" X-Destination-ID: freebsd-questions@freebsd.org X-SMFBL: ZnJlZWJzZC1xdWVzdGlvbnNAZnJlZWJzZC5vcmc= Message-ID: <4B19218E.70909@comcast.net> Date: Fri, 04 Dec 2009 09:49:50 -0500 From: Steve Polyack User-Agent: Thunderbird 2.0.0.23 (X11/20091124) MIME-Version: 1.0 To: lists@midsummerdream.org References: <4B191E92.7010007@midsummerdream.org> In-Reply-To: <4B191E92.7010007@midsummerdream.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: FreeBSD 8.0 not detecting hot swap drive insertion X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Dec 2009 14:49:53 -0000 Rob wrote: > I'm running a 10 hot-swap SATA disk ZFS pool and recently upgraded > from 7.2 to 8. Since I upgraded, freebsd isn't spinning up or > recognizing a new drive that is inserted. In freebsd 7.[0,2], I could > remove a drive and insert a new one and freebsd would recognize it, > spin it up, and create the device nodes. None of that is happening in > 8.0, and the only way I've found to get it to recognize the disk is to > reboot the system. > > I tried using atacontrol to force freebsd to reinit an ata channel, > but that didn't have any effect. Did something change in 8.0 that > prevents this auto-detection? Is there a way to re-enable it? > Are you using the original (7.x) ata(4) driver or the newer enhanced SATA drivers like ahci(4) or siis(4)? If you're using the latter your devices will be labeled /dev/ada* instead of /dev/ad*. If you are indeed using the newer enhanced SATA drivers, you will need to use camcontrol to reset and rescan the associated SATA channels.