From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 3 21:12:30 2012 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A9172106566B for ; Tue, 3 Apr 2012 21:12:30 +0000 (UTC) (envelope-from rsimmons0@gmail.com) Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 633BF8FC14 for ; Tue, 3 Apr 2012 21:12:30 +0000 (UTC) Received: by vbmv11 with SMTP id v11so153899vbm.13 for ; Tue, 03 Apr 2012 14:12:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=mJINJaBZAuRhI41JYEPHIO6YTD1ft6aW94lSafyWITE=; b=M/8whOdpWOhZ5W7f1ENwFQ55izs05tBAMxaRQICmWcAljUk0e9Ef5eRqPkcf8egx0o 4G+ey6ItteTq1+S+oi/eU2Sy+Y9tD50xJStA3IhXuYEVCdQtguMgGwP6/SesaJaRwPFS KzFwmW/G40LzgwbVMfjADYnZiKqqzwznLZncNEBCzal7ryppaD21/q1FT2I6w/y/7znO MnqZHa5vuaETfo5W/5sg/5pFBCw8jLles9gsxccEp0HWeI7llfAdCgvHOYFEnItLgjcf JZEwM9jUOQ7YEZ0aDEgJfVbH1YLPwdVFlQOAlFCwsHsgQ1x+1IVSyf88lNAhypA+3g3U R4Gw== MIME-Version: 1.0 Received: by 10.52.92.140 with SMTP id cm12mr5527251vdb.115.1333487549940; Tue, 03 Apr 2012 14:12:29 -0700 (PDT) Received: by 10.52.117.76 with HTTP; Tue, 3 Apr 2012 14:12:29 -0700 (PDT) In-Reply-To: <20120403.194643.926.1@DOMY-PC> References: <20120403.194643.926.1@DOMY-PC> Date: Tue, 3 Apr 2012 17:12:29 -0400 Message-ID: From: Robert Simmons To: hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Subject: Re: gpart and it's EBR confusion X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Apr 2012 21:12:30 -0000 On Tue, Apr 3, 2012 at 3:46 PM, wrote: > 9.0 R i386 > > EBR scheme never installed > > md0s3 has BSD labels scheme > ---- > # gpart destroy -F md0s3 > md0s3 destroyed > > # gpart create -s BSD md0s3 > gpart: geom 'md0s3': File exists > > # gpart show -p md0s3 > =3D> =A0 =A0 =A00 =A01023120 =A0md0s3 =A0EBR =A0(499M) [CORRUPT] > =A0 =A0 =A0 =A00 =A01023120 =A0 =A0 =A0 =A0 - free - =A0(499M) > ---- > > > During one of above tasks, on main console kernel outputs: > -- > GEOM: md0s3: invalid entries in the EBR ignored. I've had a similar problem, but with "gpart destroy" and a GPT partition. If I create a GPT partition on a disk then for some reason begin an install process again by rebooting and starting from the beginning of bsdinstall I am unable to destroy the old partition scheme. I encountered this with sysinstall and 8.0-8.2 as well. The workaround that I found is to use "dd" rather than "gpart destroy". Just dd the drive or part of drive in question from /dev/zero or /dev/random and everything is a clean slate.