From owner-freebsd-geom@FreeBSD.ORG  Tue May 20 20:20:00 2014
Return-Path: <owner-freebsd-geom@FreeBSD.ORG>
Delivered-To: freebsd-geom@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id CE895453
 for <freebsd-geom@freebsd.org>; Tue, 20 May 2014 20:20:00 +0000 (UTC)
Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com
 [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id B5C8D2E2B
 for <freebsd-geom@freebsd.org>; Tue, 20 May 2014 20:20:00 +0000 (UTC)
Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1])
 by segfault.tristatelogic.com (Postfix) with ESMTP id 92CEF3ADCF;
 Tue, 20 May 2014 13:20:00 -0700 (PDT)
From: "Ronald F. Guilmette" <rfg@tristatelogic.com>
To: "Steven Hartland" <killing@multiplay.co.uk>,
    freebsd-geom@freebsd.org
Subject: Re: GEOM_PART: Integrity check failed (ada2, MBR)
In-Reply-To: <90779722305645B99AA673EDA11C349F@multiplay.co.uk>
Date: Tue, 20 May 2014 13:20:00 -0700
Message-ID: <38408.1400617200@server1.tristatelogic.com>
X-BeenThere: freebsd-geom@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: GEOM-specific discussions and implementations
 <freebsd-geom.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-geom>,
 <mailto:freebsd-geom-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-geom/>
List-Post: <mailto:freebsd-geom@freebsd.org>
List-Help: <mailto:freebsd-geom-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-geom>,
 <mailto:freebsd-geom-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 20 May 2014 20:20:00 -0000


In message <90779722305645B99AA673EDA11C349F@multiplay.co.uk>,
"Steven Hartland" <killing@multiplay.co.uk> wrote:

>----- Original Message ----- 
>From: "Ronald F. Guilmette" <rfg@tristatelogic.com>
>
>> I already have sought, and have already been provided with the steps
>> that I need to undertake in order to "repair" the apparent capacity of
>> the drive in question, and I am already making plans to replace my
>> *&^%$#@ Gigabyte motherboard with something different with all due
>> haste.
>
>Just in case you or others are unaware later versions of camcontrol have
>the ability to see and edit / remove HPA.

I, for one, was most certainly *not* aware of that.

Could I ask you to please elaborate?  How would this be done... using
camcontrol?