Problems after switching from RAID 1 to RAID 0

st3

Member
Oct 23, 2002
128
0
0
I?m going to try and keep this as concise as possible. I added another HD to my system (500GB PATA Seagate). Since I couldn?t use it in RAID 0+1 I decided to backup my raid 1 array and convert it to RAID 0 (and regularly back that up with the new drive). Initially I couldn?t get the array to format in windows after I set it up. After some initial troubles I finally got that to work. The next problem that has arisen is that I can?t restore the backup onto the array, I keep getting some I/O error message. Additionally, Norton disk doctor and the windows error checker both have problems checking the ?drive? (array).

So I figure that maybe one of the drives is going bad. Fire up some DOS based tools (including the Hitachi DFT) and all of them check out OK. Which leads me to believe it is a software (driver?) based problem. I have the latest driver version (which isn?t that new). If it was a problem with the drivers I would have thought it would have been a problem when I was running them in RAID 1, and I never did have a problem.

Some other notations: During this troubleshooting process I have taken the drives out of RAID, reformatted and restored the backup to (a) drive. Everything worked fine. I will also point out that during my testing of the drives with DOS based programs I was having some problems with stability (programs crashing, hanging etc).

Any insight is appreciated.
 

RadiclDreamer

Diamond Member
Aug 8, 2004
8,622
40
91
What backup application are you using? Some such as ghost have trouble setting the image back to an array
 

st3

Member
Oct 23, 2002
128
0
0
Powerquest Drive Image. I've used it with this setup before and have had generally good look (an older version of ghost however was not so kind).
 

Tsaico

Platinum Member
Oct 21, 2000
2,669
0
0
Also, are you loading drivers for your Raid device and not the generic ones on the XP disc? I had problems with the data getting corrupted during installation of XP when I used generic XP, but when I used the current drivers the problem went away.