Ce site est optimisé pour être consulté depuis un navigateur moderne dans lequel JavaScript est activé.

Comment TRIM unallocated/unformatted space après partition shrinking on an SSD in Windows?

ayi

Comment TRIM completely unused, unallocated, unformatted, unpartitioned space (but other volumes encore exist) on an SSD in Windows 11, that used to contain data, for over provisioning? (For note: when I say "empty space" I mean space that is maintenant unallocated, unformatted, etc., not necessarily unused space in an existing volume/partition.)

J'ai cherché around and found a lot of answers for people asking similar questions about "empty space" that jamais contained anything (such as on a nouveau drive), so a TRIM is unnecessary, and that's understandable. Cependant, J'ai utilisé to have my entire SSD partitioned and formatted and had regularly nearly filled it up (certainly more than the unused space J'essaie de over provision maintenant) and seulement récemment realized il y a many benefits to over provisioning that outweigh the loss of storage space. Je n'ai pas do a TRIM avant shrinking the partition cependant, so the SSD may think il y a encore data in that maintenant "empty space".

Je suis under the assumption that TRIMing a volume (C, D, etc.) seulement applies vers le "space" (sectors/blocks, whatever) that volume occupies (or could potentially occupy, including its unused space), but ne TRIM outside that volume (presumably so c'est not TRIMing space that seulement Windows ne know about).

So, if Je veux be sure that the SSD firmware knows that space is disponible for over provisioning, how puis-je be sure it knows? Y a-t-il un command or tool to tell the SSD firmware specifically that c'est for over provisioning, or how puis-je TRIM that "empty space" (that used to be used) outside any volumes?

If il y a not a command or tool to TRIM the "empty space", would just creating a nouveau partition/volume dans le space I want for over provisioning, TRIMing that, and deleting it effectively do what I want?

ayi

Je pense what OP means to do is reserve par exemple 10% of LBA space and not do anything avec it so the drive can use it for overprovisioning. By making certain this area is trimmed you'd be certain this piece of LAB space n'est pas mapped to any physical NAND real-estate. Si vous ensuite refrain from writing data to this area, the LBA space remains un-mapped.

I do data recovery and have observed:

Deleting a partition using Disk Management ne trigger TRIM, IOW data remains recoverable (demonstration).
Creation of a nouveau partition + nouveau fichier système in this unallocated space triggers TRIM for this area (IOW the LBA range is un-mapped). Ceci est as OP assumes, vital parce que avant the firmware can use this space as it pleases it has to be made aware of this. TRIM is the command to communicate this vers le controller/firmware. Si vous want to use this space purely for overprovisioning it may be a good idea vers len simply supprimez le partition again.

Over-provisioned space is simply a percentage of NAND real-estate that n'est pas mapped to LBA. It ne matter whether this space is maintained at firmware level, by means of some sort of HPA area (c'est basically what manufacturer tools that offer an over-provisioning configuration option do) or that c'est set aside by the utilisateur for this purpose. The seulement difference is that the latter ne hide the area like HPA (host protected area) par exemple does. Cependant, by leaving/making the space unallocated après you have it trimmed, you prevent from nouveau data being written to it.

Alternatively, vous pouvez set a HPA area (on a encore unused or empty drive) using par exemple hdparm. C'est essentially the same idea: Any region du SSD that's not mapped to LBA will act as overprovisioned space.

Vous pouvez not count on writing zeros vers le area. Although trimmed LBA space usually returns zeros when you read from it, c'est purely the firmware simply returning zeros depuis it detects utilisateur is trying to read from un-mapped LBA. Ceci est different than en fait writing zeros (although on modern SSDs firmware may detect zeros and not en fait allocate physical NAND to store these, but c'est a different topic).

Any overprovisioning will contribute to par exemple prolonging SSD life time. One manufacturer trick to offer higher quality SSDs avec par exemple increased endurance, is simply increasing over-provisioned space at firmware level.