From owner-freebsd-current@freebsd.org Mon Sep 26 13:39:29 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 E27A9BE8921 for ; Mon, 26 Sep 2016 13:39:29 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A711F166A for ; Mon, 26 Sep 2016 13:39:29 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 85EED28483; Mon, 26 Sep 2016 15:39:20 +0200 (CEST) Received: from illbsd.quip.test (ip-86-49-16-209.net.upcbroadband.cz [86.49.16.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id C5AFF28461; Mon, 26 Sep 2016 15:39:19 +0200 (CEST) Subject: Re: Destroy GPT partition scheme absolutely, how? To: "Hartmann, O." , FreeBSD CURRENT References: <20160926150109.0d0d793e@hermann> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <57E92507.6020900@quip.cz> Date: Mon, 26 Sep 2016 15:39:19 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:42.0) Gecko/20100101 Firefox/42.0 SeaMonkey/2.39 MIME-Version: 1.0 In-Reply-To: <20160926150109.0d0d793e@hermann> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: Mon, 26 Sep 2016 13:39:30 -0000 Hartmann, O. wrote on 09/26/2016 15:01: [...] > Using a fresh/new SD or USB resolves the problem. But the question > remains: how can I destroy any relevant GPT information on a Flash > drive (or even harddisk) to avoid unwanted remains of an foul image > installation? > > First guess was to write the last couple of bytes on such a flash drive > by letting dd(1) counting backwards, but I couldn't figure out how to > let dd(1) do such a procedure. The nightmare didn't end, while trying, > the SD flash card died :-( I use dd if=/dev/zero almost everytime when I need to install system on used HDD. I rewrite about 10MB on its start and then about 10MB on the end. I have some script to do this - simply takes media size from diskinfo command, substract 10MB and then dd with seek Hope that it will help you Miroslav Lachman