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

[Fernando 1]

Which SataDriver module did you insert: the original file or that one i had modified for TRIM with P67+Z68 chipset RAID0 systems?

Yes.

What means "Yes", the first or the second option?

It seems I can't do that, my bios doesn't have the Rapide Storage tab. Probably because it's a beta bios. On the other hand, at least they are releasing new things for my Z68 board...

Do you see within the "Boot" section of the BIOS any CSM settings? If yes, you should use "Auto" or "Disabled". After a reboot you may find the "Intel(R) Rapid Storage" section of the EFI BIOS.

 

[john-117]

What means "Yes", the first or the second option?

Yeah, I didn't make much sense :whiste: I used the file you modded.

Do you see within the "Boot" section of the BIOS any CSM settings? If yes, you should use "Auto" or "Disabled". After a reboot you may find the "Intel(R) Rapid Storage" section of the EFI BIOS.

CSM has two settings, Always and Never. But even if I set it to Never, it returns to "Always" after every reboot. Could it be the graphics card isn't compatible with the UEFI bios?

 

[Fernando 1]

Yeah, I didn't make much sense :whiste: I used the file you modded.

So you got this modded BIOS working?
The reason why you didn't get TRIM support within your RAID0 is the fact, that your RAID Controller doesn't use the modded "SataDriver" module, since you are not running your OS in clean EFI mode. If the SataDriver module would have been in use, you would see the big "Intel(R) Rapid Storage" Utility tab within the UEFI BIOS.

CSM has two settings, Always and Never. But even if I set it to Never, it returns to "Always" after every reboot. Could it be the graphics card isn't compatible with the UEFI bios?

Probably it's the graphics card.
Try the following, provided your CPU has an Intel HD graphics chip:
1. Remove your graphics card.
2. Enter the BIOS and set the "CSM" to "Never".
3. Reboot and enter the BIOS again. Now you should see the "Intel(R) Rapid Storage" tab.

 

[john-117]

So you got this modded BIOS working?
The reason why you didn't get TRIM support within your RAID0 is the fact, that your RAID Controller doesn't use the modded "SataDriver" module, since you are not running your OS in clean EFI mode. If the SataDriver module would have been in use, you would see the big "Intel(R) Rapid Storage" Utility tab within the UEFI BIOS.

Yes, but when I open IRST from windows, go to help/system report, you can see which raid rom is used, right? When I used your modified file, I could see v12.0.0.1783. There was an option in the bios to use the legacy raid rom. When I did that, I found I was using v11.2 raid rom.

Probably it's the graphics card.
Try the following, provided your CPU has an Intel HD graphics chip:
1. Remove your graphics card.
2. Enter the BIOS and set the "CSM" to "Never".
3. Reboot and enter the BIOS again. Now you should see the "Intel(R) Rapid Storage" tab.

It was the graphics card. I swapped my card with a newer EFI compliant one (7870 XT Joker) and CSM would stay on "Never". However, I cant find the IRST tab in the bios. It's a beta bios, they broke mouse support with the current beta (version K), so there may be some bugs. It seems stable however.

 

[Fernando 1]

Yes, but when I open IRST from windows, go to help/system report, you can see which raid rom is used, right? When I used your modified file, I could see v12.0.0.1783.

That indicates, that the SataDriver really is in use.
Can you open the Utility from within the RST Console software?

 

[john-117]

That indicates, that the SataDriver really is in use.
Can you open the Utility from within the RST Console software?

I think so, but Windows are currently running from the Raid volume. Maybe I can boot Windows from another disk, and create the raid array from Windows. Worth a try...

Also an indication that SataDriver is working is the speed difference when booting.

 

[Fernando 1]

I think so, but Windows are currently running from the Raid volume. Maybe I can boot Windows from another disk, and create the raid array from Windows. Worth a try...

That is not a good idea.
If you want the best performance, you should install the OS and the bootloader onto the RAID0 array.

Also an indication that SataDriver is working is the speed difference when booting.

Yes, that is an indication, that the EFI RAID Utility is working, but unfortunately you don't have access to it.
Maybe you should flash the BIOS, which I have modified today. It contains the SataDriver v11.6.0.1702 with enabled TRIM in RAID0 support. Contrary to the BIOS you are using now the included SataDriver has the same GUI code as the original SataDriver module of the BIOS. Maybe this will solve you problem regarding the direct access to the EFI RAID "SataDriver" Utility.

 

