From nobody Fri Oct 11 07:47:29 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 4XPzHV58rJz5YS8W for ; Fri, 11 Oct 2024 07:47:34 +0000 (UTC) (envelope-from ralf-mardorf@riseup.net) Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (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 "mx1.riseup.net", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XPzHT2nHGz4r0r for ; Fri, 11 Oct 2024 07:47:33 +0000 (UTC) (envelope-from ralf-mardorf@riseup.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=riseup.net header.s=squak header.b=DA0cJc4n; spf=pass (mx1.freebsd.org: domain of ralf-mardorf@riseup.net designates 198.252.153.129 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 mx1.riseup.net (Postfix) with ESMTPS id 4XPzHS056gzDqH9 for ; Fri, 11 Oct 2024 07:47:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1728632852; bh=W6lEXwYwQf9Fgbz/5JsHbMsOxKwKPq1doeviWCBUe68=; h=Subject:From:To:Date:In-Reply-To:References:From; b=DA0cJc4n3fPQ1OBDRZ8IurF1zMd5klrvAym+wUYVNDoa1FSX1sxR82VNcKtqLsXeh Y7j9wsmoH94D/cBmEYEm1PxDXvrjtcssWzh1nxYK2PHmW3Apiydr1QMrQKBqb0WyK8 q5WC9Ja7Qz2e3eQoKAx+WvDG/1TOj9HlQBq7d0pQ= X-Riseup-User-ID: 343164A90913514B65FCAB0B1A610BED41BF60CC1102303E16E900BC949E9E66 Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews01-sea.riseup.net (Postfix) with ESMTPSA id 4XPzHR2vTHzJmvR for ; Fri, 11 Oct 2024 07:47:31 +0000 (UTC) Message-ID: Subject: Re: How to zero a failing disk drive before disposal? From: Ralf Mardorf To: questions@freebsd.org Date: Fri, 11 Oct 2024 09:47:29 +0200 In-Reply-To: <0bd5d79d35bb036fc73cd226edae1b969b22e3ee.camel@riseup.net> References: <5117.1728561469@segfault.tristatelogic.com> <2544410a-8a99-4b2e-a194-c8326a2e0ddd@heuristicsystems.com.au> <0bd5d79d35bb036fc73cd226edae1b969b22e3ee.camel@riseup.net> 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.20 / 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.998]; DMARC_POLICY_ALLOW(-0.50)[riseup.net,none]; R_DKIM_ALLOW(-0.20)[riseup.net:s=squak]; R_SPF_ALLOW(-0.20)[+a:mx1.riseup.net]; RCVD_IN_DNSWL_LOW(-0.10)[198.252.153.129:from]; MIME_GOOD(-0.10)[text/plain]; RWL_MAILSPIKE_GOOD(-0.10)[198.252.153.129:from]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; DKIM_TRACE(0.00)[riseup.net:+]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; ASN(0.00)[asn:16652, ipnet:198.252.153.0/24, country:US]; ARC_NA(0.00)[]; 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]; RCVD_VIA_SMTP_AUTH(0.00)[]; MIME_TRACE(0.00)[0:+] X-Rspamd-Queue-Id: 4XPzHT2nHGz4r0r X-Spamd-Bar: ---- On Fri, 2024-10-11 at 09:12 +0200, Ralf Mardorf wrote: > After countless discussions [...] I am firmly convinced that it is > sufficient for a private household to overwrite just 1 time. >=20 > The problem with the Lunchbucket family's HDDs is that they only > replace them when they are defective anyway. For sure we will not use kind of a shred program that tries to overwrite files, we will use kind of a dd command with a random pattern, zeros or else. On Thu, 2024-10-10 at 04:57 -0700, Ronald F. Guilmette wrote: > I could just dd /dev/zero to the thing. But there's a catch. > According to what I have read, dd will halt if it encounters a write > error. By https://unix.stackexchange.com/questions/229354/how-to-ignore-write-errors-= while-zeroing-a-disk a "sdd" command is mentioned, wich seems to be provided by https://sourceforge.net/projects/schilytools/files/ and it might be available for FreeBSD, https://www.freshports.org/devel/schilybase . FWIW the Arch User repository provides schily-tools-sdd, but Arch Linux doesn't provide a live media. Ubuntu and friends provide a live media, but they don't provide schilytools, but it might build without issues on an Ubuntu or so live media, https://www.unixmen.com/install-schily-tools-on-linux/ .