


Note that a multi-pass overwrite-type erase is not exactly a great idea for an SSD due to the added wear.Ĭonventional drive wiping is not considered fully effective on SSDs because they use internal memory remapping in an attempt to spread the writes evenly and extend the memory cell write lifespan. I could be mistaken there, maybe it's possible today, maybe it works over UASP (such is required to get TRIM to work, for example)? But perhaps the ntroller in the Samsung enclosure doesn't support UASP either? Sure we might have NVMe drives inside these things today and have USB 3.whatever Gen2 (whatever they have changed the name to by now 'cause they keep changing it), and sure they have very high bandwidth over such a connection (the rare times you actually have a port that is connected to something faster than standard 3.0), but pretty sure you still end up with problems like this where native commands can't be passed effectively. Anyway today since SATA itself is going way of dinosaur I guess that point about eSATA superiority is moot now. USB sucks for stuff like this because it's not a native connection-I have no idea why USB 3.0 basically killed eSATA when there's lots of disadvantages (like this) to using USB for a storage interface on things other than flash drives/memory cards. Pretty sure this is because you can't pass the Secure Erase command over USB.
