Yes, testdisk / photorec will be the way to decide where you stand. Of course the more you have done with things from either Windows or Linux the bigger the chances that something may have by now helpfully decided to launch a TRIM run for you, and in a practical sense you may well be done for - but you may also not be, and technically/theoretically the difference HDD/SSD in a recovery context is not as big as the replied to statement implied. But most certainly I wouldn't know about a deep Windows behavioral detail like that and in any case, trouble would then not so much be due to HDD vs SSD directly but HDD vs SSD plus Windows being a pain in the ass. Now admittedly, Windows may have elected to trim that expanded filesystem immediately when resizing and in that case, yes, you are SoL. explicitly chose to zero out the expanded filesystem space AND Windows did not 'helpfully' immediately trim that now expanded filesystem, the previous not physically overwritten Linux data will be there the same on SSD as it would've been on HDD. This is to say that if poster did not e.g.

As per above garbage collection is not a factor for logical sectors not written to, and TRIM is not until you in fact trim: TRIM is an SSD drive command that an operating system calls specifically so as to have the SSD's firmware know which logical sectors are to be considered not currently occupied, but neither Linux nor Windows uses so-called 'continuous trim' by default, i.e., does not trim immediately on deleting something but relegates trimming to an e.g. But that's in a practical recovery context not a difference with an HDD where the data would've been physically overwritten immediately: data in sectors that were in fact written to is for practical recovery purposes gone on both.Īnd data in sectors that were not is not on HDD and is usually not on SSD. Only when something is in fact written to a previously occupied logical sector is an SSD's logical sector map shuffled about, and does garbage collection on an SSD know that the the bit of flash that previously underlied that logical sector is not current anymore, i.e., may be erased in the background. When you delete something on the software level, be it files in a filesystem or partitions in a partition table, the drive as such is none the wiser, be said drive an HDD or an SSD. Will is putting things far too conclusively. On a SSD, garbage collector and trim will have deleted all your data.

Linux recover lost partition