Hi all. This is a duplicate of a thread in the HD forum, as it mutated from an earlier HD question, but thought maybe this would get more relevant hits here. Basically I am adding x1 500Gb WD HD to a system which already has one of those drives, as well as a Seagate 250Gb drive for backup/other purposes. Advice received was to setup a 100Gb-ish RAID 0 for XP 32bit and apps, with rest as a RAID 1 for data.
I copied the Intel RAID drivers from my Mobo CD to a floppy, set up my SATA drives as RAID in Bios, then setup a 120Gb RAID O in the Ctrl+I utility on my x2 500Gb WD drives, followed by the rest taken up for the RAID 1. All seemed to work okay, both arrays then show up as 'healthy'. (I used the default stripe size, wasn't confident enough to fiddle!)
So I reboot from the Windows CD, press F6, push in the floppy, XP ticks away loading setup, I use the 's' key command to specify the floppy, select the relevent option of 4 that show up (the one that includes ICH10R, as specified by my mobo manual), and that's when it all goes wrong! (actually I got a couple of random errors before this point, but I only got each 1 once - I therefore used the non-Windows way of creating the RAID floppy from my mobo CD twice to create 2 new copies - using these new floppies I now always get to this point)
Whicever disk I use I get: "File iastor.sys caused an unexpected error (4099) at line 2113 in d:\xpsp\base\boat\setup\oemdisk.c."
Help! Any ideas anyone????
My only 2 thoughts (based on zero RAID experience and not even fully understanding what it is until this week), are either (a) that both RAID arrays showup when the PC is turning on as 'bootable' - is there a way I should have made the RAID 1 not bootable?, or, (b) the drivers from the mobo CD are duff - I know you can download some from the Intel site instead, would these solve the problem?
The only floppy drive I currently have access to is on the machine in questions, so in order to get to them I'll need to install XP on the 3rd (non RAID) HD and create floppies from them in there I guess. (If I do this, how do I take Windows off this 3rd drive before restarting the PC to install it on the RAID 0 array?)
Really appreciate your help, utterly lost with this one....
I copied the Intel RAID drivers from my Mobo CD to a floppy, set up my SATA drives as RAID in Bios, then setup a 120Gb RAID O in the Ctrl+I utility on my x2 500Gb WD drives, followed by the rest taken up for the RAID 1. All seemed to work okay, both arrays then show up as 'healthy'. (I used the default stripe size, wasn't confident enough to fiddle!)
So I reboot from the Windows CD, press F6, push in the floppy, XP ticks away loading setup, I use the 's' key command to specify the floppy, select the relevent option of 4 that show up (the one that includes ICH10R, as specified by my mobo manual), and that's when it all goes wrong! (actually I got a couple of random errors before this point, but I only got each 1 once - I therefore used the non-Windows way of creating the RAID floppy from my mobo CD twice to create 2 new copies - using these new floppies I now always get to this point)
Whicever disk I use I get: "File iastor.sys caused an unexpected error (4099) at line 2113 in d:\xpsp\base\boat\setup\oemdisk.c."
Help! Any ideas anyone????
My only 2 thoughts (based on zero RAID experience and not even fully understanding what it is until this week), are either (a) that both RAID arrays showup when the PC is turning on as 'bootable' - is there a way I should have made the RAID 1 not bootable?, or, (b) the drivers from the mobo CD are duff - I know you can download some from the Intel site instead, would these solve the problem?
The only floppy drive I currently have access to is on the machine in questions, so in order to get to them I'll need to install XP on the 3rd (non RAID) HD and create floppies from them in there I guess. (If I do this, how do I take Windows off this 3rd drive before restarting the PC to install it on the RAID 0 array?)
Really appreciate your help, utterly lost with this one....