Data corruption after running Diskeeper
We have seen situations like this come up, especially when the report is accompanied by reports of "randomness".
Diskeeper, when it operates, may be accessing pieces of the disk your users or applications may not be accessing on a day-to-day basis. These pieces of the disk may be getting "flaky", in other words, getting to a point where they’re getting intermittent read/write errors for one reason or another.
A file written on a bad sector will almost always become corrupted. If it is a system file, such as ntoskrnl.exe, you may get a crash and may not be able to reboot. Anything that writes to the disk may use the bad sector, and since Diskeeper does so much writing, it is possible that it was involved.
It is a good policy to run
chkdsk
(with the
/f
and
/r
qualifiers) on any disk before you first defragment it and, whether you are defragmenting or not, you should run
chkdsk
at least weekly. This will clear up errors in the file system and mark any bad sectors found so that they can no longer be used. Bad sectors are not common, but can develop at any time.
We recommend you:
-
Have current backups
-
Run CHKDSK /f /r on any problem disks
-
Use manufacturer’s diagnostics to identify any drives needing imminent replacement, and get them replaced
If this FAQ helped, please let us know. If you didn't find the answer to your question here please e-mail
|
