Windows 7 "pings" all drives in the very early stages of the Windows boot process to determine what kind of drive it is. If the response is SSD (a 0 or 1, I forget), then defragging is automatically disabled on
that drive. The user does not have to do anything.
The potential problem I see here is you have two SSDs in a RAID array. The RAID controller then needs to ensure that information is being properly supplied to the OS. Using Saltgrass' attachment as a guide, yours also should (if all is good) also show defragging was not done.
Having said all that, I do NOT recommend any sort of automatic or scheduled defragging. Period. So I recommend everyone with Windows 7 disable scheduled defragging, and anyone using a 3rd party defragger to disable real-time and scheduled defragging there too.
Why? Two reasons.
- It is counterproductive to defrag a drive with potentially 1000s of tiny temporary files on the drive. These include cookies and temporary Internet files. Therefore, you should always run a disk cleanup program (Windows own Disk Cleanup is perfectly good) BEFORE defragging. Auto (real-time) and scheduled defraggers don't "clean out the clutter" before defragging.
- You should always defrag from Safe Mode to ensure the fewest number of unmovable files are opened. When defragging from within a running operating system, there will many, many opened, and unmovable files that will impact defragging efficiency.
Also is there a way to control which drives the system is defragmenting?
Absolutely! Do it manually.
The need for a good defragger was more important years ago when drives were small, slow, and had very small buffers, and RAM was more expensive thus the Page File had a greater role on performance.
Today's drives are smarter, HUGE, fast, have large buffers and PCs are coming with gobs of RAM. So defragging is not the problem it used to be.
If you need regular defragging, then that means you do not have a big enough hard drive - one that has lots of free space for the OS and disk controller to minimize fragmentation in the first place. It does not matter that files are scattered all over the drive. What matters is the file segments are physically located close together.
Also, while there are many good 3rd defraggers, I don't feel they are necessary (especially if they cost money) and more importantly, the hype about which defragger is more efficient is really a moot point. So what if Defragger A is more efficient than Defragger B which is more efficient than Windows own native defragger? That advantage is lost, starting
immediately, the first time the computer is used again as temp files start pouring in, OS and program files are updated, and user files are created, modified, and deleted.
I defrag maybe twice a year - and that is only because in my work, I am constantly trying out (installing and uninstalling) new applications that contain many files.