Date: Sat, 24 Jul 2004 16:23:32 -0500 From: Lane <lane@joeandlane.com> To: freebsd-current@freebsd.org Cc: Robert Watson <rwatson@freebsd.org> Subject: Re: GEOM fails to create ad0 Message-ID: <200407241623.32730.lane@joeandlane.com> In-Reply-To: <Pine.NEB.3.96L.1040724121636.19077C-100000@fledge.watson.org> References: <Pine.NEB.3.96L.1040724121636.19077C-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200407241623.32730.lane>