Long story short, 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. While I can't get my hands on any detailed tech specs of this drive, I would wager that it uses the RZAT TRIM command and not DRAT. Unfortunately, I haven't found detailed specs on concerning TRIM support for these particular drives (the White Paper they reference is 404). The 2016 MBP uses the SanDisk SDRQKBDC4 064G 64 GB 3 NAND which is OEM'd specifically for Apple. With drives that use RZAT, once the TRIM command is executed, the drive will return "zeros" regardless of whatever data is in that space. In drives that implement DRAT, the deleted space is marked "unused" the data "can" be recovered, to a point. From the research I have done thus far, modern SSD's use either DRAT or RZAT depending on the "quality" of the drive (higher quality generally meaning RZAT is implemented). What all of this comes down to is which type of TRIM command your hardware is capable of executing. (RZAT): All read commands to the LBA after a TRIM shall return zero. (DRAT): All read commands to the LBA after a TRIM shall return the (LBA) after a TRIM may return different data. Non-deterministic TRIM: Each read command to the Logical block address.Returned from an ATA IDENTIFY DEVICE command: There are different types of TRIM defined by SATA Words 69 and 169 Introduced a queued TRIM command to remedy this. Normal workload of queued read and write operations. Within the TRIM specification, included in SATA 3.1,Ī drawback of the original ATA TRIM command is that it was defined asĪ non-queueable command and therefore could not easily be mixed with a Keep in mind that the SATA 3.1 spec which addressed the TRIM issues wasn't released until July of 2011 The conference where this paper was presented was in Feb of 2011. Since I was the author of the answer linked, I'll have a go at explaining what's going on.įirst off, it's important to note that the study FAST referenced from the SE Information Security community, Reliably Erasing Data From Flash-Based Solid State Drives is from 2011 and now 6 years old 1.