Zitat von D2theZ im Beitrag #135

---

Curious I just tried updating with the supplied file (thanks by the way) and UBU just freezes with a blinking cursor when replacing the module you attached and says File Exceeds the Volume Size?

---

Thank for the compressed v12.9 GUID 91xxxxxx SataDriver Fernando!! That version DID successfully integrate into my bios which is from a Gigabyte Z68 UDH-B3 motherboard. Maybe you can host more Universal TRIM modded GUID 91xxxxx SataDrivers going forward?

@ D2theZ:

Thanks for your feedback. It is fine, that you succeeded with the insertion of this compressed TRIM modded SataDriver module into your Gigabyte BIOS. Have you already done the TRIM test?
I will follow your suggestion and offer the latest "Universal TRIM modified" SataDriver versions for GUID 91B4D9C1 in compressed form (to make it easy by using the UBU tool).

Please modify the following module for gigabyte motherboards (GUID 91B4D9C1-141C-4824-8D02-3C298E36EB3F)
THX

Zitat

---

Modified version:

• >Especially modified Intel RST(e) EFI RAID "SataDriver" v12.6.0.1867 with TRIM in RAID0 for Z68 systems< (>MIRROR<)

---

@ k.bomb81:
Welcome at Win-RAID Forum!

When you give me a link to the original Intel "SataDriver" v12.6.0.1867 with the GUID starting with 91B4D9C1, I will modify it for you.
Why don't you want to take one of the newer SataDriver versions, where the requested TRIM modified GUID 91B4D9C1 model is available?

Regards
Fernando

Hi Fernando,

I've a Rampage IV Extreme BIOS 4804. I want to modify SataDriver 12.7 (originally) to 13.0.0.2075 but if i see the GUID with MMTool i don't see 90 or 91, but I see GUID that start with 43AQA

What kind of GUID i can using?

Thanks

@ RaptorX:
Welcome at Win-RAID Forum!
I am sorry about my late reply, but I obviously have missed your post.

Zitat von RaptorX im Beitrag #141

---

I've a Rampage IV Extreme BIOS 4804. I want to modify SataDriver 12.7 (originally) to 13.0.0.2075 but if i see the GUID with MMTool i don't see 90 or 91, but I see GUID that start with 43AQA
What kind of GUID i can using?

---

Hi,
My PC :
-mobo : Z77MX-D3H
-1 SSD running Windows server datacenter 2012 R2 on intel's SATA 3 port
-4 x 4tb WD RED in RAID 0+1 on intel's SATA 2 ports
- Intel's orom 12.7.0.1936 and driver 12.8.10.1005

Q1 :
I did try to update RST drivers to 12.9.3.1000 I have had a BSOD each time I logon.
I can stay at logon screen without issue but if I enter the password and go to the desktop then bam : BSOD
So I guess there is a mismatch between orom 12.7.0.1936 and driver 12.9.3.1000 and that this is that combinaison that BSOD?
(BSOD is something like DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 iaStorA.sys...)

Q2 :
-As I said, my intel's orom is 12.7.0.1936. From what I can see there are at least 2 newer orom versions.
Do you think I can safely upgrade my orom to a newer version (and also use newer drivers)? Or is it dangerous for my RAID data?

Thanks for your help

@ propergol:
Welcome at in-RAID Forum and thanks for your request!

To be able to anser to your first question, I need some additional informations:

1. Did you install the OS in LEGACY (using the MBR) or in UEFI mode (using the GPT)?
2. Which BIOS module is your Intel SATA RAID Controller using, the Intel RAID ROM or the Intel EFI SataDriver v12.7.0.1936?
3. How did you install the Intel RST(e) RAID driver v12.9.3.1000 (manually from within the Device Manager or by running the installer of the complete package)?
4. Did you uninstall the Intel Rapid Storage Software and reboot, before you updated the Intel RAID driver?

Zitat von propergol im Beitrag #143

---

Q2 :
-As I said, my intel's orom is 12.7.0.1936. From what I can see there are at least 2 newer orom versions.
Do you think I can safely upgrade my orom to a newer version (and also use newer drivers)? Or is it dangerous for my RAID data?

---

1. Did you install the OS in LEGACY (using the MBR) or in UEFI mode (using the GPT)?

I did install using UEFI but then I did a recovery image of the c: drive and Acronis B&R "converted" it to MBR.
I am not 100% sure but it looks like that now I can choose equally to boot in legacy or UEFI.


2. Which BIOS module is your Intel SATA RAID Controller using, the Intel RAID ROM or the Intel EFI SataDriver v12.7.0.1936?

Well, as I said it looks like I can use one or the other : if I set the bios to "CMS=never" then I can manage the RAID into the bios, if CSM=always then I see Intel's dos RAID (ctrl+I), both were booting ok before.
Both RAID interfaces (BIOS or DOS) are from same version : 12.7.0.1936


3. How did you install the Intel RST(e) RAID driver v12.9.3.1000 (manually from within the Device Manager or by running the installer of the complete package)?

That's a long storry ...
-I was first running Server 2012 with RST 12.8.10.1005
-I did uninstall RST then updated to Server 2012 R2 (uninstaller)
- then installed RST 12.9.3.100 (by running Intel's package)


4. Did you uninstall the Intel Rapid Storage Software and reboot, before you updated the Intel RAID driver?

see #3


Now here is where I am : I did window repair (that went strangely fast) and was able then to go to the desktop without BSOD.
Then I did reinstall RST but this time 12.8.11.1000
And now I am scared of trying a restart



EDIT : but you say that I can update my orom with a newer version without isue, so to solve my problem can't I just update my orom and driver to a known matching version?

@ propergol:

Thanks for your additional informations.
You obviously have already solved your main problem, so there is no urgent help necessary anymore.
My comment:
It was not a good idea to change
a) a Server OS without doing a clean install,
b) the partition table (MBR/GPT) from within a running Server OS and
c) the Intel RST(e) RAID driver versions and the related RST(e) Software without paying attention to the Driver/ROM/SataDriver combination.

If I were you, I would do a clean OS installation in UEFI mode and use a matching RST(e) RAID driver/SatDriver version combination (both should be from the same development branch).

ok....
I just try to reboot : BSOD

but but but....

I have found the problem!!! : it has nothing to do with RST, it was SpeedFan that I did not setup back properly after upgrading to R2.
When a single HD or SSD is plug to Intel's ports AND NOT member of RAID array, then for some reason Speefan see it as SCSI device and that make Windows BSOD.

Thanks a lot for your help anyway!

You say I should use RSTe but what would be the benefit over desktop RST version?
This server is more a sophisticated NAS than a real server.


EDIT : and the solution regarding Speedfan is to use /noscsiscan parameter.

Zitat von propergol im Beitrag #147

---

You say I should use RSTe but what would be the benefit over desktop RST version?

---

oh ok, I was begining to wonder what you were talking about

Regarding my update from 2012 to 2012 R2, I know that this is not very clean to do so, but I have read that this update could be a litle bit cleaner than what Microsoft have done in the past.
So I did a backup and updated, and if something goes wrong I would restore or start over a fresh install.

Talking about RST(e) , could you advise some particular combo? Since I don't realy like my actual orom/driver mismatch...

Zitat von propergol im Beitrag #149

---

Talking about RST(e) , could you advise some particular combo?

---