Help a noob: two SSDs in Raid 0

libbykino

n00b
Joined
Jul 15, 2010
Messages
7
I'm self taught in computer building, and Raid configuration is a new obstacle for me. I understand basically how it works, but most of the information I find online is two to even six years old (makes me feel even more out of date...)

my current drives:
1 Intel X25-M 80GB SSD with Windows 7 and all my other games/programs on it
1 pretty standard 750GB HDD storage drive with pictures/music/videos/other crap on it
1 TB external drive for backup

My SSD is great, I've had it for about 7 months now, been working fine, no problems whatsoever. I love the performance and I'm hooked on SSDs for life now. The only problem is storage, obviously. 80GB isn't enough space for my OS and all the programs I want to run from my SSD.

The plan is to buy a second 80GB Intel X25 and run them in Raid 0. I'm not terribly concerned about data loss, since I backup everything onto an external already. BUT... I'm a complete noob at this and I have some (probably simple) questions:

1. Will I be able to add a second SSD and set them up in Raid without reformatting the drive I already have?

2. If I have to reformat, like I suspect I will, is there a way to simply copy my entire HD to my external drive temporarily and then restore it to the Raid array after setting it up? What program (if any) would I need to help me with this?

3. Should I use a Raid controller card? My mobo is an Asus P6T with Raid 0/1/5/10 support built in, but would a card be better? Is it like graphics cards, such that onboard functionality is inferior to separate cards?

4. The exact SSD I have is no longer manufactured (wow that was quick!), will the SSD that replaced it (same size, same manufacturer, same series) be alright to run in Raid?

5. Am I over-complicating my problem? IE: should I just suck it up and replace my current SSD with a bigger one and forget about Raid altogether?

Any advice at all would be helpful, thank you!...

-------------
Success story!:

Just to let everyone know how this turned out...

I decided not to partition the G1 SSD. Creating a partition on the disk without TRIM would probably increase it's long-term efficiency, but only if I were using it alone. Making a striped Raid with two drives of different sizes would have been extremely unstable, and so I would have had to partition the G2 SSD as well. Losing 40 total GB to a little extra long-term security isn't worth it to me. Rather, I choose to participate in regular external backups, take the full advantage of my drives' capacity now, and worry about reformatting again later should the need arise.

I also decided not to bother cloning. Well, that's a lie... I tried cloning for about a day and eventually gave up in frustration. "BOOTMGR is missing".... I hate you so much! Instead, I sucked it up and just did a reinstall of all my programs... which really ought to be done every once in a while anyway, and I'm glad I did.

Overall, I have to say this was an excellent learning experience for me, and definitely not without its several speedbumps. I'd never dreamed that Raid could increase the performance of my already blindingly-fast SSDs so much. Read/write speed is now no longer my performance bottleneck, and is in fact now the coolest thing about my computer.

Thank you all for your help and advise! See you next time I get the itch to upgrade...

__________________
 
Last edited:
1. Nope.
2. Acronis True Image
3. For RAID-0, Intel will be fastest, but an addon card will guarantee that you can move it between computers.
4. Yes.
5. Up to you.

Other: RAID will disable TRIM support on the drives, but it's not generally a big problem.
 
Thanks! Alright, so here's my plan of attack:

-Wipe my external drive clean
-use Acronis True Image to copy my current SSD (boot drive) to the eternal drive
-Boot from the external drive and wipe the current SSD
-Install second SSD and set up Raid 0 array
-use Acronis True Image to copy the boot drive to my new SSD array
-Boot from SSD array
-Wipe external drive and set it up to backup the array

Any reason that won't work? Basically, I'm trying to avoid having to reinstall Windows and all my other programs.
 
1. Yes, if you have Intel controller (ICHxR) you can; note that this is the only software driver that i know that can do this. It can transform single disk to RAID0, RAID0 to RAID5, expand, and other things like partition-based RAIDs.

3. onboard has lowest latency, and is software based just like many cheap add-on PCI/PCI-express RAID cards. But there's nothing wrong with software RAID, especially RAID0. The Intel solution could be the fastest too, if you enable write caching (dangerous but uses your RAM as writeback buffer).

4. You have gen1 X25-M now? That one does not support trim, the new one will.

5. Yes, just buy a gen2 X25-M and don't RAID them; then you at least have TRIM on one. I suggest you use the TRIM-ed disk for Windows instead.

