To test a log file for suspected damage, run the following command:
For example, to test a log file that is named as e014789.log, type: eseutil /ml e014789.log
If the log file passes the test, the following response appears:
Integrity check passed for log file:
If the log file fails the test, the following response appears:
CORRUPTION DETECTED in log file
Operation terminated with error -501 (hope so….)
You can use a single command to test all the log files in a folder.
To do this, open a command prompt window, and then change to the folder where the log files are located. Type the following command: eseutil /ml Enn
NOTE: Exchange cannot repair damage to log files that is the result of factors other than torn writes. Hardware failures that randomly damage a log file cannot be overcome because the lost data cannot be reliably reconstructed.
you can use one of the following recommended ways:
1. Locate a good copy of the damaged log file. Another copy may exist either on an Exchange online backup or on a recent server backup.
2. Discard the damaged log file together with all the log files that are newer than the damaged log file. Then restore a known good online backup of the Exchange database. You will lose any data that was logged after the damaged log file was created.
If these solutions are not workable….
You can repair the database by using called hard repair /p functionality of the eseutil utility. Before you do this, make sure that you back up all the database files in a storage group. You may also take help from a third party Exchange server repair tool to fix the corrupted log files and mount the database to MS Exchange server easily.
Hope it helps u !