From owner-freebsd-questions@FreeBSD.ORG Thu Dec 1 08:27:10 2011 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 36261106566B for ; Thu, 1 Dec 2011 08:27:10 +0000 (UTC) (envelope-from cyberleo@cyberleo.net) Received: from paka.cyberleo.net (paka.cyberleo.net [66.219.31.21]) by mx1.freebsd.org (Postfix) with ESMTP id 12BF78FC08 for ; Thu, 1 Dec 2011 08:27:09 +0000 (UTC) Received: from [172.16.44.4] (den.cyberleo.net [66.253.36.39]) by paka.cyberleo.net (Postfix) with ESMTPSA id CF86F28407; Thu, 1 Dec 2011 03:07:43 -0500 (EST) Message-ID: <4ED735CD.7030505@cyberleo.net> Date: Thu, 01 Dec 2011 02:07:41 -0600 From: CyberLeo Kitsana User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20111106 Thunderbird/7.0.1 MIME-Version: 1.0 To: Robert Huff References: <20182.39340.354254.608836@jerusalem.litteratus.org> In-Reply-To: <20182.39340.354254.608836@jerusalem.litteratus.org> X-Enigmail-Version: 1.4a1pre Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: questions@freebsd.org Subject: Re: problem formating disk with gpart 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: Thu, 01 Dec 2011 08:27:10 -0000 On 11/30/2011 03:01 PM, Robert Huff wrote: > > One of my systems has a hot-swap eSATA device, which reports as > "ad1". I'm trying to use this to prepare a new disk using gpart and > something (possibly my understanding) is broken. > After removing another disk and inserting the new one, I do: > >>> gpart show ad1 > => 34 976773101 ad1 GPT (465G) > 34 976773101 - free - (465G) > > ... which is the value for the disk just removed. > If I do (to start clean): > >>> gpart destroy ad1 > gpart destroy ad1 > gpart: Input/output error > > Huh? If I remember correctly, the old ATA subsystem (ad*) does not support hotswap notification, so the kernel will not see a device change until reboot or reinit. You should probably be using AHCI (if the driver supports your chipset) or very careful use of atacontrol detach, attach, or reinit. -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net Furry Peace! - http://wwww.fur.com/peace/