Acronis SnapMan conflicts with Dk Svr 9 + Undel Svr 5

Discussion in 'Acronis Disk Director Suite' started by alerter, Mar 21, 2005.

Thread Status:
Not open for further replies.
  1. alerter

    alerter Guest

    Has anyone else encountered disk write buffer conflicts between Acronis' SnapMan drivers (Partition Expert 2003 bld 292) and Executive Software's Diskeeper Server 9 and Undelete Server 5?

    Everything boots to desktop AOK.

    Eventually, SnapMan writes a single error message to the System EventLog and then schedules a CHKDSK to be performed. Diskeeper displays an error dialog about deferred disk writes not completing properly (writing nothing into the EventLog) and the Undelete Server RecycleBin becomes spruiously corrupted. Needless to say, this requires a shutdown/restart to clear. No data loss, but a definite sw driver conflict, as disabling SnapMan eliminates the problem. This is on NT4 post-SP6a + all HotFixes.

    Seems that with each new version of Diskeeper and Undelete, Acronis SnapMan develops conflicts. (Very similar Acronis conflicts cropped up when Dk 8 and Undel 4 first came on the scene.)

    Is there an updated version of SnapMan that eliminates this new conflict?

  2. alerter

    alerter Guest

    More info on this...

    SnapMan.sys (v1.2.0.53) and UdDrv.sys (v5.0.108.0) are not playing together well. Each wants to be a BOOT time driver and in an ideal world, both manage to get along.

    Now, however, whenever SnapMan is allowed to load at BOOT, once a desktop is established, there will eventually be some kind of interruption in the communicaitons between the UdServe (background service) and the NetUnd (interactive desktop app) processes in Undelete Server.

    This interprocess communications interruption causes logical corruption to one of Undelete Server's local volume Recovery Bin folders. Files and folders themselves in the Recovery Bin are not corrupted. The corruption is that UdServe and NetUnd fail to agree on what resides in and what has been purged from the Recovery Bin.

    This logical corruption causes locks to be thrown on empty ophanded files/folders within the Recovery Bin. These empty folders should be deleted, but because UdServe and NetUnd have fallen out of synch with each other, these folders remain in the Recovery Bin.

    Then when Diskeeper Server (v9.0.524.0) tries to run an automatic defragmentation on the same volume, DkS detects disk discrepancies, usually in the form of MFT entry discrepancies. A chkdsk is thrown, requiring a system shutdown and restart to execute. This is another possible conflict with SnapMan, as orphaned folders/files in the Recovery Bin have no correlation with MFT discrepancies.

    When CHKDSK subsequently runs, it never reports finding any actual problems on the volume, not even when run with the /F and /R switches.

    Again, all of these problems go away if/when SnapMan is manually disabled.

    Again, this is not the first time SnapMan has had problems with major new releases of Undelete Server and/or Diskeeper Server.
  3. Acronis Support

    Acronis Support Acronis Support Staff

    Apr 28, 2004
    Hello alerter,

    Thank you for your interest in Acronis software (

    We regret to inform you that Acronis Partition Expert is not supported any longer because it is rather obsolete version. Please download free trial version of Acronis Disk Director Suite 9.0 from and see whether the problem remains. If so please send a letter with the description to

    Thank you.
    Ilya Toytman
Thread Status:
Not open for further replies.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.