Further to my last post, I figured out the problem. So here it is if any of you encounter this same problem. We have a NAS and we have moved several of our SQL databases to the filer. The beautiful thing about this technology is that you can set it up and the operating system doesn't know any different. Through the explorer window, it looks like another drive. This way, we can have several databases on that server but residing on the NAS.
I went through the event viewer, system log and discovered that the first event id created referenced this same location but, it put f:\ and then the rest of the information, which indicated it was the NAS. I was then able to go to the NAS and try to open these files and they were corrupt and I wasn't able to open them. Microsoft has an article on this particular problem (Microsoft Knowledge Base Article - 246026 ) here are the details:
Cannot Delete or Repair Corrupted File on NTFS Volume
View products that this article applies to.
This article was previously published under Q246026
When you try to delete a file on an NTFS volume, you may receive the following error message:
Cannot delete file name: The file or directory is corrupt and unreadable.
The System event log in Windows NT 4.0 contains the following message:
Event ID: 41
Description: The file system structure on disk is corrupt and unreadable. Please run the chkdsk utility on the device with label "Volume_name"
The System event log in Windows 2000 contains the following message:
Event ID: 55
Description: The file system structure on disk is corrupt and unusable. Please run the chkdsk utility on the volume "Drive_letter:"
If you run Chkdsk against the volume, Chkdsk may or may not make repairs, but afterwards you still cannot delete the corrupted file.
This behavior can occur if the NTFS volumes' Master File Table (MFT) is corrupted. The short and long file name pairs that are stored in the directory index record and the file names that are stored in the associated File Record Segment (FRS) contain case-sensitive characters that do not match.
NTFS supports case-sensitive (POSIX) file names, but Chkdsk does not check file names in case-sensitive mode.
For example, assume that the directory index record has a BADFILe.TXT entry but the FRS has a BADFILE.TXT entry for the file name. NTFS views this as being invalid or corrupted, but Chkdsk compares only the names and ignores the case. It does not make repairs.
To resolve this issue, back up the volume that contains the corrupted file(s) and exclude the corrupted file(s) from the backup job. Reformat the volume, and then restore from the backup.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.