Exchange 2010 Database Corruption 531 and 218
Hi EE
We are constantly getting alot of warnings and errors regarding event ID 531 and 218.
Is there a possible solution to this?
Cheers
Goraek
We are constantly getting alot of warnings and errors regarding event ID 531 and 218.
Is there a possible solution to this?
Cheers
Goraek
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I have read all the links you provided, but still not able to get any answers. And yes, we are using DAG.
Currently Database is mounted or Dismounted?which exchange version you are using in dag members?Since when you are facing this issue?did you install any updates reccently?
ASKER
We havent done the check if the databases. All our databases are mounted. Im not sure if they did a firmware upgrade but thats the question i need to ask the storage guy. I coukd check it but im only there yo help out. Its exchange 2010 sp2.
It could possibly be the firmware upgrade? But will need to check. In the interim any other suggestions?
It could possibly be the firmware upgrade? But will need to check. In the interim any other suggestions?
How many mailbox databases do you have currently ?
As it looks could be possible Database corruption ... is the event comming for some specific Database or all .... can you understand is it for some SAN LUN or something ?
When did the events starts any upgrades or activity done around that corner ? I have seen this once during some SAN or Storage Upgrade
- Rancy
As it looks could be possible Database corruption ... is the event comming for some specific Database or all .... can you understand is it for some SAN LUN or something ?
When did the events starts any upgrades or activity done around that corner ? I have seen this once during some SAN or Storage Upgrade
- Rancy
How many servers do you have in your DAG?
Are your database copies up to update/in sync?
I would create another mailbox database, check that no errors are occurring, move a test/temp mailbox to it and if no issues, move the remaining mailboxes to it and then drop the corrupt database.
Are your database copies up to update/in sync?
I would create another mailbox database, check that no errors are occurring, move a test/temp mailbox to it and if no issues, move the remaining mailboxes to it and then drop the corrupt database.
ASKER
We have alot of databases from 50GB to 350GB, we have 6-7 databases.
Its on different datastore, but from a SAN LUN, i'm not too sure coz I didnt get the see the SAN console as to how its all configured.
But apart from that, any other suggestion?
Its on different datastore, but from a SAN LUN, i'm not too sure coz I didnt get the see the SAN console as to how its all configured.
But apart from that, any other suggestion?
From the events it should give some idea if they have some database name or info ?
- Rancy
- Rancy
ASKER
Yup, this is the event info
Event ID 531
Information Store (1976) The database engine attempted a clean write operation on page 6634378 of database C:\database.edb. This acton was performed in an attempt to correct a previous problem reading from the page.
Event ID 218
At '11/11/2012 1:11:40 AM' the copy of database 'database' on this server experienced a performance problem. Failover returned the following error: "There is only one copy of this mailbox database (database). Automatic recovery is not available.". For more detail about the failure, consult the Event log on the server for other storage and "ExchangeStoreDb" events.
Event ID 533
Information Store (1976) databasemail: A request to write to the file "C:\exchange.log" at offset 932352 (0x00000000000e3a00) for 512 (0x00000200) bytes has not completed for 82 second(s). This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
Event ID 510
Information Store (1976) database: A request to write to the file "C:\database.edb" at offset 17305993216 (0x0000000407848000) for 65536 (0x00010000) bytes succeeded, but took an abnormally long time (187 seconds) to be serviced by the OS. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 111531 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
Event ID 531
Information Store (1976) The database engine attempted a clean write operation on page 6634378 of database C:\database.edb. This acton was performed in an attempt to correct a previous problem reading from the page.
Event ID 218
At '11/11/2012 1:11:40 AM' the copy of database 'database' on this server experienced a performance problem. Failover returned the following error: "There is only one copy of this mailbox database (database). Automatic recovery is not available.". For more detail about the failure, consult the Event log on the server for other storage and "ExchangeStoreDb" events.
Event ID 533
Information Store (1976) databasemail: A request to write to the file "C:\exchange.log" at offset 932352 (0x00000000000e3a00) for 512 (0x00000200) bytes has not completed for 82 second(s). This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
Event ID 510
Information Store (1976) database: A request to write to the file "C:\database.edb" at offset 17305993216 (0x0000000407848000) for 65536 (0x00010000) bytes succeeded, but took an abnormally long time (187 seconds) to be serviced by the OS. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 111531 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
Is there some specific DB on "C:\database.edb" ??
- Rancy
- Rancy
ASKER
Specific DB? What do u mean?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
We've excluded Exchange processes and paths/location as they havent been previously apparently. But since then its been working ok, however there are some occasions spike in the morning which is fine.
We'll monitor and see how it goes.
We'll monitor and see how it goes.
ASKER
Also, just want to confirm and clarify, the above event IDs, is it possible that AV could be causing these errors? Also could cause the corruption? They may be some pages that are corrupted, but until we take it offline and scan, we won't know. And also if we unmount, a risk of not able to remount would be disastrous!
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Cool it looks like the AV exclusions fixed it.
It's been a few weeks, and nothing.
I guess it looks like its working, but its also worthwhile to do a DB scan ensuring they are perfectly normal :)
Thanks for all the help.
It's been a few weeks, and nothing.
I guess it looks like its working, but its also worthwhile to do a DB scan ensuring they are perfectly normal :)
Thanks for all the help.
ASKER
Great info!
DB scan is what i would be more worried as you would need to run eseutil /g and will run at 4GB per hour and would be a issue
- Rancy
- Rancy
This error it`s result write operational problem in during FW storage upgrade. Perhaps one or few pages in databases is corrupted. Please dismount database and check status database use Eseutil /G and Eseutil /K Eseutil /K Checksum Mode