From owner-freebsd-current@freebsd.org Thu Sep 29 18:35:04 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 72C60C02D4E for ; Thu, 29 Sep 2016 18:35:04 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from mail.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 52EC98E6; Thu, 29 Sep 2016 18:35:04 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (c-73-231-226-104.hsd1.ca.comcast.net [73.231.226.104]) by mail.baldwin.cx (Postfix) with ESMTPSA id 28B4B10AF7C; Thu, 29 Sep 2016 14:35:03 -0400 (EDT) From: John Baldwin To: Andriy Gapon Cc: "Andrey V. Elsukov" , freebsd-current@freebsd.org Subject: Re: Destroy GPT partition scheme absolutely, how? Date: Thu, 29 Sep 2016 11:33:10 -0700 Message-ID: <11528552.m8AMM69Vtr@ralph.baldwin.cx> User-Agent: KMail/4.14.10 (FreeBSD/11.0-PRERELEASE; KDE/4.14.10; amd64; ; ) In-Reply-To: References: <20160926150109.0d0d793e@hermann> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.baldwin.cx); Thu, 29 Sep 2016 14:35:03 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Sep 2016 18:35:04 -0000 On Thursday, September 29, 2016 01:01:44 AM Andriy Gapon wrote: > On 28/09/2016 21:08, Andrey V. Elsukov wrote: > > This is very strange problem, how did you created MBR if you have not > > destroyed GPT? :) > > Using a tool that's not aware of GPT at all? I think the drive's arrived with some partition scheme on them from burn-in testing or the like and when trying to be reinstalled we could end up "exposing" the GPT when the MBR was destroyed or something like that. -- John Baldwin