Deeper information about chkdsk results
I have a server that failed to run backup over the weekend, and when diagnosing the issue have found that a corruption of the file system is to blame. I've run chkdsk and only one item has been found.
Does anyone know of a way to translate what "Index entry Logs in index $I30 of file 68199 is incorrect".
I am trying to determine if the file/entries affected are minor (e.g just a log file) or the corruption is something more significant (e.g. the main copy of the registry) before I run chkdsk /f. I know the corruption has to be addressed ether way, however it would be nice to have more details about the corruption before I commit to chkdsk /f. and a subsequent reboot.
Does anyone know of a way to translate what "Index entry Logs in index $I30 of file 68199 is incorrect".
I am trying to determine if the file/entries affected are minor (e.g just a log file) or the corruption is something more significant (e.g. the main copy of the registry) before I run chkdsk /f. I know the corruption has to be addressed ether way, however it would be nice to have more details about the corruption before I commit to chkdsk /f. and a subsequent reboot.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.
I have recommended this question be closed as follows:
Accept: mbkitmgr (https:#a42075778)
If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.
seth2740
Experts-Exchange Cleanup Volunteer
I have recommended this question be closed as follows:
Accept: mbkitmgr (https:#a42075778)
If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.
seth2740
Experts-Exchange Cleanup Volunteer
It looks like file is under different claster that is registered in allocation table.
When you run chkdsk then program is going through index and compare with physical file allocation. It there is an issue it is correcting index for file location.