[john-117]

Fernando, is there a modified efi raid rom for Z68 users? The newer version, 12.0.0.1783.

I can now report that using the modified efi 11.6 raid rom, trim does not seem to work with my Vertes 3 Max Iops drives.

However, I have observed something strange. When I was using an unmodified raid rom, optimising the drives (Windows 8) would complete instantly. With the modified raid rom, the hard drive light stays on for ~10 seconds, maybe it is doing something.

 

[Fernando 1]

Fernando, is there a modified efi raid rom for Z68 users? The newer version, 12.0.0.1783.

According to >this< message you have already tested it.

I can now report that using the modified efi 11.6 raid rom, trim does not seem to work with my Vertes 3 Max Iops drives.

How did you verify, that it doesn't work?

However, I have observed something strange. When I was using an unmodified raid rom, optimising the drives (Windows 8) would complete instantly. With the modified raid rom, the hard drive light stays on for ~10 seconds, maybe it is doing something.

The Win8 "Optimizer" (formerly named "Defrag Tool") does nothing else than to send TRIM commands into the related SATA Controller, but you don't know, if TRIM passes through it.
When the Optimizer finishes its work immediately, this means either, that there was nothing to be cleaned, or, that the TRIM command didn't have any effect. I think, it was the latter - no TRIM support within the RAID0 array.

 

[joe_967]

Hi Folks,

I downloaded a modded bios for my p868-v Gen3, and the raid screen on boot up confirms Option ROM 11.6.0.1702.

I then set up my Raid 0 array using 2 128gb OCZ Vector drives. I installed windows 8, and also installed Intel RST version 11.7. (in that order)

Here's the deal, using the Hex editor test, it seems that Trim is not working for me.

I've run the windows experience update, and the drive optimizer tool.

Any help would be very appreciated,

 

[Fernando 1]

I downloaded a modded bios for my p868-v Gen3, and the raid screen on boot up confirms Option ROM 11.6.0.1702.

Where did you get the "modded" BIOS and who had modified it??
Since Intel's original Option ROM v11.6.0.1702 doesn't support TRIM in RAID0 for Z68 chipset systems, the inserted Intel RAID ROM module has to be especially modified.

 

[joe_967]

Hi Fernando,

First of all thanks fo taking to time to respond, I appreciate the effort you're putting in here.

I downloaded the modded bios from here: http://www.overclock.net/t/1244232/asus-asrock-bioss-with-updated-raid-orom

Any direction/advice you can provide from here would be greatly appreciated.

Thanks again.

 

[Fernando 1]

I downloaded the modded bios from here: http://www.overclock.net/t/1244232/asus-asrock-bioss-with-updated-raid-orom
Any direction/advice you can provide from here would be greatly appreciated.

What do you expect from my side?
I neither have modded the BIOS for you nor did I look above your shoulders while you were testing if TRIM is working or not.

 

[joe_967]

Hi Fernando, I suppose I should start over and not rely on a third party bios. I have downloaded the most up to date bios, but I will admit the link here is a bit intimidating. Would you be able to lend assistance and help me determine which orom I should be using from here?

http://www.win-lite.de/wbb/board208...m-modules-for-bios-modding-already-extracted/

I'm thinking that it should be:

>Especially modified Intel RST(e) RAID ROM v11.6.0.1702 with TRIM in RAID0 for P67 and Z68 systems< (for DEV_2822/282a with an Alternate Device IDs 1C04 or 1C06, can be verified by >this< tool, credits go to Dufus, for details look >here<)

Thanks again.

 

[Fernando 1]

Hi Fernando, do you know if there is a reliable version of this bios available for download?

Why don't you modify the BIOS yourself?
>Here< is my BIOS modding guide and >here< you will find the Intel RAID ROM v11.6.0.1702, which has been modified by me by enabling the TRIM in RAID0 support for P67/Z68 chipset mainboards.

EDIT:

I'm thinking that it should be:
>Especially modified Intel RST(e) RAID ROM v11.6.0.1702 with TRIM in RAID0 for P67 and Z68 systems< (for DEV_2822/282a with an Alternate Device IDs 1C04 or 1C06, can be verified by >this< tool, credits go to Dufus, for details look >here<)

