Has anyone experienced this on this IDE RAID kontroller(128MB cache)? I got a 1TB raid-5 array(6*200GB Seagate Barracuda) and its been up for like 1 month. One time after a reboot it started hanging on initializing the board, and i got a bit worried that it was initializing the array and escaped it and proceeded booting w2k3. A week after i set up weekly synch of the array as recomended from the maintanance chapter in the manual. It started yesterday evening and took a heap of time. Today around 12:30 i had to shut it down to retreieve a 250GB SATA HDD that mounted as a stand-alone disk on the server for moving data, before delivering it to a warranty exchange. Afterwards i started the server, went out and came back 6 hours later. The the synch said 89% and a worrysome popup message told me the driveletter on which contains the whole raid-5 array was corrupt and i needed to run chkdsk on it. I let the synch(not same as init array, big diff ) complete and then ran chkdsk d: /f /x and it started correcting a heap of records and recovering a lot of files. At the end i had lost 100GB of data and i was almost paralized... this wasnt supposed to happen on a very expensive raid controller. Does anyone have a real clue of what happened here and how i can prevent it from happening again? I hadnt come around to get a good backup solution running yet and it seems ive misplaced my trust on this raid controller. I have not yet written any new data to the raid volume, but i guess chkdsk has when running. Any advice on recovering my data and on what might have happened?