New system with raid 0 .. want to boot to my OLD system drive sometimes
 

Is that possible? I plugged it in but the bios doesn't see it.. Windows does, though.

Do I need to manage it through the raid controller in order to boot from it? Can I boot from a single drive while there is a raid 0 set up? I am a raid virgin :1orglaugh

All I want to do is be able to boot to my old drive from time to time

Also wondering if I can preinstall mobo drivers and everything before trying to boot from my old drive

Never ever go RAID0 if you have important data on the drives.. trust me.. i know :( better invest in a few more drives and go for a RAID5 or 6..(correct me if I'm wrong here, RAID raped virgin here as well)

As I understand it, if either drive fails on a Raid 0 setup... you are fucked. But my sister told me that I can set one up with 3 drives and somehow the extra one will back the other two up?

How would having a single mirroring the two acting as one not cut the performance in half?

I definitely understand than R0 is NOT safe, thanks :thumbsup

i like boots...

I finally just now got it to boot my XP Pro 32 bit install on the drive from my old computer.. but it was not easy


1. Go into bios, it can see the single drive from my old computer, but won't allow me to select it as a boot device

2. Select "configure all drives ide" or whatever it says like that (select ide where it says raid)

3. Save changes and exit

4. Go back into bios and select the single drive to boot from (I also disabled the two raid 0 drives.. well, both physical drives that make the array- so hopefully I won't fuck the array up)


Is there an easier way? The board has some kind of ide boot rom or something
I am completely virgin to using boot roms and raid controllers and all this shit

Well it worked.. booted back into Windows 7 64 bit

Sure is a pain in the ass, though

With RAID0 (striping) performance is roughly doubled because you get the speed of both drives. The setup with three drives is called RAID3 or RAID5. Basically the third drive holds a checksum of the others, so if any single drive fails the data is still readable. We have RAID5 arrays of eight drives apiece. Reads can use all drives, so the more drives the faster files can be read. The capacity is that of seven drives, with one used for parity.

RAID3 has one drive dedicated to parity and is good for sequential access, like videos. It slow for random writes, though, because all writes have to update the one parity drive.

The more popular RAID5 has a few blocks on each drive used for parity and is good for random access, like the OS. It's fast for reading because reads use all drives, but slightly slower than RAID0 for writes because writes have to update two drives, not just one. The writes may be executed parallel, though, so it's not always half as fast as RAID0. RAID5 is good balance between safety, capacity, and speed in many cases because most systems read files more often than write them.

That reminds me, MrMaxwell there's something else I'd like to chat with you about. Can you shoot me an email at ray @ bettercgi.com or give me a call at 979-530-1300.

I had a bad experience

I shot you an e-mail
I cannot remember, are you one of the people on here who likes me or one of the ones who hates me?

Very interesting post - thank you!

Whether Ray likes you or hates you, if he wants to talk to you it is well worth listening to him :thumbsup

Sides, from the info and detail he gave you I don't see how you could put him in your hater club. Just my :2 cents:



.

that is about the just of it, unless you boot it into a virtual machine. not sure how easy that will be in this case.

THAT is a good idea. I have never used a VM but I am pretty sure this cpu has the vx bit thing. Going to google virtual machines, now :thumbsup

Enjoyed a nice e-mail exchange. I like the guy. (That means a-lot, coming from me.)