Hello. After running some PowerShell scripts to create reports on our Exchange (2007) Environment. I ran into an issue where the script kicked back an access error to one of the Transaction Logs of a Mailbox Database. After logging into the Server containing the Mailbox Database, I received the following error in the Event Viewer: Event Type: Error Event Source: NTFS Event ID: 55 Description: The file system structure on disk is corrupt and unusable. Please run the chkdsk utility on the volume "Exchange Database". Now the weird part is that our Exchange Mailbox Database is mounted and receiving mail fine (that we can tell). The error message in the event viewer is not talking about the Drive containing the Transaction Logs, just the Exchange Database. What would be the best first option? I have already done the following: http://support.microsoft.com/default.aspx/kb/932578?p=1 Should I run a the chkdsk utility on the database volume or use the eseutil? Should I focus on the Transaction log first or go by what the Event Viewer says and focus on the Mailbox Database? They are both located on the same SAN

Running ESEUTIL shouldn't be necessary unless Exchange is reporting errors. If I were you, I'd take an immediate backup and then schedule an outage window, during which I'd (1) take a backup, and then (2) run CHKDSK. If it makes you feel better, after you're reasonably satisfied that the error is fixed, you could run ESEUTIL but don't do a repair because you could lose data. If there are errors found by ESEUTIL, I would follow the next recommendation below. If you have the disk space, you might consider creating new databases and moving all the mailboxes to them, and then just blow away the old volume completely. That's just what I'd do. I'm sure that there other opinions.-- Ed Crowley MVP"There are seldom good technological solutions to behavioral problems."."Justin The Heartbreak Kid" wrote in message news:e54bbea6-d3f5-469a-b94b-1c2a947ddabf...Hello. After running some PowerShell scripts to create reports on our Exchange (2007) Environment. I ran into an issue where the script kicked back an access error to one of the Transaction Logs of a Mailbox Database. After logging into the Server containing the Mailbox Database, I received the following error in the Event Viewer: Event Type: ErrorEvent Source: NTFSEvent ID: 55Description:The file system structure on disk is corrupt and unusable. Please run the chkdsk utility on the volume "Exchange Database". Now the weird part is that our Exchange Mailbox Database is mounted and receiving mail fine (that we can tell). The error message in the event viewer is not talking about the Drive containing the Transaction Logs, just the Exchange Database. What would be the best first option? I have already done the following: http://support.microsoft.com/default.aspx/kb/932578?p=1 Should I run a the chkdsk utility on the database volume or use the eseutil? Should I focus on the Transaction log first or go by what the Event Viewer says and focus on the Mailbox Database? They are both located on the same SANEd Crowley MVP "There are seldom good technological solutions to behavioral problems."