Here is another Asus P67 bios I made, Asus Sabertooth P67 latest release 3602 and 11.6.0.1702 OROM, 100% working TRIM in Raid0: http://www.diskusjon.no/index.php?ap...tach_id=509437
Here is another Asus P67 bios I made, Asus Sabertooth P67 latest release 3602 and 11.6.0.1702 OROM, 100% working TRIM in Raid0: http://www.diskusjon.no/index.php?ap...tach_id=509437
I'll have to try this on my P55 motherboard (Gigabyte GA-P55-UD3)
Would be interesting if I could get TRIM working on this old motherboard! (I can confirm that modern 11.x BIOS works correctly on my motherboard!)
RST: 11.5.9.1002
@ station-drivers.com
If anyone wants to try :)
I'll re-run the test with a much larger text file tonight when I get home.
I don't think it matters though. I think Dufus is incorrect about my data just being flagged for rewrite. The data from the text file falls outside of the range of the newly created TMP file, and was zeroed out. You can in fact see the EOF for the TMP file and it ends right where the data should be from the text file, and if what Dufus said is true, the data would still be there, since it was just flagged. Writing out the TMP file wouldn't zero out the bits behind it.
My array is high usage and nearly full, so I'm not surprised by another file being written to that location in 2 minutes(which is about how long it takes to scan).
That would be fine. Even better would be a JPG file.Quote:
Originally Posted by zoson
By the way I have another question:
If you followed the informations you got at AnandTech Forum, how and where did you detect the Alternate DeciceID of your on-board SATA RAID Controller?Quote:
Originally Posted by zoson
According to my knowledge the device with the ID "3A16" is not any Intel SATA RAID Controller, but the "82801JIR (ICH10R) LPC Interface Controller" (look >here<).
By the way: Did you already run "Dufus SATA ID Tool" (>LINK<), which will show the correct Alternate DeviceID of your on-board SATA RAID Controller?
That is quite normal for all Intel SATA RAID Controllers with the standard DeviceID DEV_2822 (from ICH8R to 7-series chipsets) and doesn't indicate at all the special SATA RAID Controller of your mainboard.Quote:
Originally Posted by zoson
freaking AWESOME!
Have you guys checked if it works for x79?
X79 is supposedly working with the latest bioses (if available) without modding, Intel is probably finding the X79 owners fury a little hard to swallow and sales a bit lacking, so X79 owners will get it hasslefree..
Yeah, the intel forums have a $hitstorm going on with pissed X79 owners abou this. Good to see intel stepping up.
You forgot to share your TRIM-Raid0 success at OCZ forums, Brahmzy? They where still in the "darkages" when I took a look yesterday... :P
We have a thread: http://www.ocztechnologyforum.com/fo...s-NOW-POSSIBLE
Ouch, not alot of peace&love over there, had an urge to post there when I got my modded bios working a few days ago, but I guess my lazyness saved me some gray hairs, for once :D
then you haven't spent much time here :rolleyes:Quote:
Originally Posted by Ourasi
Hi,
Trying to get trim working on my x58 Classified. Aida64 says its a 82801hb/hr ich8/9 raid controller. I've tried every device id I can think of by plugging it into the 11.6.0.1702 lookup table but nothing works. Anyone know what the proper device id is?
Thanks
I suppose, that the Alternate DeviceID of your Intel SATA RAID Controller is DEV_2925.Quote:
Originally Posted by davidm71
By the way: >Here< is the answer I gave you at AnandTech Forum.
Hey Zoson,Quote:
Originally Posted by zoson
I have a rampage 2 extreme, I replaced the firmware with 11.6.0.1702 in the bios but upon booting it wouldn't go beyond the raid post. I then replaced the raid firmware with 8.9 (I think I was originally on 8.5 or so) and that booted up normally, so I think I'm creating the new bios correctly. Do you know of a reason why the rampage 3 would work and the rampage 2 would not, differing intel raid controllers? I thought all raid controllers for the x58 boards were the same, but maybe I'm incorrect?
Thanks, any help is appreciated.
Thaydengeo
Could you make a TRIM-BIOS for ASUS P8P67 (REV 3.1) BIOS 3602 ?
P8P67 Rev 3.1 3602 BIOS: http://ul.to/w1kq9u0v
Thanks in advance!
This was written on Tuesday. Did you meanwhile get any new results?Quote:
Originally Posted by zoson
davidm71 and thaydengeo are not the only X58 RAID0 users, who are waiting for your feedback.
You probably can get it from >here<.Quote:
Originally Posted by C3
Fill Tested RAID 0 TRIM on my Z68A-GD80 B3 and TRIM works perfectly. Thanks for the OROM Fernando!
Does anyone have the oc formula working with this orom?
If not...could you please mod it for me?
OC Formula is Z77 and should have working TRIM-orom from manufacturer, check the version on top of Intel raidbios..
I modded my BIOS. It was pretty easy once you know what to do.
Flashing went smoothly. I switched from AHCI to RAID after enabling IastorV in the registry. I can see 11.6 in the RAID boot settings. I now need my 2 512GB SSD (which I rapidly bought from newegg @ 194$ !!) to test if TRIM is working.
Hopefully the firmware of your new SSDs do fully support TRIM.Quote:
Originally Posted by kensiko
Good luck!
WOOHOO!! :eek: Success!! :up: RAID0 TRIM WORK ON Z68!! :p: F*CK YOU INTEL! :mad:
Asrock Z68 Exreme4 GEN3
BIOS V2.30 modded by Garikfox with Fernando OROM 11.6.0.1702 RAID0 TRIM enabled hack specific to the P67/Z68
2 X Crucial M4 128GB 000F Firmware
RAID0 128K strip array originally created with OROM 10.8.0.1303
Intel RST driver 11.6.0.1030 installed before upgrading to OROM 11.6.0.1702
Win7 64 Ultimate
I flashed, I configured, I conquered. Nothing else to change. 100% confirmed to work with HxD, thanks to Fernando's guide. Ahhhhhhhhh, the pretty zeros all over the place!
NOTE: I don't know If I did something wrong, but after the first reboot, it didn't work. Rebooted a second time, tested again and BOOM! Maybe 2 reboot are necessary. Also, the M4's Marvell controller seem to have a more relaxed triggering time for TRIM. I did the test immediately after deleting the file and emptying the trash can and it didn't work. I then waited a good 45-60 seconds, tested again and BOOM!
Thanks a ∞ times!! to everyone involved. Especially Garifox, Fernando and of course to the one that made all this possible: Dufus.
TRIM takes a few seconds to work, look at HDD led when deleting >4GB files.
Hi Fernando, I was wondering if you could give me some advice here, I currently own a Samsung 840 Pro 512gb, no raid, just 1 drive. I have x79 Asus Sabertooth motherboard. I tried the RSTe V3 drivers and they write capped my drive in a horrid way, less than 3mbps on the 4K. I uninstalled the V3e drivers and used the msachi driver and it was a dramatic improvement but not what I got on the first run of Anvil Benchmark. I looked in the registry and there was an entry for the IASTOR.F driver exactly where you said it would be.Quote:
Originally Posted by Fernando
http://img713.imageshack.us/img713/9...6amiastorf.png
Uploaded with ImageShack.us
After deletion my Anvil with the msachi driver was better but not close to the first run after a clean install of Windows 7 64bit. Now what IRSTe driver should I use or should I just continue with the masachi driver?
As long as you are running your SATA drives in AHCI mode, I would stick with the generic MS AHCI driver.Quote:
Originally Posted by alan1476
As an alternative you may try the 64bit Intel RST driver v11.2.0.1006, which I have modified for being usable even with X79 Chipset systems. You can find it here: http://www.win-lite.de/wbb/board195-...-raid-treiber/. Remember: You have to force the installation by using the "Have Disk" button.
Thank you so much. Now I have to put the drivers on a disc I guess. LOL. You are very nice. Thank you.Quote:
Originally Posted by Fernando
Well I forced the drivers you gave me and the only thing it did was change the name of the drive in the Device Manager from Samsung 840 to just plain old " Disk" it however had no other consequences, it could be I didnt do it right. Still using MSACHI, and its write capping the drive, not to the extent where its not fast, but using Anvils Benchmark, it went from a 5300 to a 4300. All the 4K write score were way low. This happened after a clean install of Windows 7 64bit, it was great before I ran the Windows accessment and horrid after the accessment, very wierd.Quote:
Originally Posted by Fernando
After having installed the Intel RST driver v11.2.0.1006, did you check the driver of the Intel SATA AHCI Controller? Only this way you are able to verify, that the driver update has been successful.Quote:
Originally Posted by alan1476
Nope, but I am on it now, thanks again.Quote:
Originally Posted by Fernando
And what is your impression regarding this Intel RST driver compared with Microsoft's generic AHCI driver?Quote:
Originally Posted by alan1476
All I can say is that you should be paid by Intel for fixing the stuff they should be fixing. Thankyou Fernando, you are a gerntleman.;)Quote:
Originally Posted by Fernando
INTEL Chipset Device Software drivers 9.4.0.1005
* Product: Intel(R) Chipset Device Software
* Release: Production Version
* Version: 9.4.0.1005
* Target: Intel(R) Xeon(R) Processor E5 Product Family/Core i7, Intel(R) C200/C600/X79 series chipset
Download
These "Intel(R) Chipset Device Software" packages do not contain any driver, but just information (=text) files. Nobody is able to use them as AHCI or RAID driver.Quote:
Originally Posted by alan1476
So there are no new IRSTe drivers v9.4.0.1005 out.
Nevertheless there may be good news for users with an X79 chipset mainboard: A new Intel RSTe RAID ROM version 3.6.0.1023 is available! Users with an X79 chipset system can download this brandnew RAID ROM module from >here<.
Hi all,
In addition to Fernando's HxD method of verifying TRIM functionality, i would like to add this program i just found :
TRIMCheck
I'm just adding the post of user "Bad Machine" of theSSDreview forums, where i found it :
Quote:
TRIMcheck: A FREEWARE TRIM TESTER
The title says it all. fsutil will tell you if TRIM is enabled or not, but it won't tell you if it is really functional. TRIMcheck will actually check if TRIM works or not.
This program has no GUI, it runs in a command prompt window. You must copy it on the SSD that you are testing and run it twice, waiting for at least 30 seconds to a minute between runs in order to ensure accurate results.
When executed for the first time it will write on specific sectors on the SSD. It will then delete the written data and exit. When you run it a second time a minute later, it will try to read the exact same sectors. When TRIM works you'll get zeroes on the sectors it wrote, plus a notification that TRIM works. If the data is still there you'll be notified that TRIM is not working. This is good for cases where certain software use cheap workarounds that cripple TRIM in order to ensure SSD compatibility. In such cases fsutil will still show that TRIM is enabled, regardless if it really works or not. With this proggie you'll know for sure.
Hope you like it, i just tested it with success on system (non-raid).
EDIT :
Since there has been some misunderstanding, i did not develop the tool, i clearly stated that i found it and gave a link to where i found it.
Developer is Vladimir Panteleev and source of the tool is CyberShadow's blog.
Both are stated in the program running window, first 2 lines.
Pretty cool thanks felixQuote:
Originally Posted by felix_w
@ felix:
Thank you very much for the informations regarding the TrimCheck tool, which has been offered by the user "Bad Machine" at "The SSD Review Forum."
I have just tested it with my Intel Z77 RAID0 array and this is what I got:
http://www10.pic-upload.de/thumb/15....tka45f917k.png
Just to verify the results, I executed the "Easy Trim Test" method by using a hex editor, which I had layed down >here<. Result: The sector, where the jpg file had been, zeroed out within a few seconds after the delition of the file.
So I am rather unsure, if "Bad Machine"s TrimCheck tool gives realistic results, if the SSD is part of a RAID array.
Great program! I tried to test TRIM on any of my SSD using the hex method and I never succeeded, but now I got that:
Edit:Quote:
Re-checking raw volume data...
Opening \\.\C:...
Seeking to position 39428247552...
Reading 16384 bytes...
First 16 bytes: 6F D2 64 F4 28 00 07 95 21 E3 15 2B D3 D7 61 C2...
Test file created and deleted, and continuation data saved.
Do what needs to be done to activate the SSD's TRIM functionality,
and run this program again.
Usually, you just need to wait a bit (around 15 seconds).
Sometimes, a reboot is necessary.
Press Enter to exit...
C:\>trimcheck-0.3.exe
TRIM check v0.3 - Written by Vladimir Panteleev
https://github.com/CyberShadow/trimcheck
Loading continuation data from C:\trimcheck-cont.json...
Drive path : \\.\C:
Offset : 39428247552
Random data : 6F D2 64 F4 28 00 07 95 21 E3 15 2B D3 D7 61 C2...
Reading raw volume data...
Opening \\.\C:...
Seeking to position 39428247552...
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!
Negative result for my RAID array.
As far as i can see, the tool uses a similar method with Fernando's Trim Test method, although it does it automatically.
Ιt may be easier , yet not known if 100% valid, for some non-experienced users, maybe not existing in XS, but out there, there are some.
Hi, Ferando!Quote:
Originally Posted by Fernando
You have to run the tool to create testfile, run it again to trigger deletion, then reboot and run it again with the same *.json created before the reboot (reboot forces TRIM success every time).. It seems only singledrive TRIM's instant with this tool, the tool possibly is forced into a queue by the OS/drivers, since it's not a user-triggered emptying of the recyclebin ..
Intel 520 Raid0:
http://bildr.no/thumb/1393108.jpeg
Crucial C300 Raid0:
http://bildr.no/thumb/1393109.jpeg
Single 840 Pro OS drive:
http://bildr.no/thumb/1393112.jpeg
Done on Asus P67 Sabertooth, all Raid0 volumes successfully TRIMMED..
*Edit: Updated with correct method...
This tool doesn't work for me.Quote:
Originally Posted by Ourasi
It doesn't matter how long I wait before I rerun the tool, even after a reboot: I always get the message "TRIM appears to be NOT WORKING".
But when I do the hex editor test, the related section zeroes out within 2-3 seconds.
Doesn't work for me either and I know TRIM is functioningQuote:
Originally Posted by Fernando
Here is what workes for me every time: Put the tool on the volume you want to test: Run the tool, it creates the testfile and *.json, run it again imidiately to trigger deletion, do not delete the *.json. Then reboot, and run it again.. Works every time on my end on Win7...Quote:
Originally Posted by Fernando
First run creates testfile+json only, if you reboot now, it wont work since no deletion has been triggered. Reboot only after you run the tool the second time, as the second run triggers deletion. The third run after the reboot should see success as the sectors are zeroed out...
Anyway, I'm sure TRIM works for both of you, and I suspect there are some issues with this tool, since I to do not need a reboot or a long wait with the hex editor test, with hex editor it TRIMS instantly..
Exactly this procedure doesn't work on my system (Win8 x64). Surprisingly the tool detects TRIM as working, if I wait minimum 30 minutes and then rerun it, but this is not a correct TRIM verification. It could be the SSD in-box Garbage Collection as well, which cleaned the SSD area within that long time.Quote:
Originally Posted by Ourasi
It doesn't work for me either, but I do not believe this tools works at all. It might and Imight be doing it wrong but it doesnt detect TRIM on my machine and faustil says its running. Its says " indeterminate" wait 15 sec and reboot, well I did that and it keeps saying it. It wont work.Quote:
Originally Posted by Fernando
Meanwhile I have done some intensive tests with the version 0.3 of the TrimCheck tool.
Here are the details of my test system:TRIM definitively is active within my RAIDed SSDs. That has been proven very often by having done the "Easy TRIM test method", which I have described >here<. After having completely deleted the JPG file the related section always zeroed out within 2-3 seconds.
- Hardware: Z77 chipset MB with 2x256 GB Samsung 840 Pro as RAID0
- OS: Windows 8 Pro x64
- Intel RAID ROM: RST(e) v11.6.0.1702
- RAID drivers: Intel RST(e) v11.7.0.1013
Having these previous TRIM test results in my mind, I was very astonished, that I always got this message, when I ran the "TrimCheck" tool:
http://www10.pic-upload.de/thumb/17....p3vxfw9bv5.png
Yesterday I have done the following experiments:
- I executed the TRIMCheck tool as Administrator and reran it 1, 2, 3, 4, 5, 10, 15, 30 and 60 minutes later.
Results:
Each time I got the following message:
http://www10.pic-upload.de/thumb/17....y6fbumlwni.png
So the TrimTest tool didn't detect any TRIM activity.- I restarted the computer and let the TrimCheck tool check again.
Result:
http://www10.pic-upload.de/thumb/17....y6fbumlwni.png
So the reboot of the OS didn't change anything. TRIM has still not been detected by the tool.- Then I executed the Win8 "Optimizer" (former Defrag Tool), which sends a thunderstorm of TRIM commands to the related drive, and optimized drive C this way.
A few seconds later I reran the TrimCheck tool.
Result:
Surprise, surprise - now I got this message:
http://www10.pic-upload.de/thumb/17....pzx4q1ui3r.png
These resuts verify, that the current version 0.3 of the TrimCheck tool is not able to detect any TRIM activity unless the release of TRIM commands by the OS has been pushed by a separate action.
Conclusion:
Contrary to the manually done Hex Editor method (see above) the TrimCheck tool is not able to detect "normal", that means unpushed TRIM activity.
My comment:
When I compare the action of CyberShadow's (Vladimir Panteleev's) TrimCheck tool with the manual Hex Editor TRIM test, I suspect, that the test file, which is copied by v0.3 of the TrimCheck tool onto drive C and deleted later on, is too small sized (16,4 KB).
Obviously the insertion and delition of a much bigger sized file (> 1 MB?) is needed to let the OS send out TRIM commands by itself.
FYI I ran the tool again on my RAID array and now it is all 00 00 00. It's possibly due to the garbage collector, not sure.
It sometimes works for me as well.Quote:
Originally Posted by kensiko
If it shows "TRIM appears to be WORKING" within 1 minute after having executed the EXE file the first time, you can be sure, that TRIM is active. No Garbage Collection is able to clean SSD cells 100% within one minute.
Anyway I'm happy to see 00 00 because this means that the SSD in my RAID array are automatically cleaned by one way or another. This tool is clearly useful.
Trimcheck seems to delete its file differently than Windows and doesn't trigger an immediate TRIM. I tried trimcheck, waited the recommenced 20 seconds and ran it again and it failed. Waited 1 minute, failed again. This is my solution:
If you want to avoid the reboot and/or wait guessing in your TRIM validation, use the Anvil's storage utility "Trigger TRIM" function located in the "Benchmarks" menu. Also very useful to ensure your benchmark is performed on a freshly trimmed drive.
Get the latest RC6 version there:
http://www.guru3d.com/files_get/anvi...ownload,4.html
I did a fresh trimcheck again, manually triggered the TRIM and then trimcheck immediately confirmed TRIM is working. No reboot, no waiting.
I would recommend the author of trimcheck to incorporate a TRIM triggering code similar to Anvil storage utility.
There is also trimtool for that job, i believe it does the same, i don't know for sure though. Known from the Crucial Forums.
SSD tool is very nice. Seems to do the same work Anvil storage is doing for TRIM.
Unfortunately, I tried trimcheck again with SSD tool and it didn't wok. Then tried with Anvil storage TRIM, and still didn't work! Seems like my previous success was a fluke. Trimcheck seems not to be 100% reliable in its present form. I did the HEX test many before and always got zero.
EDIT: Waited another 5-10 minutes, and finally, trimcheck confirmed TRIM to be working. Trimcheck is broken, as the manual TRIM triggered by Anvil storage utility was instantaneous with the HEX test method. That 5-10 minutes of waiting coincide with my first unsuccessful test and the time it took me to think to use Anvil storage utility TRIM function.
Thank you for the heads up and testing done Ramon Zarat. I Cannot believe i started this tread on 7-13-2012 and this whole thing about trim on Raid0 due to my findings and has already over 69k + views already :yepp: , im glad i started this whole thing and has been very useful for everyone , to share the knowledge makes me happy :up:
is this driver Intel? Rapid Storage Technology Driver 12.0.0.1083 RC any good ?
I am running these Intel RST(e) drivers v12.0.0.1082 with my Z77 RAID0 and am very satisfied.Quote:
Originally Posted by andressergio
By the way: After having flashed the BIOS with the updated Intel EFI RAID "SataDriver" v12.0.0.1783 I have recreated the RAID array and then installed Win8 Pro x64 in EFI mode onto the freshly created RAID0 array. Everything works perfect.
In my opinion all RST(e) SCSI-filter drivers are lacking in performance, this falls under this category.. I'm on 11.2.0.1006 flpy only, and works with raid0-TRIM and are among the best reg. performance on win7... Win8 might be another story though...
Since Intel has stopped the development of the RST driver iaStor.sys already in June last year, the time will come very soon, when all the iaStor.sys users have to say goodbye to this LEGACY 1-driver model.Quote:
Originally Posted by Ourasi
Just to verify that, you should try to install Windows 8 in EFI mode onto an Intel RAID array. With a BIOS containing the actual EFI RAID "SataDriver" module Win8 will not even detect your RAID array unless you load an Intel RST(e) driver package containing the SCSI filter driver iaStorF.sys.
By the way: Nobody will really notice the benchmark result differences between the best RST and the actual RST(e) drivers.
Well, I'm in no hurry to go win8, and most likely will skip it completely.. So I have no reason to dump the 11.2 for a newer RST(e) version.. Btw: I never wrote that the perfomance difference would be noticable in real world, but since this is XS forums, proper benchresults do matter :P
Thanks Fernando im using the most stable BIOS on the Maximus Formula 5 Z77 wich is the 0095 its old and no ROM updated so i think i have no TRIM...i will install the RST either wayQuote:
Originally Posted by Fernando
cheers !!!
Sergio
Has anyone tried the new 9.4.0.1016 RSTe Intel drivers for the X79 chipset?
That are neither RSTe drivers nor real drivers at all. What you mean is the "Intel Chipset Device Software" package 9.4.0.1016, which contains - as all the other "Intel INF Update Utiliy" sets - a lot of more or less actual text files with the suffix ".INF. Real drivers have the suffix ".SYS".Quote:
Originally Posted by alan1476
Yes that is exactly what I mean. I downloaded something from the site, have not tried to install yet until I heard your opinion. Thanks for clarifying that Fernando, I saw them on Station Drivers and thought it was a new driver. I am using the 12.0 drivers and they work fine on my X79 system. best yet for me.Quote:
Originally Posted by Fernando
1 .- Thank for all your nice post
So if i understand good, because i got dx79si and intel bios must have some sort millitery secret in it, i just can't open it
and use the good news for users with an X79 chipset mainboard: A new Intel RSTe RAID ROM version 3.6.0.1023 is available!
right
sorry for the poor english
Intel Rapid Storage Technology(RST), Version 12.5.0.1066 WHQL is out.
RST: 12.5.0.1066
ROM: 12.5.0.1815
http://www.station-drivers.com/forum...hp?f=32&t=4393
TNX stasio :up:
Cool thanks stasio now it displays intel RST correctly with no errors as before Intel + Asmedia here
cheers !
Sergio
guys my intel RST says "RST is not on execution" i was seeing my intel raid + my asmedia 3TB drive now it went away, i reinstalled like 3 times and same...uninstalled and back and same...i also tried to up service but it says it cannot start due to an error...
any help ?
Cheers !
Sergio
Hola my friend , I also had a lot of errors after installing this new RST , to the point it Blue Screen a couple of times and corrupted my Raid0 array of my 24/7 rig , lucky me I have just saved a back up completel;y a few days ago and I restore the whole OS , I end it up uninstalling it and went back to 11.2 as that was the last one working flawlessly for me. I hope you get it solve asap , but for me this RST driver was a nightmare.Quote:
Originally Posted by andressergio
thanks Chispy as always !!!Quote:
Originally Posted by chispy
guys i have a doubt on SLI
we are talking about TRIM that deleting a file then TRIM
but... what if i want to TRIM my entire SSD...what if i have it installed and want to optimize it like INTEL SSD TOOLBOX does ?
does making a disk image of my raid of SSD with Acronis erase my SSD, make raid again and put the image back realigns and restore speed ? or its useless ?
Thanks
Sergio
anyone ?
Do what you wrote but use secure erase, don't just delete
anyone know if X58 was finally included in letting TRIM pass-thru to RAID?
or maybe even hacked drivers? :D
Only Intel 7-Series and X79 chipsets are natively supported by the TRIM in RAID0 feature.Quote:
Originally Posted by tiro_uspsss
It aren't the drivers, but the Intel RAID ROM module, which prevents, that the TRIM command passes through the Intel ICH9R/ICH10R SATA RAID Controllers of X58 chipset RAID0 systems. TRIM in RAID0 is a no go for X58 chipset RAID0 arrays, not even a modified Intel RAID ROM will enable this feature.Quote:
or maybe even hacked drivers? :D
I have :
- one Gigabyte UD5 motherboard running on the official F13 (latest) BIOS
- 2 Crucial m4 64gb running in AHCI mode
- I will have 2 Samsung 840 Pro 128gb in 2 days (they are shipping as I write this)
I downloaded from tweaktown:
- modded BIOS F13 with IRST 11.5.0.1347 orom
- modded BIOS F13 with IRST 11.1.0.1413 orom
- modded BIOS F13 with IRST 11.6.0.1702 orom
I want:
- to set the 2 Crucial ssds in RAID 0
- to set the 2 Samsung ssds in RAID 0
Can someone please advise on which modded BIOS should I use to get the best performance?
Can someone please advise also on which RST driver version should I install on W7x64?
The general rule of thumb is that x58 ICHR10 DOES NOT SUPPORT TRIM IN RAID 0.
Thank you very much Intel, you :banana::banana::banana::banana::banana:s.
But I'm betting the house on Crucial's and Samsung's Garbage Collection algorithms on the ssds firmware.
Am I stupid for all of the above?
Should I just forget about Raid 0 on x58?
Thank you for bearing with my long plea for an honest advice.
If I were you, I would take the actual BIOS F13 with the Intel RAID ROM v11.6.0.1702.Quote:
Originally Posted by daedao
If you want the best performance, you should install the Intel RST driver v11.2.0.1006.Quote:
Can someone please advise also on which RST driver version should I install on W7x64?
Yes, that is fact and may minimize the life time of your SSDs.Quote:
The general rule of thumb is that x58 ICHR10 DOES NOT SUPPORT TRIM IN RAID 0.
To be honest: I would not run the SSDs as RAID0 without having TRIM support.Quote:
Should I just forget about Raid 0 on x58?
Not to dismiss you, since you are a legend with modded bioses, but wouldn't GC (garbage collectors) have the same effect as TRIM?Quote:
Originally Posted by Fernando
I know that passing the TRIM command to the controller is more elegant and rapid, but with GC you get the same results just not right after you delete a file.
Your SSD has to be in idle state for the GC to kick in.
At least with the Crucial drives. And I believe Samsung has something similar if not better than Crucial's implementation. Both I think are good at this.
SSDs have come a long way since 2007-2008 era when having TRIM functionality was a must have.
I believe that today's SSDs have better firmwares. Crucial and Samsung are probably the best right now.
I plan to use the raids for booting Windows, Linux, games and some virtual machines loading and java compiling, and since i'm on an "old" chipset (x58) I do not have sata 6gbps ports, so I want to make up for that by using SSDs in raid 0. So I won't be writing to the SSD all that much. Just initially when I setup my OS and restore my Steam collection and copy my VMs.
After that it will mostly be reading from the SSDs.
I'm not that rich to buy a new motherboard and processor just because Intel wants so and I plan to give my platform a few more years.
My UD5 coupled with my i7 980x and 24 GB ram rocks. I see no real reason to upgrade.
Used R0 for years without trim, and have seen no negative results from it. Nice to have it but not the be all end all from where I stand and it surely would not prevent me from using R0 now if I did not have trim.
Raid0 without TRIM is the reality for the majority of raiders with SSD's, and if you keep enough free space or have a decent spare area combined with good GC/FW, there is no reason not to enjoy raid0, as many of us XS-storage-nerds has for years..
TRIM+raid0 makes SSD-raid0 less high-maintenance for powerusers and is alot more bench-friendly, but we can live without it... The SSD-raid0 newb however, that fills the the array to the brink and benches to the tillt before popping up on various forums complaining about bad performance, it might be a godsent :D
@ daedao:
My answer "I would not run the SSDs as RAID0 without having TRIM support" was valid just for me and not for all other SSD RAID0 users.
So there is no difference between Ourasi's and my statement.
Furthermore I want to mention, that the relevance of the TRIM support does not only depend on the usage of the SSDs, but on their intern Controller and Firmware too. Not all SSDs have a very effective Garbage Collection.
RST 12.6.0.1028 (ROM 12.6.0.1867) is out. :clap:
I'm not saying you're not right. TRIM is important, but I think that it's also overrated.Quote:
Originally Posted by Fernando
Good garbage collection does the same.
Anyway thank you for your advices, I was able yesterday to flash the bios very easily and with no problem whatsoever.
Maybe this weekend I'll have some time to set up my new Windows 7 install on the RAID stripe.
After that I'll post some numbers here.
Intel? Rapid Storage Technology Driver 12.6.0.1033 WHQL is out.
Newbie here! I am a bit confused on all this TRIM for SSD RAID 0. :(
I want to build a new system with 2 ssd's in raid 0 with TRIM. What motherboard can I purchase that will support this without having to install modified bios? Which X79 mb? Which Z77 mb? or must I install a modded bios to have trim function? I am interested in the AsRock x79. Thank you and sorry if I ask dumb questions.
afaik...Z77 based mobos don't need the bios modded to allow raid arrays to be trimed, it's the Z67/Z68 (maybe X79, not sure) that do. Not sure if intel ever 'fixed' the raid for X79's. I remember some pretty mad X79 owners when they seen that everyone else could get trim working except folks that bought high end intel gear (X79 and socket 2011). I'd be mad as hell to lol. They may have pulled it off by now....I quit following the story once I got a hold of a modded bios/rom for my Z68...lol
You may want to wait 2 weeks for Haswell and the Z87 chipset to launch....I would, but that's just me. If u do wait you can spend the time picking out all the other components for your build. You'll pay a little more (vs. Z77 etc.) cuz you're buying at launch time but it shouldn't be too terrible.
Does anyone know if the new Intel Z87 motherboard that are all SATA 6Gb/s will run a 3 or 4 x Samsung 840 Pro in the Intel RST with trim? As of now I am getting the following results pictured below and probably only going to get maybe a increase in Writes if anything. But only having 2 x 128GB I need a bit of more space and I figured why not try it.. Any thoughts
Thanks
http://i274.photobucket.com/albums/j...ench30full.jpg
Well after reading Gigabyte manual I've discovered that in a RAID 0 or 1 you must have 2 or more or even number of drives it says. So I assume 3 x Samsung 840 Pro's in a R0 will not work. Heading to Microcenter to pick up my 4th 840 Pro. Not worried about so many drives as I will be building another system soon if I do not think the performance is all that great I will split 2 x to the other system.Quote:
Originally Posted by Lu(ky
Anyone have any ideas on what I should put for the block size.
Thanks
Sent from my iPad using Tapatalk HD
you can use 3 or 5 drives it doesn't matter
http://i876.photobucket.com/albums/a...ps49779727.png
Thx B Gates
Here is what I got with my so far still feel my reads should be in the 1500..
http://i274.photobucket.com/albums/j...psb5e1d648.jpg
You need to turn on write caching its not turned on. Also make sure your cstates are turned off. 11.2 is a better driver tooQuote:
Originally Posted by Lu(ky
guys i need to clear my mind with something...
if my raid is not trimed and i do an image to disk with Acronis True Image Home 2013 then i erase the SSD and dump the image back, would it be of any benefit on performance ? does acronis alings or trims the data ?
Thanks !!!
Sergio
thats even better than TRIM its a great way to refresh your arrayQuote:
Originally Posted by andressergio
Acronis 2010 thru 2013 align disk if your not sure open as ssd and look up at the top left .Quote:
Originally Posted by andressergio
(4) Samsungs on Z87:
http://i876.photobucket.com/albums/a...psc1a3bd28.png
Stanky :)
current setup:
http://i876.photobucket.com/albums/a...psd2a9ad57.png
mama mia !!!Quote:
Originally Posted by b gates
Quote:
Originally Posted by B Gates
thanks guys !!!Quote:
Originally Posted by the_real_7