Separate names with a comma.
Discussion in 'Memory and Storage' started by Dufus, Nov 8, 2012.
This is where you create the array
Yep, but I'm trying to figure out what the Intel RAID ROM Utility is that Fernando made reference to. Is it a separate utility, in addition to the IRST application?
Yes, that is the DOS based utility you get by hitting Ctrl+I while booting.
I had a feeling that that's what you were referring to. It lists the array as normal and each drive as being a member disk, but doesn't say whether or not if the array is being detected as a SSD.
Thanks for the pictures. Everything seems to be fine regarding the RAID arrays.
So it's obviously just the "Optimizer" (= Win8 Defrag Tool?), which doesn't detect all SSDs correctly.
Did you ever run the Windows-Experience-Index (WEI)?
I ask this, because usually the OS detects the SSDs by running the WEI.
I ran it only once, which was right after I installed Windows 8 and fully updated it with all drivers, windows updates, mandatory apps, etc., and then made a clean backup image.
I'll run it now and report right back.
EDIT: Still being listed by Win8 Defrag Tool as a hard disk drive. I wish there was a simple registry entry that I could change to force Windows into seeing it as a SSD.
What's everyone's opinion? Do you all believe that's the reason the array won't TRIM?
Have you tried an earlier Intel RST Driver? This is what seems to work the best for me:
Uploaded with ImageShack.us
The Intel RST 126.96.36.1993 drivers showed TRIM was present / working on my system but the HxD .jpg method proved otherwise.
Thanks for the suggestion Spinejam. Yes, I previously had version v188.8.131.522 installed, and TRIM wasn't working on the Transcend array. The Patriot array works great with both driver versions. I can't remember if the defrag tool listed the Transcend array as a SSD or not with v184.108.40.2062. Do you think I should reinstall that version again, or maybe even v220.127.116.110? (<-never tried).
The only thing I haven't tried is installing Windows 8 from scratch again. I didn't do this due to it not being needed to get TRIM functioning on the Patriot array.
Initially, I tested TRIM on the Transcend array while Windows 8 was installed using IRST v18.104.22.1682. When it didn't work, I put the older Patriot drives in. With a freshly created RAID 0 array, I ran the TRIM test on them. Worked instantly. I thought, "Okay, cool. TRIM is working!"
From there, I created a fresh backup image of the system, deleted the Transcend array, and restored the image to the Patriot array instead. Not a single problem. Drives were detected as solid state drives right off the bat, and the TRIM test passed with the OS installed exactly as it was just 20 minutes before.
Now that I had the Transcend drives separate again, I tested TRIM on each individual drive. Perfect, instant results! This is still with IRST v22.214.171.1242. I decided to re-created the array directly through the Rapid Storage application (~11-27-2012). Once setup, I immediately ran the TRIM test. It didn't work. I ran win optimize (which makes me think it was detected as a SSD before), logged off/in, and rebooted, but didn't get TRIM working. See here. When IRST v126.96.36.1993 was released, I installed it hoping that it would fix my issue, but no.
So, now I'm just stuck. I refuse to give up though.
It is rather strange, that Win8 doesn't detect your Transcend drives as SSDs. This issue obviously is the reason why you don't get the TRIM command into your Transcend RAID array.
I suspect, that either the firmware of your Transcend SSDs or the mainboard BIOS is responsable for your problems.
Just got this from a support ticket I submitted yesterday to Gigabyte...
Currently orom in Z77 models is version 11.1.
We will update to 11.5 soon but no confirmed deadline to finish the update.
Any idea why mobo manufacturers don't generally update the ROMS? Is it because they can't be bothered or is there a more reasonable explaination?
Who has to validate a new ROM on an Intel chipset? Intel and/ or the mobo manufacturer?
Surely it must be easier to deal with validation and not problems related to outdated ROMs and mismatched drivers?
Sorry for all the questions but I 'm just curious why it seems to be such a bid deal to update a ROM.
Generally the mainboard manufacturers are more interested in developing and offering new BIOS versions for actual mainboards than to be up-to-date with the insertion of third party PCI ROM modules. Maybe they are afraid to be bothered by the users more than ever, if they would start a PCI ROM update rallye.
It's the chipset and OROM manufacturer Intel, which develops, produces and has to validate all new Intel Option ROMs on different Intel chipsets. Nevertheless the mainboard manufacturers do test them too with their boards and may even deny the usage, if they are not satisfied with the test results.
Nobody feels responsable, both sides (the chipset manufacturer and the mainboard manufacturer) are passing the buck.
Trim doesn't work for me, but Win 8 pro detect my two x Vertex 3 V2.25 raid 0 as one SSD drive. Windows shows 100 trimmed and HxD test proves it's wrong.
- Gigabyte Z68X-UD4-B3
- Controller ID 2822 / alternate ID 1C06
- Last bios (F10) (no UEFI).
- Various modified OROM tested, 188.8.131.522 included.
- Modifications on Intel module tried (1C06 ON and all others changing ON/OFF).
- Ghost system image made / raid reconstructed.
That is very strange.
Are you absolutely sure,
that your BIOS contains the correctly modified Intel RAID ROM v184.108.40.2062 with enabled TRIM support for Z68 SATA RAID Controllers (Alt. Device ID 1C06) and
that you have done the Hex Editor TRIM test correctly?
I have a z68xp ud3 with 2x vertex3 v2.25 120s and win7 works fine. Win8 not so much.
What does that mean regarding the TRIM support?
Just to chime in as well, Windows 8 does not TRIM in RAID for me.
Widows 8 Pro - fresh install
ASUS P8P67 Pro
2x Agility 3 240GB
BIOS 3602 with Intel OROM 220.127.116.112 (modded by garikfox)
Tried RST 18.104.22.1682 and 22.214.171.1243
Windows see the array as an SSD, attempts to trim it, but HxD shows that the data is untouched.
There's some talk about it over at the overclock.net forum.
Windows 8 Pro:
My Hxd .jpg test would fail w/ driver 126.96.36.1993.
Everthing works fine w/ driver 188.8.131.522 though.
1. I tried your modified ROM v.184.108.40.2062 and others.
2. Yes. The same Offset, tested with HxD and Winhex.
Everything tested, except the UEFI BIOS / new O.S. installation.
As I have already reported >here<, I got full TRIM activity within my 2x128 GB Crucial M4 RAID0 with my Z68 system running Win8 x64 and using Intel's RST(e) drivers v220.127.116.113 once having flashed a BIOS with the modded Intel RAID ROM v18.104.22.1682.
I don't have any explanation for the different TRIM results posted by Schmide, TooYellow, spinejam and bbclient.
@ Fernando 1:
Good news -- I uninstalled driver v22.214.171.1242 and reinstalled driver v126.96.36.1993 and it seems to work just fine now.
Uploaded with ImageShack.us
Uploaded with ImageShack.us
Since going to the new 188.8.131.523 rst driver I get 1-2 second occasional freezes. Only noticed just now and happened on only two random instances. may be unrelated as I also updated the marvel, and every other device to the latest firmware on my Z68 Asus deluxe board. May have to to roll back to last bios version I had but was good on last intel rst release. Any one can suggest what to do to track this down?
Don't pre 5 series chipsets have alternate device ids?
I really need some help here, i installed the modded 184.108.40.2062 and the rst driver 11.7 and can not get trim working on my asus p8p67 deluxe on w7 64.I am using hxd and still shows no change after deleting,what am i doing wrong thank you.:thumbsdown:
They may have an Alternate Device ID, but they probably are not able to let TRIM pass through the Intel SATA RAID Controller.
1. Which Alternate Device ID of your RAID Controller is Dufus SATA ID Tool showing?
2. Where did you get the modded Intel RAID ROM module resp. the modded BIOS?
3. Are you 100% sure, that the modded BIOS has been flashed correctly?
1. Ok the sata id says controller id#2822 alternate#1c04.
2.from your post #70 of this thread it was the modded 3509 bios.
3.Well i hope i did it right i used the EZ flash on the board,it worked and the raid rom shows 220.127.116.112.