From owner-freebsd-current@FreeBSD.ORG Sat Jul 24 21:23:34 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE2A316A4CE; Sat, 24 Jul 2004 21:23:34 +0000 (GMT) Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.120.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9973943D1F; Sat, 24 Jul 2004 21:23:34 +0000 (GMT) (envelope-from lane@joeandlane.com) Received: from user-112urtn.biz.mindspring.com ([66.47.111.183] helo=joeandlane.com) by harrier.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 1BoTzS-0000rb-00; Sat, 24 Jul 2004 14:23:34 -0700 Received: from [127.0.0.1] (localhost.joeandlane.com [127.0.0.1]) by joeandlane.com (8.12.11/8.12.11) with ESMTP id i6OLNX8h000685; Sat, 24 Jul 2004 16:23:33 -0500 (CDT) (envelope-from lane@joeandlane.com) From: Lane To: freebsd-current@freebsd.org Date: Sat, 24 Jul 2004 16:23:32 -0500 User-Agent: KMail/1.6.2 References: In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200407241623.32730.lane@joeandlane.com> cc: Robert Watson Subject: Re: GEOM fails to create ad0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jul 2004 21:23:34 -0000 On Sat July 24 2004 11:17 am, Robert Watson wrote: > On Sat, 24 Jul 2004, Lane wrote: > > I successfully built a kernel for FreeBSD 5.2.1-RELEASE #1 on my 8Gig > > ad2 but when I boot it my 30Gig ad0 does not appear in /dev/ > > > > I boot 4.10-STABLE on my 30 Gig ad0 and am able to mount ad2, but not > > vice versa. > > > > Does anyone have information on how to trouble-shoot GEOM? > > I guess a first question would be: is this a GEOM problem, or a driver > problem? Drivers find devices and present them for use by GEOM, which > then provides storage abstraction and exposes the device via devfs. Does > ad0 appear in your dmesg output? If not, perhaps we're looking at a > driver problem... > > Robert N M Watson FreeBSD Core Team, TrustedBSD Projects > robert@fledge.watson.org Principal Research Scientist, McAfee Research > Ok, I guess I kind of figured this out. I opened the box and switched the drives around. I hadda reedit fstab, but now both drives are visible regardless of which one I boot on. so ... nevermind ... and thanks to those who responded.