From owner-freebsd-current@FreeBSD.ORG  Fri Jan  2 18:56:11 2009
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 6A573106564A
	for <current@freebsd.org>; Fri,  2 Jan 2009 18:56:11 +0000 (UTC)
	(envelope-from imp@bsdimp.com)
Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85])
	by mx1.freebsd.org (Postfix) with ESMTP id 11EA88FC2E
	for <current@freebsd.org>; Fri,  2 Jan 2009 18:56:10 +0000 (UTC)
	(envelope-from imp@bsdimp.com)
Received: from localhost (localhost [127.0.0.1])
	by harmony.bsdimp.com (8.14.2/8.14.1) with ESMTP id n02IsGED059179
	for <current@freebsd.org>; Fri, 2 Jan 2009 11:54:16 -0700 (MST)
	(envelope-from imp@bsdimp.com)
Date: Fri, 02 Jan 2009 11:54:26 -0700 (MST)
Message-Id: <20090102.115426.-1540393465.imp@bsdimp.com>
To: current@freebsd.org
From: "M. Warner Losh" <imp@bsdimp.com>
X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: 
Subject: New warning, what does it mean?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
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, 02 Jan 2009 18:56:11 -0000

I'm getting the following from my main disk on boot now:

GEOM: ad0s2: geometry does not match label (255h,63s != 16h,63s).

What does it mean?  This system is a dual-boot FreeBSD/Windows
laptop.  In the past I've seen sysinstall barf on the former geometry,
and have had problems installing dual-boot core4/FreeBSD systems
because of it.

In addition, the above error message is useless.  Who is complaining?
Why are they complaining?  What is the corrective action to be taken
here?  Why does it matter with modern disks and BIOSes anyway?

Warner