Can I RAID two SSD of the same size but different brand?

[videopho]

One is OCZ Vertex2Plus and A-DATA is another.
Actually OCZ is 60gb and A-DATA (Microcenter branded) is 64gb.
Is it RAID0'able?

 

[Spikesoldier]

i would double check to make sure that they have the same controller onboard.

but that shouldnt stop you from throwing them into a RAID 0 stripe, just the configuration wouldnt be ideal.

 

[VirtualLarry]

I think it could end up somewhat unstable, mixing controller types for RAID 0.

Vertex 2 Plus is NOT a SandForce controller like the Microcenter/A-Data one.

 

[groberts101]

I've mixed controller types just to play around and test along with seeing a handful of others messing about as well but VirtualLarry is nearly on target about the effect.

It's not so much the stability as it is the varying internal algorithms which use TRIM and GC quite differently(even at different times. Not to mention the distinct differences in bandwidth for certain parts of the spectrum and even based on data type used.

Will be basically like throwing the extra low end grunt of the Sandforce based drive away and then conversely throwing out the incompressible write speeds of the Vertex Plus. Is not so bad though if your unable to match accordingly for proper raid in the short term. Wouldn't be planning on running it indefinately though.

 

[dac7nco]

One is OCZ Vertex2Plus and A-DATA is another.
Actually OCZ is 60gb and A-DATA (Microcenter branded) is 64gb.
Is it RAID0'able?

I've tried this experiment... It is an incredibly BAD idea. OCZ is the most unreliable (but funny) manufacturer, but I tried to RAID 10 with two Intel 80GB + one 160GB (partitioned), split into four slices of 40GB each. The result was heinous fuckery. Two of three drives were unwritable as Photoshop scratch drives/cache, after two months.

Daimon

 

[videopho]

it was my suspicion as well as I agreed with most of you.

 

[dave_the_nerd]

You can RAID anything. But your computer may decide to take a nap from time to time.

 

[Emulex]

that's just a weak raid controller. it's very common to replace 1 drive at a time and have it rebuild then you can expand your raid. if different drives didn't work - this would be impossible. been doing this for years with hp's raid controllers (with BBWC/FBWC) and LSI controllers - works great. heck i had a old scsi drive fail and i popped in a 146gb because it was cheaper than trying to find a new 36gb and it's 36/36/146gb - no problems.

cheap soft-raid controllers - problems. but if you don't spend $50 on a LSI controller (like the br10i i have for sale with 8 ports using a fan-out cable included in deal) - then well you shouldn't be playing with raid.

and of course use raid-edition drives you should know by now that only a few folks have written custom drivers to handle consumer drives (qnap/drobo) - the free raid solutions and hardware raid don't tolerate this. qnap abstracts the error correction to their own solution so if a AV drive (tler=0) and a raid edition drive (TLER=8) and a consumer drive (30-180 seconds) is handled well with the drivers then you don't have that problem - but you must tune your o/s to handle long timeouts. iscsi is pretty cool because you can withstand 10 minutes of timeout and continue in most operating systems - some apps might freak out (sql) but the system won't BSOD. slick.

so you get what you pay for still counts here.