We have a customer that the backup started failing
because it couldn't backup the exchange information
store, it turns out that they have a bad block on the
hard disk just where the exchange information store is,
we are currently getting event id 7 (bad block) in the
system log and event id 200 (exchange database
corruption) in the application log.
We are a bit loathed to low level format server and
reload for one bad block. We have tried running
chkdsk /f /r which moved a file (no name just number) and
then when run a second time it was clean. We also ran
scandisk with all options ticked.
We can obviously run eseutil to repair the exchange
information store but if its actually sat on bad block
then it is just going to get corrupt again.
Any suggestions?
Regards
Debbie
because it couldn't backup the exchange information
store, it turns out that they have a bad block on the
hard disk just where the exchange information store is,
we are currently getting event id 7 (bad block) in the
system log and event id 200 (exchange database
corruption) in the application log.
We are a bit loathed to low level format server and
reload for one bad block. We have tried running
chkdsk /f /r which moved a file (no name just number) and
then when run a second time it was clean. We also ran
scandisk with all options ticked.
We can obviously run eseutil to repair the exchange
information store but if its actually sat on bad block
then it is just going to get corrupt again.
Any suggestions?
Regards
Debbie