RAID0 trim and SRT seems possible on 6-series and 5-Series

[DigitalDJ]

@ DigitalDJ:
Thanks for having tested it and thanks for your reports.
Don't your mainboard have any non-Intel SATA Controller?

It does, but it is full of drives in RAID5. Nevertheless, I rebuilt the array with 12.5 RST PCI OPROM, then reflashed the BIOS with just the inserted 12.5 SataDriver (patched for Z68) and removed the PCI OPROM.

TRIM still does not passthrough with Windows 8 EFI (with RST 12.0 driver)

 

[Fernando 1]

I inserted the SataDriver using MMTool. I simply selected the "Insert" tab, chose the modded SataDriver and added it with the same "Vol. Index" as CSMCORE (01 in my case) and had the "Insert As Is" option. It ends up being the last module under Volume 01 (Volume 01, Index A0 in mine) with the same 90C8D394...etc GUID. I then Deleted 8086,2822 PCI OPROM, also using MMTool.

AFAIK the SataDriver file ist stored within the BIOS in compressed form. If I am right, you should have inserted the SataDriver.ffs file with the option "Insert Compressed".

TRIM still does not passthrough with Windows 8 EFI (with RST 12.0 driver)

Since the Intel OROM/driver versions v12.5 are are much different from the previous versions, you may try the v12.0 SataDriver/driver combination.

 

[DigitalDJ]

The driver I have isn't compressed. It's uncompressed....and all the strings are visible. If it were compressed, I'm pretty sure you couldn't edit the device IDs without decompressing it first? I don't think it matters whether you insert the module as compressed, as long as it fits with the 8MB capsule and you aren't compressing an already compressed driver. If it's executed (and therefore it shows up in the BIOS menu), it definitely shouldn't matter.

12.5 and 12.0 OPROMs are actually _very_ similar. Very few differences, which is also why the 12.5 OPROM reportedly works with the 12.0 Drivers. I disassembled it to confirm. The drivers however, are very different. Nevertheless, even 12.0 SataDriver with 12.0 drivers does not enable TRIM.

 

[Fernando 1]

The driver I have isn't compressed. It's uncompressed....and all the strings are visible. If it were compressed, I'm pretty sure you couldn't edit the device IDs without decompressing it first?

That is correct.

I don't think it matters whether you insert the module as compressed, as long as it fits with the 8MB capsule and you aren't compressing an already compressed driver. If it's executed (and therefore it shows up in the BIOS menu), it definitely shouldn't matter.

I am not sure regarding this point.
All I know is, that the SataDriver module of the original BIOSes is compressed and the SataDriver works fine, if it has been inserted in compressed form. (look >here<).

Nevertheless, even 12.0 SataDriver with 12.0 drivers does not enable TRIM.

I can not confirm this statement.
Since I have installed Win8 x64 in UEFI mode onto my Intel Z77 RAID0 system, I have tested it with both SataDriver and RST(e) driver versions v12.0 and v12.5.
Result:
TRIM is working within my RAID0 with all available EFI "SataDriver"/RST(e) driver version combinations from v11.7 up, with the only exception, that the Intel RST(e) drivers v12.5.0.1066 do not support TRIM in RAID0 at all (AHCI systems show full TRIM activity even with these drivers).

 

[DigitalDJ]

That is correct.
I am not sure regarding this point.
All I know is, that the SataDriver module of the original BIOSes is compressed and the SataDriver works fine, if it has been inserted in compressed form. (look >here<).
I can not confirm this statement.
Since I have installed Win8 x64 in UEFI mode onto my Intel Z77 RAID0 system, I have tested it with both SataDriver and RST(e) driver versions v12.0 and v12.5.
Result:
TRIM is working within my RAID0 with all available EFI "SataDriver"/RST(e) driver version combinations from v11.7 up, with the only exception, that the Intel RST(e) drivers v12.5.0.1066 do not support TRIM in RAID0 at all (AHCI systems show full TRIM activity even with these drivers).

