How to fix Exchange server error "Error – 1022=’JET_errDiskIO’ = Disk I/O error"?
The MS-Exchange server database generates various errors. These errors make it quite difficult to work smoothly. Sometimes it happens that the Exchange server database file refuses to open. On every attempt to open the database from the server, it is still unsuccessful. Exchange database corruption is one of the reasons for such behavior. Because of this, the data cannot be addressed. You cannot access the content of the database. To avoid such data loss situations, please use a backup. However, if the backup falls short of recovering data, perform exchange recovery with the help of a third-party tool.
Related to the previous topic, let’s study an error message. As discussed earlier, the Exchange server displays an error message on the screen when it tries to open the Exchange server database. The database cannot be opened, and when you view the error details, you see the following event log in the description:
Event type: Error
Event source: ESE
Event Category: General
Event ID: 489
Computer: Computer name
Description: Process name [process id] filename: an attempt to open the file [pathfile name] for read only access failed with [Error Code and Explanation]. The file open operation will fail with an error [-1022].
Root of the problem:
Tea “Error -1022=’JET_errDiskIO’ = Disk I/O error” occurs when a disk I/O error prevents Exchange from accessing the requested database page or check file. Also check the input/output or drive error log at the time of event 490. The problem occurs when the check file path is incorrect, it may be due to drive failure.
Solution:
To handle the above error, run “chkdsk /f /r” command. If running this command does not resolve the issue, check the permissions on the Exchsrvr folder. Make sure SYSTEM has full control of Exchsrvr and all subfolders (on each partition) that contain Exchange data.
If you cannot mount databases, you will need to troubleshoot any Windows NT file-level antivirus software that might be running on the Exchange server. Also check the drive or input/output error log at the time of the 490 event. Check and correct the path for the check file. You can also fix the root cause and use an updated backup to recover data from the database.
If all else fails, running Isinteg -fix and the ExMerge command on a new Information Store will also help fix the problem.
However, if no satisfactory results are found after using the above commands, go with a third party Exchange recovery tool. Many tools are available on the market whose main objective is recover exchange server.
Stellar Phoenix Mailbox Exchange Recovery is a sophisticated and useful tool that successfully performs Exchange server recovery in all cases of corruption. This Exchange recovery software recovers all data from .edb files contained in messages, notes, tasks, attachments and other objects.