I hope I can be concise here, I tend to go into fantastic detail sometimes.

The facts:

Two 200 gigabyte seagate harddrives
Raid 0 array
Harddrives bought groundbreaking new about a year ago (possibly 2 at the most)
Worked fine in anticipation of a few days ago
Both harddrives show up in Device Administrator
In device administrator properties, Disk 0 shows up as “volume unreadable, MBR unreadable, 0 megabytes used, 0 megabytes whole,” etc.
Disk 1 shows up as “MBR, 398 gigabytes whole, 398 gigabytes free”

In disk management, it shows disk 1 as “online” but the volume shows as 186 gigabytes free, failed” and it says “seconadary disk missing”.

Disk 0 is shown, but with an “unreadable” error, and the only option is to “exchange to basic disk” (which i reflect kills it)

When I click on disk 1, I have a “reactivate option” but when I click it, it says secondary disk missing.

Does anyone know what I can do to force it to reconnect as a raid? I’m hoping that disk 2 is “unreadable” because it doesn’t realize it’s in a raid with the first disk, and that a simple RAID fixing program can fix it.

And no… I don’t want to send it to the 00/ hour recovery specialists.
Additional details:

If it matters any, I’m by Windows XP Pro with Service Pack 3. I’m pretty sure it was a software based RAID (I told windows to make the RAID 0 under disk management), and it was NTFS. The whole thing was about 400 gigabytes, but about 200-300 was really used.

I do have two RAID controllers, and last night i noticed to my surprise that one of my drives was connected to one of my controllers, and the other to the other controller. I’m not sure how that happened, because I don’t remember ever putting them on separate controllers. But, no one in my family knows how to work with high level computer stuff, so I guess I had done that mistake when I first set up my computer or something. But still, it worked for a year or so up in anticipation of sometime this week…

I doubt it’s a virus issue, because I have been updating my symantec antivirus corporate lately. Plus it’s the only dead drive out of like 6 partitions (3 drives whole).
@ Simples xD, the thing is, I’ve got a pretty rudimentary knowledge of computers. After all, I did build the computer around 2003, and started upgrading everything (so technically by now, it’s my third computer, since pretty much all the parts have been upgraded and swapped out about 3 times). Apparently I knew what I was doing considering the harddrives/RAID ran just spiffy for over a year.

A random issue happened recently, and I’m hoping to see if anyone here has constructive information I can use. Not random “you don’t know how to use computers so why’d you even try” stuff.

And before you try the “you should have backed up” mantra, I was seriously considering getting to that in mid July. It just so happens an act of God beat me to that.
Even if that ‘connect it the right way’ proposition was constructive. I overlooked that part of your answer. But I did rearrange it in every conceivable orientation I may possibly come up with, and all of them led to the same issue (one drive saying it’s looking for the second drive; and the second drive saying it’s unreadable). The cables are not at fault any, I swapped them out with the same result.
@don’tknow;

Thanks anyhow for looking into it even if! Unfortunately, this is a raid 0 array, in which case data is shared equally between the two drives, so it’s the opposite; where if one drive fails, neither of them work. haha, just my luck. I guess it serves me right for valuing speed and capacity over reliability. I got my speed and capacity after all, and got lack of reliability as probable

Best answer:

Answer by Simples xD
Connect it the right way and see what happens. i reflect you have fried your drive over that 1 year period of time. these things happen.
You shouldn’t do things like this to your home computer unless you absolutely know what your doing…

Add your own answer in the comments!