From owner-freebsd-questions@freebsd.org Fri Jul 14 04:48:31 2017 Return-Path: Delivered-To: freebsd-questions@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 850F6D947CA for ; Fri, 14 Jul 2017 04:48:31 +0000 (UTC) (envelope-from dpchrist@holgerdanske.com) Received: from holgerdanske.com (holgerdanske.com [184.105.128.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "holgerdanske.com", Issuer "holgerdanske.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6DA607C05E for ; Fri, 14 Jul 2017 04:48:31 +0000 (UTC) (envelope-from dpchrist@holgerdanske.com) Received: from 99.100.19.101 ([99.100.19.101]) by holgerdanske.com with ESMTPSA (ECDHE-RSA-AES128-GCM-SHA256:TLSv1.2:Kx=ECDH:Au=RSA:Enc=AESGCM(128):Mac=AEAD) (SMTP-AUTH username dpchrist@holgerdanske.com, mechanism PLAIN) for ; Thu, 13 Jul 2017 21:44:31 -0700 Subject: Re: Unusual Question To: freebsd-questions@freebsd.org References: <888578F8-AD68-4993-823C-152789F3C929@mail.sermon-archive.info> From: David Christensen Message-ID: Date: Thu, 13 Jul 2017 21:44:30 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: <888578F8-AD68-4993-823C-152789F3C929@mail.sermon-archive.info> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2017 04:48:31 -0000 On 07/09/17 02:57, Doug Hardie wrote: > I have a FreeBSD 9.3 remote server that needs to be purged. I know that rm -rf / will remove all the directory entries, but I need to write over the drive. I thought that dd if=/dev/zero of=/dev/ada0 might do the trick, but it gives an not permitted error. The whole thing can crash and burn at the end. This is an unmanned site so moving drives is not viable. If the machine has BIOS and the system drive isn't too large, write an assembly program that fits into the MBR bootstrap code area to wipe the rest of the drive, assemble the program, write it into the MBR, and reboot. Bonus: the program deletes the MBR when done wiping the rest of the drive. David