LOL you guys are funny! one dude here has issues and you're all convinced?
Personally, I think most of it's a mobo/driver bug that comes out with the use of these particular controllers just as it has in the past. Same sh*t, different cause. V3 240GB runs fine on my machine and is absolutely awesome for those running raids so far. Here's one similar to tech960's setup right here just to show that this issue is not everyones.
2 x 120GB V3 on ASUS P67
2 x 240GB V3 on ASUS P67
now while I can understand the frustration with not being able to just plug and play the drive?.. making blanket statements about drives being junk only serves to make it look like..
1. you don't know what you're talking about,
2. are simply another hater and are happy to report back to the nest,
3. or didn't want to spend the time to troubleshoot the issue the Sandforce controller has with the other hardware/drivers on that particular system.
I suspect it's a combo of #2 with heavy emphasis on #3 more than #1(but threads like this make me wonder a bit). lol
But regardless of all that it will still be a top rated controller whoever packages the components together and slaps their name on it. So in a nutshell here?.. Sandforce, Intel ,and mobo mfgrs themselves are the bigger bastards with most of the blame here. The rest falls on the consumers ability to deal with any potential hassles of getting it merged into their system.
Once the mobo mfgrs, Intel, and Sandforce get it worked out(and they surely will with credibility/sales on the line) these speedbumbs will quickly disappear. Many of the die hards have already worked though them with known workarounds for the time being. In the meantime some will fall back to other controllers and scream bloody murder though.