Date: Fri, 11 Oct 2024 09:12:01 +0200 From: Ralf Mardorf <ralf-mardorf@riseup.net> To: questions@freebsd.org Subject: Re: How to zero a failing disk drive before disposal? Message-ID: <0bd5d79d35bb036fc73cd226edae1b969b22e3ee.camel@riseup.net> In-Reply-To: <2544410a-8a99-4b2e-a194-c8326a2e0ddd@heuristicsystems.com.au> References: <5117.1728561469@segfault.tristatelogic.com> <2544410a-8a99-4b2e-a194-c8326a2e0ddd@heuristicsystems.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 2024-10-11 at 13:42 +1100, Dewayne Geraghty wrote:
> I worked for a provider of services for the statutory care of children
> (eg removed from parents). [...] We bench-drilled the hard-disks
> before sending them (out of our chain of custody) to a furnace.
+1
> For personal devices we overwrite the device multiple times
After countless discussions about [1] and having recovered and not
recovered lost data myself, I am firmly convinced that it is sufficient
for a private household to overwrite just 1 time. After that Joe and
Jane Lunchbucket can't recover the data anymore and it's also quasi
impossible for a geek to recover something.
The problem with the Lunchbucket family's HDDs is that they only replace
them when they are defective anyway. At best, you can free up stuck
heads and be happy if you can get your 4 TB drive overwritten at all. In
these cases, the question of how often you should overwrite does not
even arise.
It is not for nothing that it is said that you should mount a drive
"read only" as soon as possible after data has been lost in order to
have any chance of recovering anything at all.
Criminals and secret services will think twice about whether it is worth
subjecting the Lunchbucket family's hard drive to time-consuming and
costly forensic treatment.
[1]
=E2=80=A2 rocketmouse@archlinux ~=20
$ man shred | grep -eiterations -eCAUTION -A1
-n, --iterations=3DN
overwrite N times instead of the default (3)
--
CAUTION: shred assumes the file system and hardware overwrite data i=
n place. Although this is common, many platforms operate otherwise. Also,=
backups and mirrors may contain unre=E2=80=90
movable copies that will let a shredded file be recovered later. Se=
e the GNU coreutils manual for details.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0bd5d79d35bb036fc73cd226edae1b969b22e3ee.camel>