Corruption on drive

Hi,
Hope someone can set me straight here.
I recently installed Diskeeper Light on my XP Pro (dual booting) Drive F:\
and over the last two weeks on two occations I have received a message come up on the screen.
"Diskeeper has detected corruption on drive (F please run CHKDSK /F

How come Diskeeper Light is running in the Background. Drive F: is not Fragmented Diskeeper had come up with "Congratulations You Have No Fragmentation On Your Drive ".
What actually does CHKDSK do, I don't even know where I can find it and how to run it.
Is it save to run.
Is it like Scan Disk in 98SE.
thanks
hawk22

 

Hi Hawk,

Chkdsk is XP's disk diagnostic/fix.

Can be run two ways:

Through the HD's tools menu - bring the HD up > right click > properties > tools > check. That will schedule chkdsk on next bootup - does it before the apps load (safe mode)

Or, from a command box. Run > cmd > ok and then in the white on black dialog box enter the chkdsk command.

Someone else can address Disk Keeper. XP's built in defrag was written by Disk Keeper.

Regards - Charles

 

Diskeeper runs as a service in the background to monitor program usage in order to prepare a placement strategy for defragmentation. It may also monitor the degree of fragmentation.

There is usually an option for turning off the "performance monitor" part of the background service, but that option may not be available in the Lite version. In any case, CPU and memory usage is minimal.

 

Simply put, Diskeeper recognized that you had errors on your F drive and wouldn't run until they were fixed. That means you have somthing writing to F that is generating errors. Quite often (and I'll assume F is a secondary (non System) drive that you are using for backups or Windows is using for Updates) these are nothing more than index errors and you'll get a saved file like found.0000 or found.0001 after CHKDSK has run.

Not to worry, Diskeeper is behaving exactly as its supposed to.

 

Yes, chkdsk is pretty much the same thing as scandisk on older systems.

To do a complete scan (and at this point you probably want to)
- open a cmd window (the DOS window thing) via start~run~cmd
- at the prompt type in chkdsk c: /r (assuming it's C: you want to fix and note the space before /r)
- answer Yes to all the questions about doing the deed at next boot and then reboot.

Chkdsk will fix drive problems with either /f or /r switches. /r just does more including checking individual files (at least it does on NTFS) and checking the drive surface.

 

Thanks Guy's I have done that now but the scans went through with no hitch, no problems reported so I am glad all is well, just wondering if Diskeeper made some false alarm.
hawk22

 

It's best to err on the side of safety. But then chkdsk is not very talkative, so the error may have been fixed, anyway.

Thanks for following up.

If you are going to use a third-party defragger, you may want to turn off XP's boot optimization with its own defragger so that the 2 aren't working at cross-purposes.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Dfrg\BootOptimizeFunction

Change the value data for "Enable" to N.

Also, because the Lite version does not have a boot defragging option, you may want to combine its abilities with those of PageDefrag which, despite its name, defrags pagefile, registry hives, and other files that can't be defragged by Diskeeper.

http://www.sysinternals.com/ntw2k/freeware/pagedefrag.shtml

The 2 combined make a pretty efficient defragging solution.

 

Look in the event viewer to see what chkdsk found. In the left pane, click application and then in the right pane under source, look for winlogon.