From owner-freebsd-questions@FreeBSD.ORG Tue Nov 2 05:12:55 2010 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 43428106566C for ; Tue, 2 Nov 2010 05:12:55 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id 212898FC0C for ; Tue, 2 Nov 2010 05:12:55 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id oA25Crro082011 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 1 Nov 2010 22:12:54 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id oA25CrVY082010; Mon, 1 Nov 2010 22:12:53 -0700 (PDT) Received: from fbsd61 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA03009; Mon, 1 Nov 10 21:04:26 PST Date: Mon, 01 Nov 2010 22:03:58 -0700 From: perryh@pluto.rain.com To: dteske@vicor.com Message-Id: <4ccf9bbe.l08XJVISTgP78tSZ%perryh@pluto.rain.com> References: <20101031200258.GA1302@tiny.Sisis.de> <1288627455.6744.24.camel@localhost.localdomain> In-Reply-To: <1288627455.6744.24.camel@localhost.localdomain> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: guru@unixarea.de, freebsd-questions@freebsd.org Subject: Re: sysinstall(8) && bsdlabel a new disk 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: Tue, 02 Nov 2010 05:12:55 -0000 Devin Teske wrote: > sysinstall probes hardware when it starts. Therefore, after making > changes (specifically after writing) to the disk in the FDISK > partition editor, you need to Ctrl-C and Abort-out and relaunch > sysinstall so that it probes the new disk devices (ad4s1, ad4s2, > etc.) before you can start adding BSD disklabels (ad4s1a, ad4s1b, > etc.) to the slice (aka partition). > > This has been an age-old problem (hmmm, perhaps get could some mad > karma for fixing it). At least in 8.1, there is a sysinstall operation somewhere to re-probe devices, presumably to cover exactly this sort of situation. Does it not work?