data corruption after diskeeper boot defragmentation

mborghimborghi
edited August 2003 in Hardware
hi, system specs are:
gigabyte 8PE667 Ultra
512MB DDR 333
Radeon 9500pro
2x Maxtor 60GB ATA133 driver in RAID0, using the onboard
Promise 20276 controller.
winXP SP1

well, i have defragmente the RAID array and everything went fine, BUT when i reboot after boot defragmentation, some file seems to be corrupted, i discovered this because the mouse does not work, the device manager tells that the driver file may be corrupt!, and it was. So i run chkdsk and many errors
appeared. I have also run chkdsk BEFORE defragmenting and there was NO errors. It seems that de MBFasttrack133 driver is not compatible with diskeeper (latest version).
I have these system setup since january and never had a problem with the RAID array, till yesterday :-(

If anyone have experienced this behaviour or similiar, your help will be appreciated. thxs

Comments

  • ghayesghayes
    edited August 2003
    What build of Diskeeper are you running? Build 430 was recently released and Executive Software is strongly encouraging customers to update to this build. From the ES web site:

    "Build 430 includes changes and improvements to the boot-time defragmentation operations to address an issue that could possibly cause the boot-time process to fail."

    From the 430 readme:

    "Also Note: The Diskeeper NTFS boot-time engines have been modified in this build to verify they have exclusive access to the volume being defragmented. This change ensures that no other drivers or services can modify the volume while the boot-time defragmentation is running. If the volume cannot be locked, an error message appears describing this and the boot-time defragmentation will not run."

    If you do NOT ensure that you "lock" the drive during a boot time defrag and some other process writes to the drive then file system corruption can occur. I'm actually shocked that Diskeeper has not been exclusively locking the drive with prior builds.


    - Greg/Raxco Software
    Microsoft MVP - Windows Storage Management/File System

    Disclaimer: I work for Raxco Software, the maker of PerfectDisk - a commercial defrag utility, as a systems engineer in the support department.
  • mborghimborghi
    edited August 2003
    Originally posted by ghayes
    What build of Diskeeper are you running? Build 430 was recently released and Executive Software is strongly encouraging customers to update to this build. From the ES web site:

    "Build 430 includes changes and improvements to the boot-time defragmentation operations to address an issue that could possibly cause the boot-time process to fail."

    From the 430 readme:

    "Also Note: The Diskeeper NTFS boot-time engines have been modified in this build to verify they have exclusive access to the volume being defragmented. This change ensures that no other drivers or services can modify the volume while the boot-time defragmentation is running. If the volume cannot be locked, an error message appears describing this and the boot-time defragmentation will not run."

    If you do NOT ensure that you "lock" the drive during a boot time defrag and some other process writes to the drive then file system corruption can occur. I'm actually shocked that Diskeeper has not been exclusively locking the drive with prior builds.


    - Greg/Raxco Software
    Microsoft MVP - Windows Storage Management/File System

    Disclaimer: I work for Raxco Software, the maker of PerfectDisk - a commercial defrag utility, as a systems engineer in the support department.

    I am using build 428, i dont think the problem is with the drive not being locked, bacause the defrag process comlpeted all the 5 stages sucessfully. No errors where reported.
    Thanks
  • ghayesghayes
    edited August 2003
    If you re-read what the DK Build 430 readme states:

    "The Diskeeper NTFS boot-time engines have been modified in this build to verify they have exclusive access to the volume being defragmented. This change ensures that no other drivers or services can modify the volume while the boot-time defragmentation is running. If the volume cannot be locked, an error message appears describing this and the boot-time defragmentation will not run."

    That means that previous builds DID NOT verify that DK had an exclusive lock and the boot time defrag would go ahead and run to completion even if other processes may have been writing to the drive.

    - Greg/Raxco Software
    Microsoft MVP - Windows Storage Management/File System

    Disclaimer: I work for Raxco Software, the maker of PerfectDisk - a commercial defrag utility, as a systems engineer in the support department.
  • mborghimborghi
    edited August 2003
    Originally posted by ghayes
    If you re-read what the DK Build 430 readme states:

    "The Diskeeper NTFS boot-time engines have been modified in this build to verify they have exclusive access to the volume being defragmented. This change ensures that no other drivers or services can modify the volume while the boot-time defragmentation is running. If the volume cannot be locked, an error message appears describing this and the boot-time defragmentation will not run."

    That means that previous builds DID NOT verify that DK had an exclusive lock and the boot time defrag would go ahead and run to completion even if other processes may have been writing to the drive.

    - Greg/Raxco Software
    Microsoft MVP - Windows Storage Management/File System

    Disclaimer: I work for Raxco Software, the maker of PerfectDisk - a commercial defrag utility, as a systems engineer in the support department.

    you are right, i have downloaded the 430 update.
    IF i decide to run the boot defrag again i will discover if this was the problem, ;-)
    thanks for your interest in help me.
Sign In or Register to comment.