Yes, that is it.

 

[joe_967]

Thanks, I think I have it working.

 

[Fernando 1]

Today the user asder00 has published at station-drivers (>LINK<) brandnew Intel RST(e) drivers v12.5.0.1066 WHQL dated 03/22/2013 and the related Intel LEGACY RAID ROM and EFI "SataDriver" modules v12.5.0.1815.
After having done a deeper look into the LEGACY RAID ROM and the EFI SataDriver module with a hex editor I found some interesting differences in comparison to the previously released BIOS modules:

1. The TRIM in RAID section of the modules is much bigger sized. There obviously has been added more than just the TRIM in RAID0 hex codes for the upcoming 8-Series SATA RAID Controllers.
2. Intel has changed the "TRIM in RAID0" FLAGS for X79 chipset systems from "07" to "17", whatever this may mean.

Here is a screenshot with the highlighted TRIM in RAID0 section of the Intel RAID ROM v12.5.0.1815:

 

[Stress]

@ Fernando:

I also noticed the increased size of the look-up table and trim flags change. I wonder if Dufus has an opinion about this.

I modified the look-up table (using 07 for the trim flag) and with this modified 12.5.0.1815 option rom for my Asus P7P55D-E LX motherboard, using RST 12.5.0.1066, trim does NOT appear to be working as reported by the trimcheck tool. However trim was working as reported by the trimcheck tool for RST 12.0.0.1083 for the modified 12.5.0.1815 option rom.

I checked again and the trimcheck tool reports that trim does appear to be working for the modified 12.5.0.1815 option rom for the raid0 array on my Asus P7P55D-E LX motherboard using RST 12.5.0.1066. Perhaps I had not waited long enough for the trim check.

 

[davidm71]

Hi,

So Intel removed Trim support for non-Z77 chipsets with the 12.5.0.1815 modded orom? Seems like the caught on to this hack and stopped it?

David

 

[DigitalDJ]

Fernando,

Could you briefly outline how you are able to circumvent the integrity checks on the SataDriver EFI module? And what process you use to patch and replace the SataDriver?

I have been reading up thoroughly on both yours and Dufus' information about RST and have been trying to get TRIM working on a Z68 board (with Windows 8 booted in EFI). I'm well aware no one has got this to work yet (or have they?!)

However, I _think_ I have made progress, I'll try and keep this simple:
(I have avoided using 12.5 due the reported problems with TRIM)

1) I have an ASUS P8Z68 DELUXE (BIOS v3603) - It does not have SataDriver by default
2) I have modified the BIOS by inserting the STOCK/ORIGINAL 12.0 SataDriver EFI module using (MMTool).
3) The RSI EFI module SHOWS in the Advanced Mode BIOS menu (if you keep hitting the Right Arrow).
4) If both the OPROM and EFI module are in the BIOS, RST will default to the legacy PCI OPROM. I verified this by Winodws RST > Help > System Report, and using an 11.6 OPROM and 12.0 EFI module.
5) If you DELETE the PCI OPROM from the BIOS, RST will use the EFI SataDriver! (System Report now shows it is using 12.0 RAID option ROM version).

The problem now is that whenever I try and modify the SataDriver EFI module for Z68 (06 1C 00 00 01 => 06 1C 00 00 07), the menu is no longer available in the BIOS. I read earlier in this thread that there are some integrity checks to bypass, but I have not worked this out.

I have tried using PhoenixTool to extract the SataDriver, without the EFI FFS wrapper, patching it, then letting PhoenixTool re-insert with a recalculated FFS integrity check....but this isn't working for me.

Please help

 

[DigitalDJ]

Ahhhhhh.

I ended up getting a modded SataDriver inserted. I wrote a script that recalculates the EFI FFS Checksum. MMTool accepted the file and the modded SataDriver shows up the BIOS menu.

Unfortunately, even though I have the modded SataDriver 12.0 and RST (in Windows) reports 12.0 OpROM (has to be EFI because there is no PCI one...).....I cannot get TRIM to work

Maybe it would work if I rebuild the array? Reverted to Windows 7 EFI? Perhaps EFI/Z68/RAID0 TRIM aren't meant to be.

 

[Fernando 1]

