From owner-freebsd-current@FreeBSD.ORG  Fri Dec 19 04:31:39 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 B83DA16A4CF
	for <current@freebsd.org>; Fri, 19 Dec 2003 04:31:39 -0800 (PST)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 4FCA143D31
	for <current@freebsd.org>; Fri, 19 Dec 2003 04:31:37 -0800 (PST)
	(envelope-from phk@phk.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.12.10/8.12.10) with ESMTP id hBJCVV1o006724;
	Fri, 19 Dec 2003 13:31:35 +0100 (CET)
	(envelope-from phk@phk.freebsd.dk)
To: Wiktor Niesiobedzki <bsd@w.evip.pl>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Fri, 19 Dec 2003 13:21:46 +0100."
             <20031219122146.GA3682@mail.evip.pl> 
Date: Fri, 19 Dec 2003 13:31:31 +0100
Message-ID: <6723.1071837091@critter.freebsd.dk>
cc: current@freebsd.org
Subject: Re: GEOM oddity with verbose boot 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Dec 2003 12:31:39 -0000

In message <20031219122146.GA3682@mail.evip.pl>, Wiktor Niesiobedzki writes:

>Just an observation:
>When I boot in verbose mode I get:
>GEOM: Configure ad6s1, start 32256 length 80026329600 end 80026361855
>GEOM: Configure ad6s1a, start 0 length 1073741824 end 1073741823
>GEOM: Configure ad6s1b, start 1073741824 length 1073741824 end 2147483647
>GEOM: Configure ad6s1c, start 0 length 80026329600 end 80026329599
>GEOM: Configure ad6s1d, start 2147483648 length 21474836480 end 23622320127
>GEOM: Configure ad6s1e, start 23622320128 length 56404009472 end 80026329599
>GEOM: Configure ad6s1da, start 8192 length 80026321408 end 80026329599
>GEOM: Configure ad6s1db, start 1073741824 length 1073741824 end 2147483647
>GEOM: Configure ad6s1dc, start 0 length 80026329600 end 80026329599
>GEOM: Configure ad6s1dd, start 0 length 1073741824 end 1073741823
>GEOM: Configure ad6s1de, start 2147483648 length 21474836480 end 23622320127
>
>Entries for ad6s1d* are the suspicous one.

You seem to have (most of) a valid BSD label in your ad6s1d parition.

Try 
	bsdlabel ad6s1d

I'm pretty sure it finds a label for you. 

>Wheter I boot verbose or not, the listing in /dev is the same:
># ls /dev/ad6*
>/dev/ad6
>/dev/ad6s1
>/dev/ad6s1a
>/dev/ad6s1b
>/dev/ad6s1c
>/dev/ad6s1d
>/dev/ad6s1e

When you open ad6s1d for writing (by mounting it) the BSDLABEL which
had attached gets spoiled so you don't see the entries in /dev
while it is mounted.


-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.