From nobody Sun Oct 13 15:05: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 4XRNw03QHbz5Z4Gw for ; Sun, 13 Oct 2024 15:05:36 +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 4XRNvy4Wj4z56Kd for ; Sun, 13 Oct 2024 15:05:34 +0000 (UTC) (envelope-from ralf-mardorf@riseup.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=riseup.net header.s=squak header.b=eKIcFXQs; 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 4XRNvx07hlz9vfY for ; Sun, 13 Oct 2024 15:05:33 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1728831933; bh=4MY4DoRGPXrgIUzITqNryVkBTuMCxqPEWqam77t2P6U=; h=Subject:From:To:Date:In-Reply-To:References:From; b=eKIcFXQsfxQwDd454fXL2U0Qrc98NIJjvjemi/f6D1UBHJyIEomAwIa9OGT40XkQ7 CVIGJQ199cjl9ihBdwYgMHXyfaeItBR6biN8rQG8qMGwELhgmNAJt7NxR1ox+4UiLt QKxNKctlJCWoj678Id2ztzGIzmSr3bpqDCHiEWV0= X-Riseup-User-ID: D42F359844B22E6202D44FAEA67484890DF5018ADB5E2310C0F8B32777CA3DBA Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews01-sea.riseup.net (Postfix) with ESMTPSA id 4XRNvw4NJ0zJskT for ; Sun, 13 Oct 2024 15:05:32 +0000 (UTC) Message-ID: <0687f794db7f586c45646bb475bd833b604a2175.camel@riseup.net> Subject: Re: How to zero a failing disk drive before disposal? From: Ralf Mardorf To: questions@freebsd.org Date: Sun, 13 Oct 2024 17:05:29 +0200 In-Reply-To: <32911.1728826816@segfault.tristatelogic.com> References: <32911.1728826816@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]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; DWL_DNSWL_LOW(-1.00)[riseup.net:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[riseup.net,none]; R_SPF_ALLOW(-0.20)[+a:mx0.riseup.net]; RWL_MAILSPIKE_VERYGOOD(-0.20)[198.252.153.6:from]; R_DKIM_ALLOW(-0.20)[riseup.net:s=squak]; 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: 4XRNvy4Wj4z56Kd X-Spamd-Bar: ---- On Sun, 2024-10-13 at 06:40 -0700, Ronald F. Guilmette wrote: > Anyway, one of the drives I've got that I am hoping to dispense with > soon is an older model WD "Passport" external 4TB USB3 drive.=C2=A0 > Optimally, I'd like to simply perform [snip] Hi, Since I use Linux daily and FreeBSD only rarely, I do not know the programmes that FreeBSD offers for this purpose, but I fear that there will only be insignificant differences in this area. Under Linux it is, apart from allegedly existing exceptions, not possible to access an underlying, mostly SATA drive via the USB controller. From off-list correspondence, I know with absolute certainty that the joys of normal operation with drives in USB enclosures are actually always the plague, no matter which OS you use. I use a specific enclosure from a specific company, whose controller has firmware that causes me no problems in normal operation. I assemble these things myself. If you don't have an alternative connection to the USB port and the case can't be opened, then the desired commands will most likely not get through to the drive. Regards, Ralf Translated with DeepL.com (free version)