Fernando,
Could you briefly outline how you are able to circumvent the integrity checks on the SataDriver EFI module?

Contrary to the ROM modules the Intel EFI "SataDriver" has an internal checksum control system.
After a lot of work I found out, that it chooses the checksum-8 algorithm of the complete file. This checksum-8 code is layed down in the offset 10 at place 07 (exampe: it is "07" for the original SataDriver.ffs file v12.5.0.1815).
As a consequence you have to correct the checksum-8 after the modification to the exact code, which is layed down within the module at the location I have mentioned.

And what process you use to patch and replace the SataDriver?

When you know the checksum algorithm and the place, where it is stored, it is not a big problem to avoid the "invalid FFS file" message while trying to insert or to replace the SataDriver module into the BIOS.

1) I have an ASUS P8Z68 DELUXE (BIOS v3603) - It does not have SataDriver by default
2) I have modified the BIOS by inserting the STOCK/ORIGINAL 12.0 SataDriver EFI module using (MMTool).

Where and how did you insert the SataDriver module?
The GUID of the SataDriver module is layed down at the beginning of the offset and should be shown by the MMTool after the insertion.

Unfortunately, even though I have the modded SataDriver 12.0 and RST (in Windows) reports 12.0 OpROM (has to be EFI because there is no PCI one...).....I cannot get TRIM to work

Which Intel RST(e) drivers did you install?
Some users at German Win-Lite found out, that the Intel RST(e) drivers v12.5.0.1066 do not support the TRIM in RAID0 feature at all, whereas the Intel RAID ROM and the Intel EFI "SataDriver" module definitively do support TRIM in RAID0 for Z77 chipsets. You can find this discussion >here<.

 

[DigitalDJ]

Contrary to the ROM modules the Intel EFI "SataDriver" has an internal checksum control system.
After a lot of work I found out, that it chooses the checksum-8 algorithm of the complete file. This checksum-8 code is layed down in the offset 10 at place 07 (exampe: it is "07" for the original SataDriver.ffs file v12.5.0.1815).
As a consequence you have to correct the checksum-8 after the modification to the exact code, which is layed down within the module at the location I have mentioned.
When you know the checksum algorithm and the place, where it is stored, it is not a big problem to avoid the "invalid FFS file" message while trying to insert o to replace the SataDriver module into the BIOS.
Where and how did you insert the SataDriver module?
The GUID of the SataDriver module is layed down at the beginning of the offset and should be shown by the MMTool after the insertion.

Which Intel RST(e) drivers did you install?
Some users at German Win-Lite found out, that the Intel RST(e) drivers v12.5.0.1066 do not support the TRIM in RAID0 feature at all, whereas the Intel RAID ROM and the Intel EFI "SataDriver" module definitively do support TRIM in RAID0 for Z77 chipsets. You can find this discussion >here<.

Thanks for the reply! I worked out the checksum thing shortly after my original post. But thanks for the double clarification

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.

The end result was that when entering the BIOS Setup, it was possible to get to the RST EFI menu. Windows booted, but even with the 12.0 (not 12.5!) driver, TRIM was unsuccessful. I can only assume that it was using the EFI SataDriver since there was no longer a PCI OPROM in the BIOS.

As an aside, I found that via the EFI RST Menu, I was able to delete an array...but was not able to create one. When you tried to select a disk for the array with the "X", it would automatically clear the box, making it impossible to select a drive for the array.

I think there's still a missing part of the puzzle...probably one that needs to be supplied by the motherboard manufacturer.

Right now, I reinserted the PCI OpROM and have recreated the array with RST 12.5. I'm re-imaging Windows now...so soon enough I'll be able to tell if recreating the array helps...

 

[DigitalDJ]

Additionally, I've noticed that adding the EFI SataDriver module seems to mess with CD drives attached to the controller. While the SataDriver was present, my DVD drive had trouble reading disks. UEFI booting Windows 8 from CD would hang with a black screen and attempting to load EzFlash2 while a CD is in the drive would cause a hang. Best to probably avoid doing this then.

Removing SataDriver fixed the problem

 

[Fernando 1]

@ DigitalDJ:
Thanks for having tested it and thanks for your reports.

Additionally, I've noticed that adding the EFI SataDriver module seems to mess with CD drives attached to the controller.

Don't your mainboard have any non-Intel SATA Controller?