I chose the strongest erasing option under the security options.
If you are erasing an SSD, there's no need to use any software based secure erase methods.
When an ATA Secure Erase (SE) command is issued against a SSD's built-in controller That properly supports it, the SSD controller resets all its storage cells as empty (releasing stored electrons) - just THUS restoring the SSD to factory default settings and write performance. When Implemented properly, SE will process all regions Including the protected storage service regions of the half. 1
In another answer regarding SSD data recovery I write about the different methodologies used to erase data from an SSD. In short, there are two different methods for erasing data from modern SSDs:
- DRAT - All read commands after an erase command will return the same data
- RZAT - All read commands after an erase command will return zeros
...if the SSD has only DRAT capability, there is the possibility of recovering data, but it's usually in a situation where you were able to stop the deletion process and immediately start data recovery. If it implement RZAT, you can be pretty sure the recovery will only get zeros back unless they take it (along with a court order) back to the manufacturer to get a low level recovery.
In another answer (SRM gone in macOS Sierra), I detail why
srm (secure remove) is no longer an option in Sierra
On an SSD, unlike a HDD, a TRIM command is sent to wipe any data in
that marked space. This allows your SSD to be able to write data to
that marked space as if it was brand new and never used, and skip the
traditional deletion process.
How fast to erase your SSD?
I hit the erase button, and the process took about 3 seconds to
complete.... Is it supposed to be this fast?
In a very simplistic way to describe the erase process, when you issue a secure erase command (and your SSD properly implements it), it's not going to write and overwrite each sector as it were magnetic; it's going to "release the stored electrons" (as Kingston describes) and mark the space as "new and ready for use." If it employs RZAT, any read request to an address will return zeros.
I don't know of anyone who has timed the erase process of SSD; normally they test things like iops. However I do know that my 1TB SSD took less than 10 seconds to partition and setup (my first reaction was "damm that was fast"). However, as supporting documentation, from an article on Windows SSD performance2 I was able to grab this little gem:
In the article, they use Linux to force secure erase a 512GB Crucial SSD prior to installing it in a Windows machine; it did it in 9 seconds.
Your erase went fine, it's secure, and you have nothing to worry about that it did it so quickly. A secure erase command marks all data cells as "new, non active" almost instantaneously. Doing multi-pass writes to securely erase data puts undue wear on your SSD while giving you no benefit.
1 Kingston.com: SSD Data Wiping: Sanitize or Secure Erase SSDs?
2 Ultimate Windows SSD Performance Installation Guide