An error occurred when an attempt to determine the minimum input/output (I/O) block size for the volume failed
Topic Last Modified: 2007-11-16
The Microsoft Exchange Server 2007 Management Pack for Microsoft Operations Manager (MOM) monitors the Windows Application log on computers that are running Exchange Server 2007 and generates this alert when the event or events specified in the following Details table are logged.
To learn more about this event, do one or more of the following:
Review the description of the event that includes the variables specific to your environment. From the MOM Operator Console, select this alert, and then click the Properties tab.
Review all events that have been logged that meet the criteria of this MOM alert. From the MOM Operator Console, click the Events tab, and then double-click the event in the list for which you want to review the event description.
Details
Product Name |
Exchange |
Product Version |
8.0 (Exchange Server 2007) |
Event ID |
491 |
Event Source |
ESE |
Alert Type |
Warning |
MOM Rule Path |
Microsoft Exchange Server/Exchange 2007/Common Components/Extensible Storage Engine |
MOM Rule Name |
An error occurred when an attempt to determine the minimum input/output (I/O) block size for the volume failed. The cause depends on the error listed at the end of the Description. |
Explanation
This Warning event indicates that an unexpected error was encountered while trying to use the volume specified in the message. Specifically, an error occurred when an attempt to determine the I/O block size for the volume failed.
The cause depends on the error listed at the end of the Description section of the event. The most frequent causes are listed below.
Error -1032 = 0xfffffbf8 = 4294966264 = Jet_errFileAccessDenied = Cannot access file. The file is locked or in use. Another process has locked the file. Antivirus software may mistakenly quarantine a file, or a backup process may temporarily deny access. A flat file backup system or antivirus software may be running against the database, check file directories, or the M drive. This error can also occur if the permissions on the folder that contain the files for the Exchange stores are not sufficient for the stores to function properly.
Error -1022 = 0xfffffc02 = 4294966274 = Jet_errDiskIO = disk I/O error. The -1022 error is a generic error that appears whenever a disk I/O problem prevents Exchange from gaining access to a requested page in the database or to a check file. A disk or controller failure may have occurred and access to the entire drive has been lost, sometimes temporarily. The physical drive may no longer be accessible or have an incorrect file system, such as accidentally specifying the transaction log files path to the CD-ROM drive. Check the System log for I/O or drive errors near the time of the 491 event. This issue may occur because the path for the check file (such as E00.chk) is not correct, which may be caused by a drive failure.
User Action
To resolve this warning, do one or more of the following:
For error -1032, change the folders that contain the Exchange store files to default permissions. Configure the flat file backup and antivirus software to not scan the Exchange store subdirectories or the M drive. Use Exchange-aware online backup and antivirus software.
For error -1022, ensure that the drive for the Exchange store files is accessible and that the path for the Exchange store files is specified correctly. If it is, run chkdsk /f /r. If Chkdsk does not resolve the issue, examine the permissions on the C:\Program Files\Microsoft\Exchange Server folder, where C:\ is the directory to which you installed Exchange 2007. Make sure that System has full control of the Exchange Server folder and all subfolders on each partition that contains Exchange data. If you still cannot mount the databases, troubleshoot any Windows NT file-level antivirus software running on the Exchange server. Check the System log for I/O or drive errors near the time of the 490 Event. Check and correct the path for the check file (such as E00.chk).
For information about ESE error codes other than the ones explained in this topic, see the following Microsoft Knowledge Base articles:
After correcting the root cause, if the database is inconsistent, restore from online backup. If there is no valid backup, you can restore the database to consistency using the hard repair (/p) functionality of the Eseutil utility, run isinteg -fix until all fixes are removed, mount the database, and then ExMerge to a new, blank database. Before doing this, you should always back up all information store files in a storage group (*.log files, *.edb files and *.stm files).
For More Information
To search the Microsoft Knowledge Base articles based on criteria that generated this alert, visit the Search the Support Knowledge Base (KB) Web site.
To review Exchange 2007 event message articles that may not be represented by Exchange 2007 MOM alerts, see the Events and Errors Message Center.
If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.