From nobody Fri Oct 11 08:21:11 2024 X-Original-To: questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4XQ02N5TVrz5YVJb for ; Fri, 11 Oct 2024 08:21:16 +0000 (UTC) (envelope-from ralf-mardorf@riseup.net) Received: from mx0.riseup.net (mx0.riseup.net [198.252.153.6]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mx0.riseup.net", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XQ02M53H7z3xcP for ; Fri, 11 Oct 2024 08:21:15 +0000 (UTC) (envelope-from ralf-mardorf@riseup.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=riseup.net header.s=squak header.b=SJjPSyaV; spf=pass (mx1.freebsd.org: domain of ralf-mardorf@riseup.net designates 198.252.153.6 as permitted sender) smtp.mailfrom=ralf-mardorf@riseup.net; dmarc=pass (policy=none) header.from=riseup.net Received: from fews01-sea.riseup.net (fews01-sea-pn.riseup.net [10.0.1.109]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx0.riseup.net (Postfix) with ESMTPS id 4XQ02L1gz6z9vLs for ; Fri, 11 Oct 2024 08:21:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1728634874; bh=3fTfnBmYTU1c8sNsH2m9EH7z0hfLMrW1FQdZ8NITHjA=; h=Subject:From:To:Date:In-Reply-To:References:From; b=SJjPSyaVt6HYUN7tf+IS3SI9dvbqxvpr+giJ9dxdgPBKKQBMNjFsrErcqTDJ0hD8z dJCneEwMRVUFVBSIcHbnV6462DCYxO35yUmRP2SxozE0hqXzAd3pVHoRJjUUJySq5O kg+JmeM1nykScmgBicWA3/ilxqChcc/nwCXNP1ZE= X-Riseup-User-ID: 3AD00552FAE6BEDFA66C8C8745A4207711770AD4B93E8979785235EF3CD40A16 Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews01-sea.riseup.net (Postfix) with ESMTPSA id 4XQ02K5tT8zJsS8 for ; Fri, 11 Oct 2024 08:21:13 +0000 (UTC) Message-ID: <88d89e51653960a519a85c5edd9686e73ea9e144.camel@riseup.net> Subject: Re: How to zero a failing disk drive before disposal? From: Ralf Mardorf To: questions@freebsd.org Date: Fri, 11 Oct 2024 10:21:11 +0200 In-Reply-To: <14177.1728632667@segfault.tristatelogic.com> References: <14177.1728632667@segfault.tristatelogic.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 X-Spamd-Result: default: False [-4.30 / 15.00]; DWL_DNSWL_LOW(-1.00)[riseup.net:dkim]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; DMARC_POLICY_ALLOW(-0.50)[riseup.net,none]; R_DKIM_ALLOW(-0.20)[riseup.net:s=squak]; R_SPF_ALLOW(-0.20)[+a:mx0.riseup.net]; RWL_MAILSPIKE_VERYGOOD(-0.20)[198.252.153.6:from]; RCVD_IN_DNSWL_LOW(-0.10)[198.252.153.6:from]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_ALL(0.00)[]; DKIM_TRACE(0.00)[riseup.net:+]; RCPT_COUNT_ONE(0.00)[1]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:16652, ipnet:198.252.153.0/24, country:US]; TO_DN_NONE(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; MISSING_XM_UA(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+] X-Rspamd-Queue-Id: 4XQ02M53H7z3xcP X-Spamd-Bar: ---- On Fri, 2024-10-11 at 00:44 -0700, Ronald F. Guilmette wrote: > > 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. >=20 > Fortunately, I had the Good Sense to have multiple recent backups, so > I don't believe I lost anything. I just wanted to say that on the one hand we rightly fear data loss and therefore make backups instead of relying on the fact that one time overwritten data possibly can be restored, because it's basically not possible, at least not without a lab with glowing green liquids, flashing Tesla coils and stuff like that and on the other hand, we believe that data that has only been overwritten once can be recovered by any petty criminal who can wear a black hoodie and is able to sit on a chair in front of a keyboard, without equipment such as glowing green liquids, flashing Tesla coils. Data that has been overwritten even once is gone, to be able to read it you need at least the right Torx[tm] screwdriver, wearing a hoodie and being able to sit on a chair is no longer enough.