![]() Now, let’s see what happens when I use Windows to take two of these and stripe them. It’s a single OCZ 120 GB SSD disk, connected via 3GBPS sata. Findings - Raid 0 Testingįor starters, here’s our benchmark. But along the way, I needed to know how it would perform. I’ve recently come into possession of some new SSD drives, and this time, I’m going to do it right, damn it! I wanted to finally have some resiliency in case one of my drives died. Rebuild #3.Īt this point, I had it with these janky solutions. Next, I decided to take three drives, two physical SSDs and a chunk of unpartioned space from a six year old spinner, and put them in a Raid-5.Īs it turns out, this kills the drive. Since then, I’ve had an SSD fail in a Windows Mirror, resulting in a total loss of VMs, as I didn’t have backup working. Two months ago, I had a number of SSDs in a Storage pool on Server 2012 R2, then decided I should go to the desktop experience, and moved to Windows 10. I’ve had a lot of issues in the FoxDeploy lab recently. In this post, I’ll share my results comparing hardware to software RAID on modern Windows 10, then to take things up a notch, I’ll see how a Storage Spaces volume with Parity (maybe Microsoft is charged money for using the word ‘Raid’, because they avoid that word like the plague!) compares to the hardware solution (Spoilers: it ain’t pretty) in pretty much every configuration I could think of. I’ll be revising this post heavily, adding some iometer numbers. ![]() Update: Turns out I was pretty wrong about Storage Spaces and have been totally schooled and corrected about them here, on Reddit and at Redmond.
0 Comments
Leave a Reply. |