Rastalovich
New member
Got 2 Max 200g drives Raid 0 stripping.
Was compacting an archive today, something in the region of 4g, prob 2g compacted.
Anyway, during this process I decided to install a game that`s come into semi-open beta "9Dragons", I installed it and ran it - rar had about 40 mins left to go.
Now I wouldn`t b1tch about this too much, coz todays pcs, with their dc cpus boast being able to multitask - ha!
So anyways, ran the game and it crapped. Stuck on it`s loading screen and from my g15 display I can see the rar is still going. No combination of ctrl-alt-del, start menu key, alt-tab, will allow me to exit this stuck screen to desktop, so I figure bide my time till the cpu shows 0 on the g15 (the rar is most likely finished), then I`ll reset the pc.
Luckily enough, the rar made a sound when it finished and sure enough the cpu display read 0.
I reset, went off to get a drink, and came back to a Raid error blue-screen-menu thing I`ve never seen b4. Informing me that one of my drives if effed and giving me very little options of what to do next. Nothing did anything - so I selected the option to power down (check the cables etc).
I gave em a wiggle, nothing strange looking, and powered up. Windo$e got to desktop, restarted and the pc went to the blue screen again. Eff sake I`m thinking. Did another reset and windo$e boots to desktop - and everything looks fine. Tried the very limited Abit raid checking thing, and it says all drives are fine and there is no raid problem.
I figure something must be wrong, and there`s only games on these drives, so I can afford the crap-out if they must - run it through a defrag and see if it survives. It did, and I`m still here.
Question the first:
Q. Are there any `good` disk checking tools for the Raid system(s) other than Abit`s stock one that doesn`t seem to do much at all ?
Q. Did the situation come about similarly to how if u interupt an IDE drive doing something and can result in a scandisk check before stuff gets back into order ? a drive goes `dirty` as an example.
Q. Raid 0 - and it seemed to sort itself out - is this normal ?
Q. Can I change my shorts now, cos I have to be honest I hadn`t seen that screen b4 and I mentally panic`d 2000% ?
Was compacting an archive today, something in the region of 4g, prob 2g compacted.
Anyway, during this process I decided to install a game that`s come into semi-open beta "9Dragons", I installed it and ran it - rar had about 40 mins left to go.
Now I wouldn`t b1tch about this too much, coz todays pcs, with their dc cpus boast being able to multitask - ha!
So anyways, ran the game and it crapped. Stuck on it`s loading screen and from my g15 display I can see the rar is still going. No combination of ctrl-alt-del, start menu key, alt-tab, will allow me to exit this stuck screen to desktop, so I figure bide my time till the cpu shows 0 on the g15 (the rar is most likely finished), then I`ll reset the pc.
Luckily enough, the rar made a sound when it finished and sure enough the cpu display read 0.
I reset, went off to get a drink, and came back to a Raid error blue-screen-menu thing I`ve never seen b4. Informing me that one of my drives if effed and giving me very little options of what to do next. Nothing did anything - so I selected the option to power down (check the cables etc).
I gave em a wiggle, nothing strange looking, and powered up. Windo$e got to desktop, restarted and the pc went to the blue screen again. Eff sake I`m thinking. Did another reset and windo$e boots to desktop - and everything looks fine. Tried the very limited Abit raid checking thing, and it says all drives are fine and there is no raid problem.
I figure something must be wrong, and there`s only games on these drives, so I can afford the crap-out if they must - run it through a defrag and see if it survives. It did, and I`m still here.
Question the first:
Q. Are there any `good` disk checking tools for the Raid system(s) other than Abit`s stock one that doesn`t seem to do much at all ?
Q. Did the situation come about similarly to how if u interupt an IDE drive doing something and can result in a scandisk check before stuff gets back into order ? a drive goes `dirty` as an example.
Q. Raid 0 - and it seemed to sort itself out - is this normal ?
Q. Can I change my shorts now, cos I have to be honest I hadn`t seen that screen b4 and I mentally panic`d 2000% ?
