Defraggler + SSD raid 0

klepp0906 said:

So i've lived with this for alotta years. Its now on my short list of "things that irk me" to sort out.

Ive waited iteration after iteration for piriform to sort it out. I've installed driver after driver for my raid controller. Different versions of windows. The problem still exists.

If i try to run windows optimize it will give me the trim option for my raid 0 setup. Defraggler however only gives me defrag/quick defrag.

How can I make defraggler see my ssd raid as ssd and offer optimize/trim? Any way to force this since it seems incapable on its own?

anyone else in a similar situation or has been and been able to solve it?

Honest answer? Throw it away. The MS Optimize is all you need.

klepp0906 said:

lol yea. Its one of those rare cases where ms shines. including marvell controller drivers but thats another discussion alltogether ;p

if no resolution is available (hoping a config file exists i can change a 0 to a 1) then thats what ill have to do. Thats what ive been doing for many moons. Just anal as all hell i suppose. Some inner experience has taught me that third party must in some way always be superior or it wouldnt exist I guess. Habit maybe? who knows. Likely the same reason ive avoided the dentist for 20 years but times they are a changin :P

Some 3rd party have good extra features and/or easier to use, but not this time. A Trim command is a Trim command is a Trim command. :)

f14tomcat said:

Some 3rd party have good extra features and/or easier to use, but not this time. A Trim command is a Trim command is a Trim command. :)

Exactly.
All it does is let the OS tell the SSDs controller which blocks of data are no longer considered in use and can be wiped internally.
Nothing more.
Then the controller decides when and what is best reset back to zero(or isn't it one with an SSD)

https://en.wikipedia.org/wiki/Trim_(computing)

RAID issues[edit]

As of January 2017^[update], support for the TRIM command is not implemented in most hardware-based RAID technologies. However, software RAID implementations often do include support for TRIM.
Windows:
Windows 10 offers support for TRIM in SSD RAID volumes using the "optimize drives" option when configuring a RAID volume.
Mac OS:
The macOS RAID driver does not support TRIM. This is true for all versions of Mac OS X from 10.7 through macOS 10.12.x.
TRIM is supported for RAID (0,1,4,5 & 10) volumes when using the third-party SoftRAID® application, including TRIM support with non-Apple SSD devices. (Note: TRIM for non-Apple SSD devices must be specifically enabled using the terminal command "sudo trimforce enable")
Linux:
TRIM is available with RAID volumes in post-January-2011 releases of the Linux kernel's dmraid, which implements BIOS-assisted "fake hardware RAID" support, and which now passes through any TRIM requests from the filesystem that sits on the RAID array.^[43]
Not to be confused with dmraid, Linux's general-purpose software RAID system, mdraid, has experimental support for batch-based (rather than live, upon file deletion) TRIM on RAID 1 arrays when systems are configured to periodically run the mdtrim utility on filesystems (even those like ext3 without native TRIM support).^[44] In later versions of Linux, e.g. Red Hat Enterprise Linux 6.5 and beyond, mdraid supports actually passing through TRIM commands in real-time, rather than just as a batch job.^[45]
However, note that Red Hat recommends against using software RAID levels 1, 4, 5, and 6 on SSDs with most RAID technologies, because during initialization, most RAID management utilities (e.g. Linux's mdadm) write to all blocks on the devices to ensure that checksums (or drive-to-drive verifies, in the case of RAID 1 / 10) operate properly, causing the SSD to believe that all blocks other than in the spare area are in use, significantly degrading performance.^[46]
On the other hand, Red Hat does recommend the use of RAID 1 or RAID 10 for LVM RAIDs on SSDs, as these levels support TRIM ("discard" in Linux terminology), and the LVM utilities do not write to all blocks when creating a RAID 1 or RAID 10 volume.^[45]
For a short time in March 2010, users were led to believe that the Intel Rapid Storage Technology (RST) 9.6 drivers supported TRIM on RAID volumes, but Intel later clarified that TRIM was supported for the BIOS settings of AHCI mode and RAID mode, but not if the drive was part of a RAID volume.^[47]
As of August 2012, Intel confirms that 7-series chipsets with Rapid Storage Technology (RST) 11.2 drivers support TRIM for RAID 0 in Microsoft Windows 7.^[48] While Intel did not confirm support for 6-series chipsets, TRIM on RAID 0 volumes has been shown to work on Z68, P67, and X79 chipsets by hardware enthusiasts with a modified RAID option ROM.^[49] It is speculated that the lack of official support for 6-series chipsets is due to validation costs^[50] or an attempt to encourage consumers to upgrade,^[51] rather than for technical reasons.
An exception to the need for a modified option ROM on motherboards with an X79 chipset is if the manufacturer has added a ROM switch; this entails both the RST and RST-E ROMs being inside the BIOS/UEFI. This allows the RST ROM to be used instead of the RST-E ROM, allowing TRIM to function.^[52] Intel notes that best performance can be achieved by using a driver with same version as the ROM; for example, if the BIOS/UEFI has an 11.0.0.0m option ROM, an 11.x version driver should be used.^[53]

There are some third party software that unfortunately do not go the extra mile to distinguish properly between hard drives and SSDs, people with SSD should not use these programs. As above I recommend the built in optimiser. Its all you need.