Most database corruption (database consistency errors) comes from hardware issues mainly Hard Disk issues. The first place to look is, IO subsystem not behaving well.
Try looking into the system event log. You may find disk related errors which could be the root cause of your corruption.
You may see disk related errors like:
11/11/2011 11:11:11 Cissesrv Error None 24606 N/A TESTSERVER01 "Logical drive 3 configured on array controller P410i [Embedded] returned a fatal error during a read/write request from/to the volume.
Logical block address 257513711, block count 1024 and command 32 were taken from the failed logical I/O request.
Array controller P410i [Embedded] is also reporting that the last physical drive to report a fatal error condition (associated with this logical request), is located on bus 0 and ID 3. "
11/11/2011 11:11:11 Cissesrv Error None 24606 N/A TESTSERVER01 "Logical drive 3 configured on array controller P410i [Embedded] returned a fatal error during a read/write request from/to the volume.
Logical block address 257513711, block count 1024 and command 32 were taken from the failed logical I/O request.
Array controller P410i [Embedded] is also reporting that the last physical drive to report a fatal error condition (associated with this logical request), is located on bus 0 and ID 3. "
11/11/2011 11:11:11 dmio Warning None 35 N/A TESTSERVER01 dmio: Disk Harddisk2 block 257512687 (mountpoint E:): Uncorrectable read error
11/11/2011 11:11:11 dmio Information None 29 N/A TESTSERVER01 dmio: Harddisk2 read error at block 257512687: status 0xc0000185
11/11/2011 11:11:11 Disk Error None 11 N/A TESTSERVER01 The driver detected a controller error on \Device\Harddisk2.
If you find any disk related issue like above than call some Hardware engineer to fix the issue or replace the HDD. The above error messages leads to a disk failure if no action is taken.
No comments:
Post a Comment