How do i find a file that chkdsk says has a bad index entry
Windows 2003 server suddenly getting a NTFS error (system event ID 55) requiring that chkdsk be run. The process always gives 'deleting an index entry from index $0 of file 25". Then it inserts an index entry into the same file. How can I tell which file 'file 25' is ? No more info about that particular file is given.
When this happens there are a lot of SRV error 2000, which I have not been able to find a resolution for, and the spooler service stops and restarts. The service is used by our scanning solution. Not sure whether the spooler is causing the corruption or the corruption is causing the service to stop. Has anyone had this combination of issues? Any help would be appreciated.
When this happens there are a lot of SRV error 2000, which I have not been able to find a resolution for, and the spooler service stops and restarts. The service is used by our scanning solution. Not sure whether the spooler is causing the corruption or the corruption is causing the service to stop. Has anyone had this combination of issues? Any help would be appreciated.
ASKER
Sandeshdubey,
Thanks for your response. I was afraid there would not be an easy way.
I have run chkdsk /f several time, same file has the same problem, but so do others. We are backed up. No sectors being recovered. Service pack is up to date, will check the firmware. It's not a cluster , and the file allocation size is ok, so i did not apply the hotfix from the article.
My next move is to move all the data off to a NAS, format the volume, and hope the corruption does not travel with it.
Thanks for your response. I was afraid there would not be an easy way.
I have run chkdsk /f several time, same file has the same problem, but so do others. We are backed up. No sectors being recovered. Service pack is up to date, will check the firmware. It's not a cluster , and the file allocation size is ok, so i did not apply the hotfix from the article.
My next move is to move all the data off to a NAS, format the volume, and hope the corruption does not travel with it.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
More than likely that file was open and being written to when the power failed, so it gets scrambled, if chkdsk cannot reassemble/recover the file, then it will delete it so the entire file system does not have issues, but some times chkdsk will delete a critical system file, but it has no choice but to correct the file system.
You should let chkdsk run to completion.
I doubt the hard drive is failing, unless you start seeing "Sectors" being recovered during chkdsk.
Anyway, backup your critical data immediately. Then run chkdsk /f. To be on the safe side.
Also install the latest hotfix and Service Pack on the server.Get the SCSI/RAID firmware updated also check the h/w health from the vendor.
Refer this link also if it helps:
http://www.eventid.net/display.asp?eventid=55&eventno=1210&source=Ntfs&phase=1