Windows 7: chkdsk on reboot (windows 7)

I've searched the forums and found some people having similar issues to mine but not exactly.

This is a brand new build with a fresh install of windows 7. The boot drive (c is an SSD drive with very few applications installed. I have another drive (i that is a mirrored array (raid 1) of two 1 TB drives. It has a lot of data and other applications installed on it that I don't need to run "fast".

I rebooted the other day and chkdsk came up and said that my i: drive needed to be checked for consistency. I was a little shocked by this, but walked away for an hour or so and came back to the login screen of windows. I logged in and thought nothing more of it. I then tried opening one of my apps that's installed on the i: drive (adobe reader) and it said it couldn't find some files (or something to that effect). I uninstalled it (strange that it could find the files to uninstall...but whatever) reinstalled and everything was good again. I then rebooted later that day and chkdsk came up again on the drive. Rather than waiting this time, I just pressed a key to skip chkdsk. When windows loaded, I tried opening some apps that are installed on the i: drive and they wouldn't open...same problem as with adobe. I tried browsing some files on the i: drive and didn't see any problems at all. I opened a few pics and mp3s...all good. I rebooted again and of course chkdsk came on and went to 58560 of 252672 files (2%) almost instantly and now it's just hanging going through one file at a time VERY slowly. I'm pretty certain that it's nothing wrong with the drive phyiscally (there are actually two drives as mentioned above).

Any ideas here? As I said, I did do some searching and found some solutions to use chkdsk with a /x switch to tell windows to stop checking the volume. But I'm not sure that will resolve my "missing files" issue since most of my programs are installed on i: I'm going to wait out this current chkdsk running (it's on a different machine (obviously)), and see what happens.

just an update: it was chugging through one file at a time, and now it's blasting through each file saying "File record segment 67xxx is unreadable"

sounds like you have some bad sectors.