I have 2 HDDs in a RAID 0 software array using nf4's nvraid (2 x 300 MAXTOR SATA). Recently my computer froze and I rebooted it to find out that windows lagged out on the boot screen until chkdsk came up.
Chkdsk froze on phase 1, 4% in (stayed on 4% for 2 hours). I have been searching around the internet and found some articles to suggest that CHKDSK'ng a RAID array may screw it up because of how striping works.
Here is a case of a RAID 5 hardware array and CHKDSK:
This place says dont do it:
Chkdsk being run on one of the disks
Chkdsk is a Windows utility that uses simple algorithms to recover data from a corrupt disk. Chkdsk can be started by the user or automatically by Windows if it detects disk corruption at boot time. (Windows will ask for confirmation before starting chkdsk but will start it anyway if no response is received after a number of seconds.) Chkdsk is not RAID-aware. Its algorithms only work in the simplest cases. In general, it must be avoided.
If chkdsk attempts to repair one or more member disks, the RAID data patterns will be destroyed, usually beyond recovery.
I have booted it up to Windows Recovery Console and gotten access to the files, and everything appears to be good. Im using the nvraid drivers in the Windows Recovery Console to read the drive. Should I go ahead and run a chkdsk? Or should I do a reinstall of XP?
I understand that RAID 0 is a risky setup, and I understand I could lose all my files. I just really like this install of windows and the files are worth enough to me to try to fix this problem.
Any help or input would be appreciated!