From owner-freebsd-geom@FreeBSD.ORG Thu Sep 17 20:32:14 2009 Return-Path: Delivered-To: freebsd-geom@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 941C0106568F; Thu, 17 Sep 2009 20:32:14 +0000 (UTC) (envelope-from marcel@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 856328FC1D; Thu, 17 Sep 2009 20:32:14 +0000 (UTC) Received: from freefall.freebsd.org (marcel@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n8HKWEJc021159; Thu, 17 Sep 2009 20:32:14 GMT (envelope-from marcel@freefall.freebsd.org) Received: (from marcel@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n8HKWEUG021155; Thu, 17 Sep 2009 20:32:14 GMT (envelope-from marcel) Date: Thu, 17 Sep 2009 20:32:14 GMT Message-Id: <200909172032.n8HKWEUG021155@freefall.freebsd.org> To: shurd@sasktel.net, marcel@FreeBSD.org, freebsd-geom@FreeBSD.org From: marcel@FreeBSD.org Cc: Subject: Re: kern/138891: [geom] GEOM_PART_* fails with sliced gstripe X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2009 20:32:14 -0000 Synopsis: [geom] GEOM_PART_* fails with sliced gstripe State-Changed-From-To: open->closed State-Changed-By: marcel State-Changed-When: Thu Sep 17 20:25:11 UTC 2009 State-Changed-Why: Your disk partitioning is invalid. You cannot have both a MBR and a BSD disk label in the same place and independently of each other. ace# fdisk /dev/stripe/raid0 ace# bsdlabel /dev/stripe/raid0 If you look closely, FreeBSD 7.2 will use the MBR on /dev/stripe/raid0 and the BSD disklabel on /dev/stripe/raid0s4. However, since a BSD disklabel also embeds a MBR, FreeBSD 8.0 will correctly prefer the BSD disklabel on /dev/stripe/raid0. However, the BSD disk label is not the one that should be used. Fix the problem by wiping out the second sector on the disk. BTW: the problem is caused by creating a dangerously dedicated installation. It's known to be broken and should not be used. FYI, http://www.freebsd.org/cgi/query-pr.cgi?pr=138891