I also tried compressed form but no go. While I understand it works with BIOSes that already have the SataDriver inserted, adding it yourself doesn't seem to work straight off the bat. Something is missing I think. Now that garikfox has updated the Z68 with inserted SataDriver, I'll keep an eye on the other thread to see if anyone is actually successful with it. So far, doesn't seem like it....probably because of the inability to disable CSM.

 

[RYU_KEN]

Hi guys, I followed the steps to update the BIOS on my
P7P55D and everything seems to work, Option ROM 12.5.0.1815 and RST driver 12.0.0.1082 tested trimcheck_0.4, just that sometimes when I launch it says that TRIM does not work, then re-launch after a while and says it seems to be working, is this normal?

 

[Fernando 1]

@ DigitalDJ:
Today I have done the following:

1. I inserted the "SataDriver" module v12.5.0.1815 (with enabled TRIM in RAID0 function for Z68 systems and corrected checksum) as compressed file into the actual BIOS of my old P8Z68-V.
2. Then I flashed this modded BIOS into the BIOS chip of my formerly used system (MB: ASUS P8Z68-V, RAID0: 2x128 GB Crucial M4, OS: Win8 x64).
   By the way: The RAID had been freshly created recently with my Z77 system in UEFI mode using the SataDriver v12.5.0.1815. The OS had been installed there as well.
3. At least I have done some BIOS settings ("SATA mode": "RAID", "Option ROM Messages" > "Keep Current" and the needed "Boot Options Priorities")

Everything worked fine. Surprisingly I was even able to boot into Win8 x64 without getting the usual RAID boot delay (no Ctrl+I screen).
But: I was not able to see and to enter the "Intel(R) Rapid Storage" section of the BIOS.
UPDATE:
Obviously I made a mistake (forgot to turn off completely the power for a few minutes after having flashed the new BIOS).
Meanwhile the user ney2x succeeded with the insertion of the "SataDriver" module into the BIOS of his P8Z68-V and everything worked fine after having flashed this modified BIOS. He was able to create a new RAID0 array by using the new "Intel(R) Rapid Storage" BIOS tab and to do a fresh Win8 install in UEFI mode onto the RAID. Here< is his detailled report.

@ RYU_KEN:
The TRIM activity within the RAID array depends not only on the in-use LEGACY/UEFI RAID module and the RAID driver, but on the SSD sort and firmware as well.
This may explain the different results of the TRIM tests and the delay of the TRIM detection.

 

[RYU_KEN]

@ DigitalDJ:

Today I have done the following:

1. I inserted the "SataDriver" module v12.5.0.1815 (with enabled TRIM in RAID0 function for Z68 systems and corrected checksum) as compressed file into the actual BIOS of my old P8Z68-V.
2. Then I flashed this modded BIOS into the BIOS chip of my formerly used system (MB: ASUS P8Z68-V, RAID0: 2x128 GB Crucial M4, OS: Win8 x64).
   By the way: The RAID had been freshly created recently with my Z77 system in UEFI mode using the SataDriver v12.5.0.1815. The OS had been installed there as well.
3. At least I have done some BIOS settings ("SATA mode": "RAID", "Option ROM Messages" > "Keep Current" and the needed "Boot Options Priorities")

Everything worked fine. Surprisingly I was even able to boot into Win8 x64 without getting the usual RAID boot delay (no Ctrl+I screen).
But: I was not able to see and to enter the "Intel(R) Rapid Storage" section of the BIOS.
My conclusion: The insertion of a SataDriver module into an UEFI mode capable BIOS without such module is possible, but doesn't make much sense, if the support by other BIOS components is missing.

@ RYU_KEN:
The TRIM activity within the RAID array depends not only on the in-use LEGACY/UEFI RAID module and the RAID driver, but on the SSD sort and firmware as well.
This may explain the different results of the TRIM tests and the delay of the TRIM detection.

Ok thanks for the help, now that he has stabilized seems to work well, the tests I had done yesterday maybe it was just formatted for that too, maybe windows had other priorities to TRIM sorry for english

 

[MaxICH]

@Fernando 1

