From nobody Sat Feb 26 21:21:36 2022 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 0F75B19E04AC for ; Sat, 26 Feb 2022 21:21:46 +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 "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4K5fj474j9z4r10 for ; Sat, 26 Feb 2022 21:21:44 +0000 (UTC) (envelope-from ralf-mardorf@riseup.net) Received: from fews1.riseup.net (fews1-pn.riseup.net [10.0.1.83]) (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 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.riseup.net", Issuer "R3" (not verified)) by mx1.riseup.net (Postfix) with ESMTPS id 4K5fhx6mjzzF3hq for ; Sat, 26 Feb 2022 13:21:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1645910498; bh=8HZ4R6okAp+W1/I+b43kyl1s2a5zv3LNUHJro/GF9N4=; h=Date:From:To:Subject:In-Reply-To:References:From; b=nrn+dDWWa4i99/f+BmiV/lJbuN7iBgZWM8GOG6AkdEeY4ilBfcN7ja0PhPe8ZkgAo dsrgyioogLU8L04qDhovcCW3U8LucgYvHbzZLj/XJymRGWzakcS4yJ/uR9Y30Y54Vb kFNIxInKShZjqHmyZ2N934wqonhDd7Rz/v0m47L8= X-Riseup-User-ID: F06A7BF94729A3ADE5BA06288B5FAF7BDA16F634F0395712E456DA54490DC6FE Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews1.riseup.net (Postfix) with ESMTPSA id 4K5fhx2lf1z5vLp for ; Sat, 26 Feb 2022 13:21:37 -0800 (PST) Date: Sat, 26 Feb 2022 22:21:36 +0100 From: Ralf Mardorf To: questions@freebsd.org Subject: Re: SATA SSD keeps disconnecting Message-ID: <20220226222136.3c310bd2@archlinux> In-Reply-To: References: <7b1bf89d-aed0-5b3f-0666-1a220681d61e@netfence.it> <0806bd9f-49db-c429-0110-76c5f6887f83@holgerdanske.com> List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4K5fj474j9z4r10 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=riseup.net header.s=squak header.b=nrn+dDWW; dmarc=pass (policy=none) header.from=riseup.net; 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 X-Spamd-Result: default: False [-2.60 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[riseup.net:s=squak]; NEURAL_HAM_LONG(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; RWL_MAILSPIKE_GOOD(0.00)[198.252.153.129:from]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; DWL_DNSWL_LOW(-1.00)[riseup.net:dkim]; RCVD_COUNT_THREE(0.00)[3]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_SPAM_SHORT(1.00)[1.000]; DKIM_TRACE(0.00)[riseup.net:+]; DMARC_POLICY_ALLOW(-0.50)[riseup.net,none]; MLMMJ_DEST(0.00)[questions]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; MID_RHS_NOT_FQDN(0.50)[]; ASN(0.00)[asn:16652, ipnet:198.252.153.0/24, country:US]; RCVD_TLS_ALL(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[198.252.153.129:from] X-ThisMailContainsUnwantedMimeParts: N On Sat, 26 Feb 2022 21:45:46 +0100, Tomasz CEDRO wrote: >I thought I have to desolder the NAND chips and read them in memory >programmer Hi, are sure that it is possible to access and understand the link map ( see https://en.wikipedia.org/wiki/Wear_leveling#Types ) or even more worse probably also to decrypt the data? "Some SSD have an internal encryption key, stored in nvram. When issuing a command with hdparm to "secure erase" it, it will simply mark all SSD's blocks as "unallocated", forget the old key and generate a new one." - https://unix.stackexchange.com/questions/593181/is-shred-bad-for-erasing-ssds You likely can read the key, but you unlikely know how to use the key to decrypt data. In a nutshell, if you read the chip, you probably also need to disassemble the firmware, to understand the link map and probably also to know how to decrypt the stored data. It's just my guess, I don't have knowledge about SSD firmware secrets. Regards, Ralf