Verifying file system

[Guest]

Hi
I'm trying to look into an issue in which I got an MS exchange error regarding disk IO. I need to verify whether the error is caused by database damage in the file system. What would be the safest and surest way to verify this? Is there anything more powerful than chkdsk or should I consider any special switches in my case?
Thanks
John

 

[Jeff Patterson [MSFT]]

John,

Disk I/O errors are normally hardware related (controller, drive, etc...).

The best way to determine whether or not you have file system corruption on
a volume is to run Chkdsk with the /F switch. When you run Chkdsk in
read-only mode, it may falsely report corruption because the volume wasn't
locked for exclusive access by Chkdsk.

For more information, please refer to the following article:

187941 An Explanation of CHKDSK and the New /C and /I Switches
http://support.microsoft.com/?id=187941

Thanks,

Jeff Patterson
Microsoft Support

Hi
I'm trying to look into an issue in which I got an MS exchange error

regarding disk IO. I need to verify whether the error is caused by database
damage in the file system. What would be the safest and surest way to verify
this? Is there anything more powerful than chkdsk or should I consider any
special switches in my case?

 

[Guest]

Hi Jeff
Thank you for your reply. Yes I understand that I/O errors are usually hardware related, but we also had this incident of a trend scan micro (anti virus for exchange) holding up exchange's resources in a cluster mode. This is probably the reason why I got an Information Store's 1022 error with Event ID of 482.
I guess I will have to try the /F switch to really make sure we dont have any faulty hardware.
Any other suggestions would be appreciated.
Regards
John