I read on your orom page that the RST drivers v12.5.0.1066 do not allow Trim on RAID 0 anymore. For a Z68 Asus board, do you suggest going with:

- Orom v12.5.0.1815 with RST 12.0.0.1083
- Orom v12.0.0.1783 with RST 12.0.0.1083

Thanks!

 

[Fernando 1]

I read on your orom page that the RST drivers v12.5.0.1066 do not allow Trim on RAID 0 anymore. For a Z68 Asus board, do you suggest going with:
- Orom v12.5.0.1815 with RST 12.0.0.1083
- Orom v12.0.0.1783 with RST 12.0.0.1083

Yes, both combinations are good and will bring the TRIM command into the RAID0 array.
Precondition for Z68 users: The Intel RAID ROM module has to be modified according to this thread.

 

[MaxICH]

Yes, both combinations are good and will bring the TRIM command into the RAID0 array.
Precondition for Z68 users: The Intel RAID ROM module has to be modified according to this thread.

Thanks! I went with 12.5.0.1815 / 12.0.0.1083 and confirmed that Trim is still working on my raid0.

I want to mention that I also tried to insert the "SataDriver" FFS module following your instructions, but after setting the ROM priority to "EFI Compatible Rom" (as per ney2x guide) I wasn't able to get back in the bios and got stucked at the Asus splash screen.

At first I thought there was something wrong with the bios I modded, but after reverting back to a previous version, I realized that it was a compatibility issue with my GTX Titan. Apparently the Titan also uses a UEFI bios and some motherboards require a bios update in order to work properly with it.

Anyway, long story short, the current BIOS 3603 for the P8Z68-V Pro will not post correctly if the ROM priority is set to "EFI Compatible Rom" and a Titan is present regardless of the RST orom used. No problem with "Legacy Rom".

 

[ney2x]

@MaxICH

You should request for a vga bios with UEFI GOP with the manufacturer (MSI, EVGA, etc.)

 

[MaxICH]

@MaxICH

You should request for a vga bios with UEFI GOP with the manufacturer (MSI, EVGA, etc.)

I believe the GTX Titan is UEFI GOP. The problem is the BIOS for the P8Z68, which doesn't officially support Windows 8 fast / secure boot. I'm sure it's an artificial limit imposed by Asus just to make Z77 boards more appealing, just like raid 0 trim used to be

No big deal really. Maybe some smart guy will figure out a hack for it.

 

[razvan_n]

Anyone happened to have done already the mod for Gigabyte GA-P67A-D3-B3 v1.0?

I'd like to see how it moves with two Corsair Force GTs (120 GB) hooked on SATA3 in RAID0...

 

[jackwhitter]

@fernando & @dufus: Thanks so much for all your hard work! i got trim working on a p55m-ud2 with raid 0 samsung SSDs with all your help and guides! rocking job!

THANKS!

 

[darkcurrent]

I just want to give a BIG THANKS to Fernando and Dufus

You guys are awesome and incredibly smart.

I just got this working on a Z68X-UD4-B3 and checked with trimcheck that trim is works with raid 0.

Thanks again and awesome work guys!

 

[VirtualLarry]

Intel seem to like to hold their cards very close while often it seems remaining in silence. With the currently available OROM's as is, trim is only available on 7 series, excluding X79, so their position IMO would likely to be to say only that 7-series is "supported" without any further information such as "we plan to add support for earlier chipsets" or "we are not going to support any earlier chipsets. IMHO this leaves people not knowing what is really going on and resulting in speculation and for me, why I felt it necessary to see if trim was even possible on the earlier chipsets.

Intel is REALLY BAD about downrev platform "feature support". Clearly, they like to artificially differentiate platforms in software, in order for the sheeple to always upgrade their platforms.

I'm still on P35/ICH9R, and I wish I could get TRIM in RAID-0. There hasn't been an OROM update for my board though, so I guess I'm on some 10.x OROM version.

 

[Fernando 1]

I'm still on P35/ICH9R, and I wish I could get TRIM in RAID-0. There hasn't been an OROM update for my board though, so I guess I'm on some 10.x OROM version.

