Does what it says.

I bought one of these to aid raid to my home archives. I've had it for 3 years with no issues and recently expanded with a second. Overall i'm happy with this product and recommend it. Performance is good, configuration seamless.

Works as expected, setup was quick and easy on my Windows 10 PC.Running two 256GB mSATA drives from donor laptops in a RAID 0 for fast loading games =oP

working flawless in an old windows 2000 professional computer with on an intel D865 perl motherboard.Very easy to set up.

This is my 4th inexpensive RAID controller. The first 3 were either DOA, or came with drivers that wouldn't install. This one was surprisingly easy to install, easy to use and so far, hasn't had any problems.My setup:Windows XP/SP3 -- on a P4.3 x 2TB Seagate Barracuda LP in eSATA enclosures1 x 1.5TB Seagate Barracuda 7200.11 in eSATA enclosureI'm running Windows XP which has a 2TB Disk limit. Setting up a RAID5 with three 2TB drives requires that you setup two RAID5 groups (2TB each), and then concat them in XP. That gives you the full 4TB capacity... and RAID5 (awesome!)I purchased a separate internal-SATA to eSATA adapter because all my disks are in eSATA enclosures, and I don't have room or power in my P4 box. That adapter cost me $5.CONS:As far as I can tell, there is no way to get at the SMART data from the individual drives. I have SmartMonTools installed on my XP box to notify me via SMS if/when a drive experiences any sort of failure. These drives are SMART compatible, but the RAID controller doesn't give you an interface to retrieve the data, or a way for SmartMonTools to monitor the disks.The jumpers used to configure the external/internal ports are small and easy to loose.UPDATE (11/12/2011): OMG! I can't believe I paid so little for this card. I have a couple of things to add to my review. 1) I've been playing around in the RAID Controller GUI. It is so easy to add, delete, update, repair and do all the RAID admin things... right from the GUI. 2) The performance is through the roof! I was able to get 60% saturation on my GB Ethernet copying files via a Windows share. The bottle neck on that copy was actually the HDD on the client node.I think I need a second one of these!!!The internal-SATA to external-eSATA adapter was also a great investment. I can't believe how much faster my external drives are now that I've got them connected via eSATA instead of USB-2.0. I have 1 port on my RAID controller that isn't being used by the RAID-5 Volume Group... being that all the ports are Hot-Swappable and easily accepts my other SATA drives, it couldn't get any better.UPDATE (11/16/2011): OMG!!! In my original review posting, I indicate that you can't get the SMART data from the disks. Well... it turns out that you can get an application from SiliconImage (the chip MFG) that does exactly what I've got SmartMonTools setup to do -- monitor the health and notify me if there's an issue. Very easy to use... even easier than SmartMonTools.I had an unfortunate experience. One of my 2TB drives died. At first I thought it was the SATA card, or cable, or power supply... or something (it couldn't be the drive... it was only 12 days old). But.. it was the drive. It was dead. At the time that it died, I had no indication there was anything wrong. The RAID is on a box in my basement. I rarely ever sit in front of it, so I didn't see the little pop up saying "An Event Occurred." When I did finally sit in front of the box, I saw the pop up... and opened the RAID tool... to see that I only had 2 Disks in my RAID Group. I took the dead drive back to the store, got an exchange, and now my RAID Group is rebuilding.So... unlike other inexpensive RAID controllers I've used, when "An Event Occurs" it doesn't hang or kill the system. This RAID kept on working... and I continued to be able to do IO to it... and really hadn't noticed the degraded mode performance drop.The one thing I notice though... and I'm not sure how I feel about this.... the RAID controller GUI is telling me that it's going to take 23 hours to rebuild my RAID-5. I don't know how accurate that is, or if it's just a conservative estimate. But I would think that I could read the data from 3 2TB disks... and write the data back to those 3 2TB disks faster than 23 hours. I understand that the RAID controller doesn't know what parts of the disk are blank and therefore it has to read the entire 2TB for 2 of the disks... and calculate the parity. But Really?!? 23 hours?But... I have to say... so far, I'm liking this card!UPDATE (1-4-2012): It turns out that 23 hours wasn't a conservative estimate. In fact, it wasn't conservative at all... it actually took 37 hours to rebuild my RAID-5. Having said that... I'm not sure it's a problem, but simply a fact of life. While it's true that I wasn't able to get steller numbers when running a Disk IO benchmark while the RAID was being rebuilt... I really didn't see any performance issues doing my day-to-day work on the system. And... my benchmark scores after the RAID was rebuilt weren't too far off what they were when the RAID was being rebuilt. So... 23 or 37 hours... I guess I shouldn't care. After the horrifying experience of having one of my brand new 2TB drives fail, I was sure I would have an other failure soon.... so far, my drives have been spinning without any additional interrupts... and this RAID controller has proven to be a very smart purchase.