Defrag/Drive Optimiser has stopped automatically trimming SSD

I think you need to read carefully what is actually scheduled to occur weekly:



The drives are only analyzed weekly, they are not optimized weekly - only as needed. Also, I notice mine were trimmed yesterday, and I did nothing to cause it to happen manually.

Hi there
I'm still mystfied as to why anybody should even think of defragging HDD's / SSD's these days. Even classical "Spinners" have decent cache sizes so there's usually no problem with picking up data wherever it's located on the disk.

SSD's have no moving parts so data access is the same wherever it's located on the disk. It's usually in some sort of 2-D array where any address access is the same all over the disk -- no heads to move etc. Modern HDD's have large cache sizes and decent "pre-fetch" algorithms -- the OS can make reasonable guesses as to what data you need next so the data is already in memory when you need it -- so the whole point of "Disk optimisation" isn't really necessary any more.

I think too many people don't understand how these days the Disk I/O subsystem and the O/S file systems actually work at the "Physical" or OS kernel level. Remember also Disk caching and "pre-fetch" can also improve the whole Disk I/O subsystem. Just forget these days the whole idea of "Disk optimisation" or defragging.

Cheers
jimbo

Trim has nothing to do with defragmentation, It's a on need basis execution that depends on uses.

TRIM is a command for the ATA interface. As you use your drive, changing and deleting information, the SSD needs to make sure that invalid information is deleted and that space is available for new information to be written. Trim tells your SSD which pieces of data can be erased.

The command is different for other interfaces, and goes by different names in different operating systems, but the action is usually referred to as "Trim". No matter what name it goes by,

Trim works with Active Garbage Collection to clean up and organize your solid state drive. Trim is beneficial, but not mandatory. Because some operating systems do not support Trim, SSD manufacturers design, create, and test their drives assuming that Trim will not be used.

Technically:
NAND flash-based SSDs read and write data in units known as pages, and in a typical SSD, 128 pages constitute a single data block. But, before any data can be written or programmed to the SSD, an entire block of data that is no longer needed must be erased. An internal SSD housekeeping operation known as garbage collection helps to streamline the process.

I my experience if trim disabled under Windows will greatly shorten life expectancy. But it will run only as needed, so 48 days is more than possible with a good wear levelling maintaining things .

Verify if trim is enabled

Code:

fsutil behavior query DisableDeleteNotify

If you receive DisableDeleteNotify = 0 then Trim is enabled and supported and will run as needed.

alexncfc said:

.......My system has an SSD as well as a standard hard drive (D:) and I am not sure why I'd get this error when it surely knows it doesn't need to run trim on a hard disk? The fact the errors are spaced out weekly suggests this is the defrag scheduler.

This silliness of MS sending trim requests to HDDs and being logged as failures in the Event Viewer has existed for months or longer now.