Salta al contenuto principale

Unable to create volume snapshot

Thread needs solution

I have been trying to backup two internal hard drives - first to an internal, then to an external ESATA. The backups I am trying to run are generally run manually.

I continue to see this error:

19 Information 10/3/2011 10:19:47 PM Locking partition E:...
20 Error 10/3/2011 10:20:01 PM Operation with partition '5-0' was terminated.
Details:
Unable to create volume snapshot (0x70021)
Tag = 0xDF81DA2C74EC5084
Failed to set snapshot bitmap. (0x10C44E)
blocks = 1D1C0EFF)
Tag = 0x14181C22EF45ADCC
Not locked. (0x9)
code = E0000008)
Tag = 0x2AACB7B2AB852AC
21 Error 10/3/2011 10:20:01 PM Unable to create volume snapshot
22 Error 10/3/2011 10:20:01 PM Failed to set snapshot bitmap.
23 Error 10/3/2011 10:20:01 PM Not locked.
24 Error 10/3/2011 10:20:01 PM Operation has completed with errors.

I saw previous entries concerning this problem with older versions of Acronis, and I have followed their recommendations:

I ran chkdsk /r
I uninstalled ATI 2012, then used the Acronis Cleanup Utility, then reinstalled
I ran the Acronis report utility, but I do not know if I should post it here

I am so tired and disappointed with this program.

0 Users found this helpful

Is the external eSata connected even when trying to image to the internal drive?

Is the internal drive an physical one or a separate partition of a single one?

Do you have any encryption software running such as TrueCrypt or Bitlocker?

I wonder if the case now is that the fltsrv (the new name for snapman) is not installed properly due to a left over snapman in th eWindows driver folder. Having said that, I have both snapman and fltsrv on one of my VM's, but the snapman entry is not in registry, you might still have this lurking.

Did you use the 2012 or 2011 cleaner?

The external was connected when I tried to image to internal. I will disconnect the extenal.

The internal is a physical hard drive.

I do not have any encryption software.

I will look for old version(s) of Snapman and delete them.

I did not realize there was a 2012 version of cleaner. Can you give me the link? I will download and run it, and reinstall again.

Before you delete snapman.sys manually on your hard drive you will need to make sure it doesn't exist in registry, otherwise you'll get a BSOD at boot time.

The 2012 cleaner lives at http://kb.acronis.com/content/24545

As Colin says, that would be a very strong caution against deleting snapman.sys manually. I can tell you that, in my own case at least, the TIH2012 set-up does install its own snapman.sys driver file (version 3.12.0.634) as well as the fltsrv.sys driver file (version 1.0.0.30) for both 32-bit and 64-bit Windows systems. And both are included as required system start-up services (Start=0x00000000) in the registry under all of my OSes.

It's possible that snapman.sys isn't always needed. (Perhaps it's just for backward compatibilty with other Acronis apps as I have Disk Director installed along with TIH.) But you definitely don't want to remove that driver file if it's included in your registry's system start-ups. As a required driver, you might not even be able to boot into Safe Mode if it's missing.

The problem has been resolved.

I uninstalled ATIH 2012, and this time used the 2012 version of the ATIH cleaner.