Date: Fri, 14 Jul 2017 11:03:03 -0600 (MDT) From: Warren Block <wblock@wonkity.com> To: Arthur Chance <freebsd@qeng-ho.org> Cc: Doug Hardie <bc979@lafn.org>, David Christensen <dpchrist@holgerdanske.com>, freebsd-questions@freebsd.org Subject: Re: Unusual Question Message-ID: <alpine.BSF.2.21.1707141058180.45926@wonkity.com> In-Reply-To: <0ccfaae9-6fdb-adfa-71b2-5dd3978f41b3@qeng-ho.org> References: <888578F8-AD68-4993-823C-152789F3C929@mail.sermon-archive.info> <b5b8a49e-804d-15be-25b7-ff7c29a5ae8a@holgerdanske.com> <B63B13F0-D5E4-4C32-AD9B-B9D505AFDAA2@mail.sermon-archive.info> <0ccfaae9-6fdb-adfa-71b2-5dd3978f41b3@qeng-ho.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 14 Jul 2017, Arthur Chance wrote: > On 14/07/2017 07:11, Doug Hardie wrote: >> >>> On 13 July 2017, at 21:44, David Christensen <dpchrist@holgerdanske.com> wrote: >>> >>> 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. >> >> 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. > > How about using the BIOS extended write sector call (INT 13h, AH=43h) in > your code? That should be portable. Won't that choke after 2TB? It might wrap around to the start of the drive after the 2TB mark, or just fail. Failure would be better, at least it would mean that half of a 4TB drive might be left intact without notice. But this idea of having a self-destructive boot block has some other problems. A tiny space for code, a dangerous thing to have lying around, and if you have to reboot into it, might as well reboot into mfsBSD (http://mfsbsd.vx.sk/) and be sure that it works. For SSDs, the Secure Erase option might be viable. I have not yet had that work in the couple of times I've tried it, but that could be due to improper usage or possibly lack of support on the old SSDs being used.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.21.1707141058180.45926>