# How do you safely erase SSDs before selling? **URL:** https://discuss.privacyguides.net/t/how-do-you-safely-erase-ssds-before-selling/34650 **Category:** Questions **Created:** 2026-01-12T18:48:04Z **Posts:** 52 ## Post 1 by @cooldude — 2026-01-12T18:48:04Z I need to sell drives that contain all banking data and passwords so I was looking at how to do erase them. Im about to give up on trying to do this myself because feels pretty scary. I have been checking guides, and SSDs are not recommended to use something like nwipe with 3 DoD passes. They say to use the internal Secure Erase parameters but it’s too complex. It appears each vendor has their own propietary windows tools, but im booting from the OS drive, it will not work since it needs to be unmounted, plus im not sure if you should trust that anyway. So I was looking how to do it with Linux. I used to use partedmagic which had a nice GUI but I lost the iso, and I cannot pay for this stuff right now (now it’s commercial) Anyone knows a tutorial that actually works? I need to wipe a Samsung Evo 970 Plus and a Crucial MX500, this one is older, both are 1TB. The tutorials I have found: > **[Advanced: Erasing SATA Drives by using the Linux hdparm Utility - GROK...](https://grok.lsu.edu/article.aspx?articleid=16716)** > > GROK Knowledgebase is Louisiana State University's online support environment. > **[Secure Erase HDDs/SSDs(SATA/NVMe) using hdparm & nvme-cli on Linux](https://notebooktalk.net/topic/210-secure-erase-hddsssdssatanvme-using-hdparm-nvme-cli-on-linux/)** > > Hey everyone, I wanted to post a new thread dedicated for secure wiping SSD/HDDs after I tried hdparm and nvme-cli. I wasn't willing to share it initially, since it maybe dangerous if used incorrectly! Anyway, I posted this guide after searching many... But im worried about how to do this properly. I have already burned Ubuntu Live on an USB, but like said im not sure if these tutorials will work or screw up something. The drives have been used for years but they work great, if I can do this I can sell them, I really need the money. If someone knows please let me know. --- ## Post 2 by @fria — 2026-01-12T18:50:32Z My motherboard had a secure erase feature in the UEFI settings, you might check there. --- ## Post 3 by @cooldude — 2026-01-12T18:57:16Z Thanks for input, unfortunately, this board does not seem to have this feature. --- ## Post 4 by @Onscreen5341 — 2026-01-12T19:07:29Z > I need to sell drives that contain all banking data and passwords so I was looking at how to do erase them. Since SSDs have sectors that can’t be written by a user, rather than by the hardware itself it’s pretty hard to erase it. > I have been checking guides, and SSDs are not recommended to use something like nwipe with 3 DoD passes. They say to use the internal Secure Erase parameters but it’s too complex. As far as I know the internal erase function of your motherboard and specialized devices for SSD destructions are the only option to erase data of an SSD besides physical destroying it. > It appears each vendor has their own propietary windows tools, but im booting from the OS drive, it will not work since it needs to be unmounted, plus im not sure if you should trust that anyway. So I was looking how to do it with Linux. I would not trust them. Mainly because disk manufacture fucked up so many things in the past. > I used to use partedmagic which had a nice GUI but I lost the iso, and I cannot pay for this stuff right now (now it’s commercial) I highly doubt that it can actually securely erase it and there is no proof that it can either. > Anyone knows a tutorial that actually works? I need to wipe a Samsung Evo 970 Plus and a Crucial MX500, this one is older, both are 1TB. If I would, you would use Secure Erase from the motherboard or physically destroy the SSD with an SSD shredder. Additionally, it is good if only encrypted data was stored on the SSDs. --- ## Post 5 by @Valynor — 2026-01-12T19:09:31Z The most reliable method for Secure Erase is using manufacturer-specific tools such as Samsung Magician, Crucial Storage Executive. Because of the way NAND flash works it’s really complicated to make 100% sure everything got deleted. The above mentioned tools are your best bet (if you do trust them). To be extra secure you can fill the SSD once with random data to the brim and then format & manually call TRIM again. The only way to be 100% secure with SSDs unfortunately means to physically destroy the drive. --- ## Post 6 by @any1 — 2026-01-12T19:10:31Z > **[Data Erasure - Divested Computing](https://divested.dev/pages/data_erasure)** --- ## Post 7 by @cooldude — 2026-01-12T19:12:20Z The drives have Bitlocker enabled. But I was using it for a while before doing full disk encryption with Bitlocker. Bitlocker does overwrite empty space or something and then encrypts but im not sure if that is enough. But man that is pretty heavy stuff, an SSD shredder? I mean the idea was to sell it. --- ## Post 8 by @cooldude — 2026-01-12T19:14:12Z But like i said, how im supposed to run these tools when im booting from the OS? if I boot from the Crucial one on Windows, and I need Windows to run Crucial Storage Executive, then I cannot do it because i cannot unmount it. Im not sure if there is some free bootable media thing I could use. But you still are trusting some propietary software. Also I don’t know how to do the Trim thing. Please could someone provide step by step instructions since I dont want to damage the drives I really need the money. --- ## Post 9 by @Onscreen5341 — 2026-01-12T19:15:10Z If you trust the encryption of BitLocker (which is AES128) and you define it as secure enough, every bit of information that is/was stored after and while BitLocker was enabled should be okay. If the data was on the drive before BitLocker was enabled, or you disabled it, than not. --- ## Post 10 by @cooldude — 2026-01-12T19:17:46Z Im not sure if I copied things like keepass database or other sensitive data before encrypting them. In any case, how would I go about this? Can I follow this and it will work? > **[Data Erasure - Divested Computing](https://divested.dev/pages/data_erasure)** Btw, how would you backup your data before doing this? I have unused HDD USB drives. Should I install Debian on it with full disk encryption, then via dislocker paste my relevant backups there and then perform the guide above? (im talking about encryption from scratch just to avoid this in the future, even if it’s HDD anyway) --- ## Post 11 by @user1 — 2026-01-12T19:47:13Z > [@cooldude](#): > > Im not sure if I copied things like keepass database or other sensitive data before encrypting them. In any case, how would I go about this? You could always disable and enable bitlocker again to rencrypt the entire drive. --- ## Post 12 by @Onscreen5341 — 2026-01-12T19:48:00Z This doesn’t help, if you are worried about unencrypted data that was on the disk before. --- ## Post 13 by @user1 — 2026-01-12T19:52:43Z I don’t think so, Bitlocker should rencrypt even the free space so if something was missed with the previous encryption now should be taken care of. --- ## Post 14 by @Onscreen5341 — 2026-01-12T19:55:00Z > I don’t think so, Bitlocker should rencrypt even the free space so if something was missed with the previous encryption now should be taken care of. You can’t delete data on an SSD by just overwritting it. There is also NAND which you can’t overwrite and which bitlocker also doesn’t overwrite. So if the data was unencrypted on the SSD there is a chance someone will get this data even if you encrypt and reencrypt your SSD multiple times. --- ## Post 15 by @privacy.slouchy — 2026-01-12T19:55:10Z It’s a couple years old, but PG published an article that I continue to refer back to: > **[Erasing Data Securely From Your SSD or HDD](https://www.privacyguides.org/articles/2022/05/25/secure-data-erasure/)** > > Erasing data from your computer may seem like a simple task, but if you want to make sure the data is truly unrecoverable, there are some things you should consider. --- ## Post 16 by @anon63378630 — 2026-01-12T19:56:56Z > [@user1](#): > > disable and enable bitlocker again this is a bad idea > [@user1](#): > > Bitlocker should rencrypt even the free space it only encrypts actual data last I checked > [@fria](#): > > secure erase feature in the UEFI settings do not rely on this. > [@Onscreen5341](#): > > You can’t delete data on an SSD by just overwritting yes you can\*\*\* (to an extent and depending on certain circumstances). I’m not going to link my guide since it has already been linked, but it is what I strongly suggest doing because it combines both software and hardware erasure. and again, please please please just always encrypt all drives, even if your password is literally password, it still helps in this case. --- ## Post 17 by @cooldude — 2026-01-12T20:00:00Z Hi, is this your guide? > **[Data Erasure - Divested Computing](https://divested.dev/pages/data_erasure)** I was about to follow these steps. This is giving me anxiety. --- ## Post 18 by @user1 — 2026-01-12T20:00:35Z > [@anon63378630](#): > > it only encrypts actual data last I checked It prompts for two options, encrypting used disk space only or the entire drive. --- ## Post 19 by @cooldude — 2026-01-12T20:21:20Z Hi, I assume the divestos guide is your guide because it says divested computing. I have some questions: `shred --iterations 1 --verbose [DRIVE]` How long will this take on an HDD compared to an SSD? both around 1TB How would you make backups from the bitlocker drives into another drive? Should I install Debian with FDE and put the files there first? As far as the distro, will Ubuntu Live work? Any other tips? I am a bit dissapointed because im worried there is no way to delete data fully without smashing it with a hammer, but I really need to sell it because I need the money so I don’t know. PS: I forgot to ask, i would like to try your Extirpater -This app is just installed in a phone and click “Start”? I never thought about doing these things in phones since I never have anything of value but is interesting in case I want to sell phones too. --- ## Post 20 by @Tux — 2026-01-12T20:40:30Z On Linux: ``` dd if=/dev/zero of=/dev/sda bs=1M ``` Replace /dev/sda by your device obviously. Should be good enough for most intents and purposes. --- ## Post 21 by @Valynor — 2026-01-12T20:44:08Z Please don’t use tools intended for HDDs or just general shredding/wiping tools on SSDs. They do not work properly - the OS has NO control on a block level over where it writes/”overwrites” something on an SSD. This is solely managed by the SSD controller over which the OS again has NO control. --- ## Post 22 by @cooldude — 2026-01-12T20:47:45Z This is why im confused, everyone proposes something different, as this was not in the guide here: > **[Data Erasure - Divested Computing](https://divested.dev/pages/data_erasure)** Why is your method different? --- ## Post 23 by @Tux — 2026-01-12T21:13:38Z The previous reply explains why the “overwrite with zeros” may not be enough in theory. In practice it is enough, unless perhaps you are trying to protect unencrypted data from some very sophisticated forensics lab. --- ## Post 24 by @cooldude — 2026-01-12T21:16:34Z Well I just want to sell my drives, but you never know where it will end, so I think I will run the divested.dev guide and see what happens. --- ## Post 25 by @anon63378630 — 2026-01-12T21:21:01Z > [@Valynor](#): > > just general shredding/wiping tools on SSDs. You MUST do both. I’ve seen drives that won’t even erase when performing an ATA or NVMe erase. I don’t understand why people overcomplicate this, just do both as my guide says. > [@Tux](#): > > Should be good enough for most intents again, need to do both > [@Tux](#): > > `/dev/zero` this is bad. aside, why has this thread not even been closed as a duplicate yet? this has been asked many times before --- ## Post 26 by @cooldude — 2026-01-12T21:31:14Z Okay im going to follow your guide with Ubuntu Live.. let’s see what happens. I am also testing your phone app, is it supposed to fill the entire blue line? it went fast first, then it started again, and has a tiny amount of %, on secondary storage. If you want to sell a phone, my question would be, what happens if I click “Start” on the “Primary storage”? isn’t this the same as running an erasing task on a drive that you are booted from? or this app does not delete files and only overwrites files that you already deleted? in this case, should you do a factory reset first for the Primary storage then run it? (im not sure if a factory reset deleted all files right now) --- ## Post 27 by @anon63378630 — 2026-01-12T21:42:02Z > [@cooldude](#): > > testing your phone app I haven’t updated that in years, and I don’t think it works on modern Android. I’ve removed it from the site. > [@cooldude](#): > > let’s see what happens. you can do some verification that any method you use does or doesn’t work by using photorec, the manual is here: [https://www.cgsecurity.org/testdisk.pdf](https://www.cgsecurity.org/testdisk.pdf) --- ## Post 28 by @cooldude — 2026-01-12T21:47:11Z Well my phone is old so it seems to be working. What do you use if you want to sell a phone nowadays? all im seeing is very bloated windows software for that. There’s some stuff on the appstore but they all require a ton of permissions. --- ## Post 29 by @anon63378630 — 2026-01-12T21:52:06Z > [@cooldude](#): > > seems to be working do not rely on it > [@cooldude](#): > > What do you use all modern phones are encrypted, a factory reset should be sufficient since it purges keys and then issues a blksecdiscard --- ## Post 30 by @cooldude — 2026-01-12T21:58:52Z Why do you say its so old? it says here it was updated in Dec 09, 2024 > **[Extirpater | F-Droid - Free and Open Source Android App Repository](https://f-droid.org/packages/us.spotco.extirpater/)** > > A free space eraser I mean its not recent, but its not something ancient. My phone is a 2018 phone. Anyway, I will do a factory reset if I want to sell it, for now lets see if I can follow your guide without anything exploding. Btw ur website is not loading now. Edit: it works again. Btw sorry for being annoying but what does this mean “You MUST keep your computer on for the following steps and avoid any USB drive enclosures.”? by avoid USB drive enclosures? --- ## Post 31 by @anon63378630 — 2026-01-12T22:09:29Z > [@cooldude](#): > > by avoid USB drive enclosures? any sort of USB to SATA or USB to NVMe adapter some of them will brick a drive if you look at them wrong. --- ## Post 32 by @KevPham — 2026-01-12T22:11:13Z > [@anon63378630](#): > > aside, why has this thread not even been closed as a duplicate yet? this has been asked many times before Ironically, this specific question about SSDs was not asked on the forum before. --- ## Post 33 by @Polymer7229 — 2026-01-13T22:55:32Z If it was Bitlockered and your TPM was used to unlock it, I would just erase the partitions and wipe all recovery keys. The question is, how are YOU (or others) supposed to recover the encrypted contents from the disk without the TPM or the recovery keys? This is the selling point of enabling BitLocker/device encryption in the first place: a disk thief wouldn’t be able to read the contents. The only material left for decryption would be in your TPM, but once you install a new OS SSD, enabling Bitlocker, the decryption material is unlikely to be around. --- ## Post 34 by @anon63378630 — 2026-01-13T23:00:16Z You should still wipe before disposal/sale regardless of encryption. --- ## Post 35 by @AHF8329 — 2026-01-14T15:59:54Z I don’t mean to be offensive but some people really shouldn’t be giving advice if they don’t know what they’re talking about. **Don’t ever try to wipe an SSD by overwriting.** Not only doesn’t it work that way on SSDs but it also reduces its lifespan. There are **safe ways** to wipe an SSD but let me clarify some things: On modern SSDs, simply using the TRIM command after deleting files or partitions and leaving the device on for a couple of minutes already makes data recovery close to impossible. Once the TRIM command has been issued, you have a few minutes at best (depending on firmware) until the data is gone for good. Windows and most Linux distributions typically issue TRIM automatically once a week. You can change this frequency or manually trigger TRIM. On Windows, this can be done with the ‘optimize drive’ utility; on Linux, it’s achieved through `fstrim`. There’s no harm in issuing TRIM more frequently, apart from making deleted data irrecoverable – with almost certain guarantee. It’s important to note that LUKS partitions never get TRIMed by default on Linux due to potential metadata leaks (such as the amount of data). Unless you prioritize plausible deniability—which is rarely the case—you should enable TRIM on LUKS partitions for performance and lifespan reasons. This also means you should issue TRIM after deleting an encrypted partition, as without it, LUKS or Bitlocker headers could be recovered and open a path to password brute-forcing. In short, TRIM alone makes data recovery pretty much hopeless in practice, though there’s still a theoretical risk due to firmware differences and other factors. The only proper ways to wipe SSDs are crypto erase and block erase. Crypto Erase only works on self-encrypting SSDs (usually TCG Opal/Pyrite drives) by erasing the key encryption key, making previously written data inaccessible. An even better way to wipe SSDs is to use the block erase command, which almost every modern SSD supports. It works by applying an erase voltage to all NAND cells – this is the safest method and usually takes a couple of seconds or maybe a minute. You can read more about it [here](https://wiki.archlinux.org/title/Solid_state_drive/Memory_cell_clearing). There are various CLI applications available to help you issue these operations. You can use nvme-cli, openseachest, or sedutil for crypto erases on TCG compliant drives. Summary: - Don’t ever try to wipe your SSD by overwriting - In the real world, TRIM makes data recovery pretty much hopeless - The proper way to wipe an SSD is through crypto erase or, even better, block erase --- ## Post 36 by @anon63378630 — 2026-01-14T16:04:41Z > [@AHF8329](#): > > simply using the TRIM command after deleting files or partitions and leaving the device on for a couple of minutes already makes data recovery close to impossible. This is false. I have a stack of Marvell and Phison SSD’s that do absolutely nothing when TRIM is issued. You can blkdiscard them 100 times and still access all the data like nothing happened. You cannot trust the software, you cannot trust the hardware, you must do both, wear be damned. And if in doubt, physically destroy the drive. > [@AHF8329](#): > > sedutil for crypto erases on TCG compliant drives. I have a note about this on my page: newer Samsung and WD drives WILL NOT erase any data when a PSID revert is issued unless a locking range is configured. Micay even mentioned it here: [Daniel Micay: "PSID revert on a Samsung SSD appears to only wipe…" - GrapheneOS Mastodon](https://grapheneos.social/@DanielMicay/109622200255026968) --- ## Post 37 by @anon63378630 — 2026-01-14T16:18:11Z > [@AHF8329](#): > > self-encrypting SSDs (usually TCG Opal/Pyrite drives) Block erase is mandated for Pyrite and OPAL. Encryption/SED is NOT allowed on Pyrite. SED and crypto erase is only mandated for OPAL. > **[micron-ssd-security-features-tech-brief.pdf](https://assets.micron.com/adobe/assets/urn:aaid:aem:43be011a-4d81-4894-bdd7-cd9e0906518d/original/as/micron-ssd-security-features-tech-brief.pdf)** > > 448.74 KB --- ## Post 38 by @AHF8329 — 2026-01-14T16:55:52Z Jesus. What a pile of garbage. > [@anon63378630](#): > > This is false. I have a stack of Marvell and Phison SSD’s that do absolutely nothing when TRIM is issued. I will believe it until I see a video of you doing it because I can already tell you are either not issuing the TRIM command properly or you’re using an adapter that simply ignores the command. I’ve seen this happen quite some time. > [@anon63378630](#): > > newer Samsung and WD drives WILL NOT erase any data when a PSID revert is issued unless a locking range is configured. PSID revert != crypto erase. Crypto erase is an NVME command that also works on some SSDs which are not TCG compliant or not SEDs at all. PSID revert is something entirely different and in itself does not necessarily wipe data. > [@anon63378630](#): > > Encryption/SED is NOT allowed on Pyrite. It is allowed but **not required**. The TCG spec is very clear on this. There are some OEMs that ship Pyrite drives with encryption. Edit: Block erase has **nothing** to do with TCG Opal or SEDs in general. You are seriously confused. --- ## Post 39 by @win11.shading291 — 2026-01-15T03:50:09Z I have a friend who was asking me this and I thought a simple wipe command would work. @AHF8329, could you provide a quick ELI5 guide on how to wipe a SDD the correct way? --- ## Post 40 by @mnalis — 2026-01-15T04:12:41Z > [@cooldude](#): > > Any other tips? I am a bit dissapointed because im worried there is no way to delete data fully without smashing it with a hammer, but I really need to sell it because I need the money so I don’t know. For somewhat out-of-box thinking, if you haven’t started using your new setup yet (assuming there is one), you can also remove and sell your new unused SSDs, and keep using your old ones. You’ll get more money back that way too. Of course, that method would have some disadvantages too. Or, if you’re going with (various) wiping methods (preferably stacking them one after another), you can always preventively try to minimize the damage in case the data is somehow recovered (e.g. at least change all your passwords and other credentials that may have been written there, enable MFA where it isn’t already etc.) --- ## Post 41 by @Birdseye999 — 2026-01-15T09:35:37Z Copy paste some random junk files until the ssd is full. --- ## Post 42 by @AHF8329 — 2026-01-15T11:20:15Z > [@win11.shading291](#): > > @AHF8329, could you provide a quick ELI5 guide on how to wipe a SDD the correct way? First, check if your SSD’s manufacturer has any management software (like Samsung Magician) that allows you to easily wipe the drive. That’ll be the easiest way. If not, you can use [Seagate’s OpenSeaChest](https://github.com/Seagate/openSeaChest) but you’ll need to use the CLI. 1. `openSeaChest_Basics --scan`and get the handle of the drive you want to wipe. 2. `openSeaChest_Basics -d --restoreMaxLB ` 3. `openSeaChest_Erase -d --showEraseSupport`and check if your drive supports any erase method marked with _(Purge)._ If not, come back here and tell us more about your setup (SSD model, OS, interface etc.) 4. Preferably use Block Erase, else use Crypto Erase or ATA Enhanced Security Erase: **Block Erase:** `openSeaChest_Erase -d --sanitize blockerase --poll --confirm this-will-erase-data` **Crypto Erase:** `openSeaChest_Erase -d --sanitize cryptoerase --poll --confirm this-will-erase-data` **ATA Enhanced Security Erase:** `openSeaChest_Erase -d --ataSecureErase enhanced --confirm this-will-erase-data` --- ## Post 43 by @cooldude — 2026-01-15T22:16:24Z Hi, I ran the proprietary Crucial Storage Executive software which has an option called “Sanitize”. As you can see here: [https://invidious.nerdvpn.de/watch?v=loUjo9w84DI](https://invidious.nerdvpn.de/watch?v=loUjo9w84DI) Around 2:00. The option here gives various options (block, and greyed out cypher and overwrite). For some reason, it didn’t give me any options, and it performed the block one by default. So basically, it took like 2 minutes. That’s it? Now my question is, how do I double check there’s nothing on the drive? Also, what this GUI application did was to run this basically? `openSeaChest_Erase -d --sanitize blockerase --poll --confirm this-will-erase-data` I want to log into Linux and inspect the drive. What commands do you recommend to run to see if everything is wiped? The drive has no partitions now. Also, what about the guide that was suggested here? > **[Data Erasure - Divested Computing](https://divested.dev/pages/data_erasure)** This guy recommended to do 1 pass of random data: `shred --iterations 1 --verbose [DRIVE]` Then he did the erase methods. I have decided to start by running the proprietary stuff on each drive, and then on top of that I want to run the Linux open source stuff just for good measure. This was an old SSD drive, not nvme. Now I need to do the Samsung nvme one, so I will get the Samsung Magician thing and see what happens. Crucial did not offer a bootable solution that I could fund, luckily it was not the OS drive. For this I will need a bootable solution. As far as crypto erase, what is the difference from block erase? From what I understood, this proprietary application by Crucial only runs Crypto Erase on drives that have hardware encryption available. And what about ATA Enhance Security Erase? Should you run all of them if available? But like I said I would like to run this with Linux too because with proprietary software you don’t really know what was performed. --- ## Post 44 by @AHF8329 — 2026-01-15T23:15:46Z > [@cooldude](#): > > So basically, it took like 2 minutes. That’s it? Yes. > [@cooldude](#): > > Also, what this GUI application did was to run this basically? Yes. > [@cooldude](#): > > As far as crypto erase, what is the difference from block erase? I already explained this in my [first post](https://discuss.privacyguides.net/t/how-do-you-safely-erase-ssds-before-selling/34650/35). > [@cooldude](#): > > This guy recommended to do 1 pass of random data: Nonsense. Don’t do it. > [@cooldude](#): > > And what about ATA Enhance Security Erase? If you were able to issue block erase or crypto erase, don’t bother. ATA Enhance Security Erase is usually for older non-Opal self encrypting drives . > [@cooldude](#): > > But like I said I would like to run this with Linux too because with proprietary software you don’t really know what was performed. Honestly, there’s really no point in doing this but if it makes you feel better, go ahead. It won’t harm your SSD. > [@cooldude](#): > > Now my question is, how do I double check there’s nothing on the drive? You could learn about data recovery, but there are different levels involved. I think the most trivial and beginner-friendly approach is using a tool like Recuva, but I can tell you that if a block erase was performed, your data is **gone for good**. --- ## Post 45 by @SwampTrainer — 2026-01-16T06:21:26Z If you’ve never looked at government auctions, they always pull the hard drives and destroy them before selling. [Including the highly paranoid U.S. government selling State department computers outside the U.S](https://online-auction.state.gov/en-US/Auction/Index/1ff4fc34-a549-4692-b281-1098cc812cdb/Category/2/Page/1). That is your fastest, safest option. Pull the SSD and destroy it – OR keep it for yourself, put it in an NVMe enclosure, and use it however you like. Destroy it or keep it. If the SSD affects the sale price significantly, then get a new, fresh one (or used similar) and install it if that makes sense and won’t cost you money. You’re already wiping the drive to the point that the new owner will have to install an OS on bare metal, so why add the stress of this? Protect yourself fully first, and let the buyer worry about getting a fresh SSD and OS. Any serious buyer will be fine with that. --- ## Post 46 by @AHF8329 — 2026-01-16T10:31:30Z > [@SwampTrainer](#): > > If you’ve never looked at government auctions, they always pull the hard drives and destroy them before selling. They are just following [NIST guidelines](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-88r2.pdf). It doesn’t make sense to apply these guidelines to the average person. When it comes to government secrets, you can’t even take a theoretical 0.0001% chance that data might be recovered with nation-state capabilities. I’m not trying to belittle your fears, but you are being overly paranoid when I can tell you that forensic companies – including those hired by governments – even struggle with non-encrypted SSDs that have simply been trimmed. For example, when you reset your iPhone or Pixel (stock Android or Graphene) device, it essentially performs a crypto erase and data from the phone itself become irrecoverable. --- ## Post 47 by @anon16689408 — 2026-01-16T10:42:59Z We need TLTR articles for this kind of important topics :slight_smile: --- ## Post 48 by @cooldude — 2026-01-16T19:35:45Z Edit: I was able to run openSeaChest as you decribed. The SSD support block, crypto and Secute ATA Enhanced. I ran block and crypto, so I think I can safely sell this drive now. I ran –scan on all the drives. I was surprised to see the NVMe does not support block or crypto of “Purge” level according to openSeaChest. `1 NVM Format: Crypto Erase (Clear, Possible Purge) ` `2 NVM Format: User Data Erase (Clear) ` `3 ATA Enhanced Security Erase (Purge) NOTE: Requires setting device password. Password cleared upon success. ` `4 ATA Security Erase (Clear) NOTE: Requires setting device password. Password cleared upon success. ` `5 Overwrite Erase (Clear)` Compared to the SSD: `1 Sanitize Crypto Erase (Purge)` `NOTE: Cannot be stopped, even with a power cycle.` `2 Sanitize Block Erase (Purge)` `NOTE: Cannot be stopped, even with a power cycle.` `3 ATA Enhanced Security Erase (Purge)` `NOTE: Requires setting device password. Password cleared upon success.` `4 ATA Security Erase (Clear)` `NOTE: Requires setting device password. Password cleared upon success.` `5 Overwrite Erase (Clear)` So what is your take on that? Do I just run the option 1 and 3 for the NVMe? I was just confused to see the difference there, as the way it’s described it sounds the SSD is better at this. --- ## Post 49 by @cooldude — 2026-01-18T17:54:17Z If anyone is interested, none of the options work for the NVMe for some reason, its all blocked. Following this guide: > For NVMe drives: > > - For these commands you want to leave off the end of the drive path. Example: `nvme0n1` becomes `nvme0` > > - First try a block erase: `nvme sanitize --sanact 0x02 [DRIVE]` > > - If that didn’t work, try a secure format: `nvme format --namespace-id 1 --ses 1 [DRIVE]` result with either block erase or secure format: `NVMe status: Invalid Command Opcode. A reserved coded value or an unsupported value in the command opcode field(0x1)` And the openSeaChest steps you mentioned return this error: `Sanitize command not supported by the device.` I don’t have Windows available right now to try their proprietary stuff so im stuck there. --- ## Post 50 by @AHF8329 — 2026-01-19T09:59:36Z > [@cooldude](#): > > I was surprised to see the NVMe does not support > [@cooldude](#): > > Compared to the SSD: What? Both are SSDs. > [@cooldude](#): > > So what is your take on that? Do I just run the option 1 and 3 for the NVMe? I feel like I am repeating myself. You can use any of the available purge methods. > [@cooldude](#): > > And the openSeaChest steps you mentioned return this error: It tells you what the problem is. The application thinks your drive doesn’t support any of the sanitation methods. But it’s actually very rare that SSDs lack any sanitization method. More likely, the issue is that you’re using a USB enclosure, and some chipsets have flaky implementations of ATA and/or NVMe passthrough. You need to tell us more about your setup. --- ## Post 51 by @SwampTrainer — 2026-01-20T05:29:40Z > [@AHF8329](#): > > I’m not trying to belittle your fears, This is more about ease of the task with guaranteed success. Pulling a SSD (or pulling and swapping for a new SSD) takes minutes and doesn’t require hours of research and asking forums what’s the right method to do it. I’ve pulled the HDD or SSD from a half dozen laptops over the years and sold or donated them without a care in the world. If I were paranoid and filled with fear, I would be pulling the RAM as well, which is just plain rude to do with a sale or donation. --- ## Post 52 by @Onscreen5341 — 2026-01-20T11:27:40Z But the OP wants to sell the SSD, not the device without the SSD.