If you do want to use RAID0, consider secure erase on your current Gen1, then create the RAID0. When installing Windows on the RAID, you have the option of increasing the spare capacity, from default 6.8% to 20 or 25%. This will help keep your SSDs fast after a time of (real) usage. Especially on Intel this is recommended, as they come with very little spare capacity by default. You do this simply by creating a C: partition of 80% capacity; leaving the other (visible) 20% unused and unpartitioned. This trick only works if the drive is brand new or just had a secure erase done on it.
 
The more answers I get, the more questions I have... o_O Beginning to think I'm getting in over my head.

So I'll be able to expand my single SSD onto the raid array if I have the Intel controller software you mentioned... is that free? Do I already have it? Do I use it before or after I set up the array?

I guess I don't understand what TRIM is... I thought it was a function of all SSDs, so I'm a little unclear as to why the one I have now wouldn't have it, and why that's a bad thing. I've added all my comp specs to my signature, if that helps at all. If TRIM is such a big deal, I'm inclined to just pay more for a larger SSD and ditch the old one altogether (though that seems like such a waste).
 
libbykino: i highly recommend you follow my route and setup your SSDs cleanly, performing a secure erase on the one you have. This destroys all data; so this is what you do:

1. create image of your current SSD contents as soon as you have the second SSD
2. secure erase your current SSD (not the new one; though it cant hurt!)
3. re-install Windows on the new SSD capable of TRIM, create partition1
4. create partition2 on the old SSD, not capable of TRIM
5. verify performance, driver used (msahci or iastor.sys) and alignment ("GOOD")

partition1 could be 100% of the capacity; but if you want to make it faster after long use of time, you can opt to use only 90%. Some research suggests this may greatly benefit your drive. The theory behind it is quite complex; though i have some URLs if you like.

partition2 should have space reserved; like 80%.

The left over space should NOT be used and NEVER be written to, or this trick will not work! Just to make things clear: 80% of 100GB SSD would be 80GB, so 20GB is 'unpartitioned' and unused.
 
Oh, i made a mistake. If you want to restore the image, it would regain the original partition size. To remedy that, you would need to 'shrink' your current partition, with all data on it. This can be done with plenty of free space, and choosing the 'shrink' option in the disk management screen (right click your partition). If you can not shrink enough, while you do have enough free space, then you have to defragment your SSD first.

Note that normally you should never defragment your SSD. In this case it may be required to shrink enough space; i.e. data at the end of that partition needs to forced off to the beginning of the partition. Since you will be doing a secure erase after, you won't have any performance effects from defragmenting the SSD.

This does make the procedure a bit more complex, though. If you just want to go the easy route, then i understand. Good luck!
 
Another post:
perhaps you can just keep the partition of the new TRIM-capable the same. So you just copy all contents from old SSD to new SSD then new SSD is your system disk with TRIM. :)

Then you secure erase the old SSD and repartition it, with 80% capacity allocated; leaving the 20% unused. 80GB = 74GiB or so, so make 60GiB partition, leaving 14GiB unused.

This is much easier, and still quite effective. Note that due to the image-process, all data stored on your system drive is now much faster to access, as well. This is due to it being written in one big chunk. So a good option in my eyes. :)
 
Alright I think I'm understanding you now. Thanks very much for your help, by the way!

Will I need to make a smaller partition on the new SSD with TRIM, or are you saying it's fine as-is because it has TRIM?

Basically what I think I'm doing is: copy the old SSD to the new SSD before setting up the array, then secure erase the old SSD, set up a partition with 60GB on it, and then set up the Raid array with the new SSD and the partitioned old SSD. And all the data from the new drive should expand onto the array just fine?
 
Just to let everyone know how this turned out...

I decided not to partition the G1 SSD. Creating a partition on the disk without TRIM would probably increase it's long-term efficiency, but only if I were using it alone. Making a striped Raid with two drives of different sizes would have been extremely unstable, and so I would have had to partition the G2 SSD as well. Losing 40 total GB to a little extra long-term security isn't worth it to me. Rather, I choose to participate in regular external backups, take the full advantage of my drives' capacity now, and worry about reformatting again later should the need arise.

I also decided not to bother cloning. Well, that's a lie... I tried cloning for about a day and eventually gave up in frustration. "BOOTMGR is missing".... I hate you so much! Instead, I sucked it up and just did a reinstall of all my programs... which really ought to be done every once in a while anyway, and I'm glad I did.

Overall, I have to say this was an excellent learning experience for me, and definitely not without its several speedbumps. I'd never dreamed that Raid could increase the performance of my already blindingly-fast SSDs so much. Read/write speed is now no longer my performance bottleneck, and is in fact now the coolest thing about my computer.

Thank you all for your help and advise! See you next time I get the itch to upgrade...
 
Back
Top