From owner-freebsd-questions@FreeBSD.ORG Thu Nov 24 00:08:45 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EAF53106566B for ; Thu, 24 Nov 2011 00:08:45 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id AB54D8FC0A for ; Thu, 24 Nov 2011 00:08:45 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id pAO08XCx065320; Wed, 23 Nov 2011 17:08:33 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id pAO08XrD065317; Wed, 23 Nov 2011 17:08:33 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Wed, 23 Nov 2011 17:08:33 -0700 (MST) From: Warren Block To: "Julian H. Stacey" In-Reply-To: <201111232108.pANL80g3041149@fire.js.berklix.net> Message-ID: References: <201111232108.pANL80g3041149@fire.js.berklix.net> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Wed, 23 Nov 2011 17:08:33 -0700 (MST) Cc: "freebsd-questions@freebsd.org" , Robert Subject: Re: Invalid fdisk partition table found X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Nov 2011 00:08:46 -0000 On Wed, 23 Nov 2011, Julian H. Stacey wrote: > 2 Base of _my_ man fdisk > " When running multi user, you cannot write unless you first run this: > sysctl kern.geom.debugflags=16 > " But that's not quite correct. Setting debugflags to 16 allows writes to a partition that's mounted, something that should not normally be needed. It will give an error instead of allowing writes in that case. So if writes succeeded, that wasn't the problem. 'gpart -F destroy {device}' may help recover the CF cards.