Even if you would flash a BIOS with an updated Intel RAID ROM (v11.x or v12.x), there would be no chance to get TRIM working within your RAID0 array.
I doubt, that Intel will ever release a RAID ROM module, which can be modified to support TRIM in RAID0 for earlier chipsets than the 5-Series.

 

[Makaveli]

Even if you would flash a BIOS with an updated Intel RAID ROM (v11.x or v12.x), there would be no chance to get TRIM working within your RAID0 array.
I doubt, that Intel will ever release a RAID ROM module, which can be modified to support TRIM in RAID0 for earlier chipsets than the 5-Series.

Yep I found this out the hard way. I cannot load any higher roms than 10.0.0.8 version due to the rom size limitations discussed earlier in this thread.

I doubt we will ever see TRIM support on X58 and anything older.

 

[DigitalDJ]

So, it seems my earlier thoughts about Z68, EFI and TRIM were slightly incorrect.

I recently upgraded to 2x Samsung 840 PRO 256GB and did a fresh install of Windows 8 EFI. Still using an ASUS P8Z68 DELUXE

TRIM works with EFI SataDriver! HOWEVER only if I remove the BIOS OPROM from CSMCORE.

If I leave the OPROM in the BIOS, TRIM _does not_ work. Unfortunately, this means whenever I want to modify a RAID array, I need to reflash since EFI RST module does not allow me to create an array, only delete and view its details.

At the moment I'm using options "Keep Current" and prioritize "EFI Compatible ROM". Everything works great.

I swear I had tried this with my Vertex 3 MAX IOPS drives...so maybe the issue is with them rather than it being Z68+EFI

 

[Dufus]

Unfortunately it seems Intel may have decided after all to drop supporting pre 7 series. :\

With the way the OROM is currently modified it does not work to give trim for pre PCH. I had hoped to do some further tests with X58 and earlier using a different mod but could not find anyone willing to flash and test so kind of gave up on that.

For pre 7 if using the ASUS board with RAID UEFI BIOS driver you could try right or left tabbing in the BIOS setup to see the UEFI RAID config. Failing that it might be possible to run an UEFI shell and the EFI RAID config program that is available with some of the Intel packages.

BTW didn't get SRT working on the P55, only P67.

 

[Fernando 1]

@ DigitalDJ:
Which Intel EFI SataDriver version brought TRIM into your Z68 RAID0 array and which Intel RAID ROM version didn't?

@ Dufus:
Thank you very much for your last statement regarding the TRIM in RAID0 support of Intel's pre-PCH chipsets.
Did you already have the time to make some tests with any of the v12 RAID ROM modules and the related RAID drivers?
It seems to me, that Intel has changed the TRIM in RAID0 support mechanism.

 

[Makaveli]

I had hoped to do some further tests with X58 and earlier using a different mod but could not find anyone willing to flash and test so kind of gave up on that.

What test were those ?

 

[DigitalDJ]

@ DigitalDJ:
Which Intel EFI SataDriver version brought TRIM into your Z68 RAID0 array and which Intel RAID ROM version didn't?

I used SataDriver 12.6.0.1867 with 12.6.0.1033 drivers. However, now I'm running 12.7.0.1910 SataDriver (which I patched myself) with 12.6.0.1033 drivers, no OROM and everything is still working OK.

I went back and took the Vertex 3 MAX IOPS out of RAID0, and tried trimcheck on it, but it still does not seem to clean up after itself...even after a reboot. I think there's something iffy with these particular drive's firmware......since they do actually support TRIM.

 

[Dufus]

Did try the earlier 12 series but 11.2 legacy still seems better for my own needs even if it means a slower boot without UEFI GOP and UEFI RST driver.

What test were those ?

Hard to remember now, some register info, also tried making up a modified OROM but I have no suitable HW to test on. For instance IIRC ASUS P6T Deluxe V2 BIOS with modified 11.x OROM. Not really knowing what the outcome might be I can understand peoples reluctance to test.