quick note on super raid trim support

this is probably being noticed but will still give you guys a heads up when raiding you msata SSDs, the newer IRST version 12.x.x.x will not have trim support for the GT70 platforms due to having an older option ROM version 11.0.0.x, however IRST version 11.7.x.x will have trim supported, on both IRST version and on both windows 7 and 8 they do both report as trim enabled when running the command on cmd: fsutil behavior query DisableDeleteNotify

However the difference is noticed when I took a closer look at verifying that trim is indeed doing what it is supposed to be doing, sending the trim commands in the OS doesn't mean the array will execute it correctly!

under this link Raid0 and TRIM Support on Intel 11.5 OROM and Latest v11.5.0.1184 RST Drivers ? - Page 3 on thread #55,
it is suggested that in order to verify that trim is properly working as in clearing the correct blocks after receiving trim command via the OS, winHex is used to compare the data values before and after deletion of an item.
In fact IRST version 11.7.x.x did execute the trim commands correctly on both OS, however when on IRST version 12.x.x.x, the data after deletion of an object, no matter I restart my computer or run the trim commands manually on windows 8 disk optimisation, is staying at the same logical block instead of showing a stream of zeros at the logical block address value.

So for users who recently updated your IRST to version 12, please kindly either revert it back to version 11, or head to the msi HQ forum and ask for a custom BIOS with latest version 12.x.x.x option rom, and for those who don't care about whether trim is enabled or not on your raid system, I wish you having a good experience on your machine

 

Running the command on cmd: fsutil behavior query DisableDeleteNotify will only let you know that TRIM is enabled and supported in the operating system.

You can run the trimcheck app to test if TRIM is actually working.
Index of /trimcheck

OR

Use this method:
www.station-drivers.com • Afficher le sujet - Tuto: Easy TRIM test method

 

a classic example of false positive reporting where cmd only verifies until a trim command is sent but not testing if the command is initiated correctly due to software conflict

 

So I have a GT70-0NE (Australian SKU version) with super raid SSD. I have IRST 11.0.0.1032 factory installed. When I run the trimcheck command it seems to take upwards of 20 minutes to get the following result indicating positive. Before that it is just failing. Should it be taking that long, and is that a reliable result? How does this compare to other GT60/70 users with superRAID SSD?

TRIM check v0.4 - Written by Vladimir Panteleev
https://github.com/CyberShadow/trimcheck

Loading continuation data from C:\Temp\trimcheck-cont.json...
Drive path : \\.\C:
Offset : 96545181696
Random data : 2F A5 E1 98 8C 2F 48 1F 6A FE 30 AA 26 1F 78 90...

Reading raw volume data...
Opening \\.\C:...
Seeking to position 96545181696...
Reading 16384 bytes...
First 16 bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00...
Data is empty (filled with 0x00 bytes).

CONCLUSION: TRIM appears to be WORKING!

Press Enter to exit...

 

What is your current os? To verify the trim commands are being sent from the os use the cmd command mentioned above, to verify that the command is properly executed in the ssd trimcheck is used, however the reason for it taking so to be verified working is due to the fact that we do not know the rate at which a trim command is sent from the os.(once the command is sent from the os it will be executed immediately and finish within milliseconds) if you are running windows 8 i recommend you manually send the trim command from the os, this can be done by right clicking on c drive, properties, 2nd tab and click into optimise and in there you can choose to defrag a hdd or optimise ssd, in which optimise ssd means sending a trim command to the disk. If trim is not functioning properly trimcheck should report it not working afterwards

Brief procedure: run trimcheck once to create a file and delete, exit, optimise disk, execute trimcheck where it verifies itself to be working or not

FOr windows 7 it will be run trimcheck once, wait 30 sec, verify trimcheck, if no trim then restart, wait for the irst traybar icn to popup with a tick, verify trimcheck again.

If both fails update irst from intel to version 11.7, that is the one i'm currently running. To find the latest irst, go to intel download center, software product, chipset software, intel rapid storage technology

 

Windows 7 I'm running. 30 second wait no joy - still takes about 20 minutes, but yes a reboot seems to produce the 'positive' result much sooner. That's great news you bring; I was worried about TRIM not working and the degradation of the disk that would come with that, but that testing seems to indicate it does work on my model. Thanks for the tip!

 

this tip worked for me too! thanks!