From owner-freebsd-questions@freebsd.org Fri Jul 14 06:11:43 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 27C09D96002 for ; Fri, 14 Jul 2017 06:11:43 +0000 (UTC) (envelope-from srs0=kjah=6r=mail.sermon-archive.info=doug@sermon-archive.info) Received: from mail.sermon-archive.info (sermon-archive.info [71.177.216.148]) by mx1.freebsd.org (Postfix) with ESMTP id 087E67E020 for ; Fri, 14 Jul 2017 06:11:42 +0000 (UTC) (envelope-from srs0=kjah=6r=mail.sermon-archive.info=doug@sermon-archive.info) Received: from [10.0.1.251] (mini [10.0.1.251]) by mail.sermon-archive.info (Postfix) with ESMTPSA id 3x82Q52flbz2fkCV; Thu, 13 Jul 2017 23:11:41 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Unusual Question From: Doug Hardie In-Reply-To: Date: Thu, 13 Jul 2017 23:11:41 -0700 Cc: freebsd-questions@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <888578F8-AD68-4993-823C-152789F3C929@mail.sermon-archive.info> To: David Christensen X-Mailer: Apple Mail (2.3273) X-Virus-Scanned: clamav-milter 0.99.2 at mail X-Virus-Status: Clean 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 06:11:43 -0000 > On 13 July 2017, at 21:44, David Christensen = wrote: >=20 > 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=3D/dev/zero of=3D/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. >=20 > 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. >=20 >=20 > Bonus: the program deletes the MBR when done wiping the rest of the = drive. Neat idea, but I have a number of these systems and they all use = different disk drives. That would be a lot of work writing drivers for = each type.