Error 0x101f6: Unable to create volume snapshot
I'm backing up full computer to my Synology NAS for the first time and it keeps failing with the following error. The backup automatically restarts from the beginning of the backup and discards whatever backup state that was accumulated before the error. The back up folder is empty with no .tib file.
This the error that I repeatedly get. The backup has at least restarted a dozen times each time ending at over the 1.5TB mark.
3/25/2019 9:18:39 PM: Writing full version to file: VAL-PC_full_b1_s1_v1.tib
3/26/2019 1:28:50 AM: Pending operation 173 started: 'Creating partition image'.
3/26/2019 1:28:51 AM: Pending operation 173 started: 'Creating partition image'.
3/26/2019 1:28:51 AM: Error 0x101f6: Unable to create volume snapshot
3/26/2019 1:28:51 AM: Error 0x13c0005: Operation has completed with errors.
I then ran VSS Doctor and fixed a problem with "Some VSS shadow storages are misconfigured".
I ran it a second time to confirm that the problem was gone.


- Anmelden, um Kommentare verfassen zu können

I have monitored disk usage on my system and when there is very little disk usage the VSS Doctor will show I/O load unhealthy levels some of the time.
Other times it checks out all green as seen in this attached log.
What is IO load measuring? I'll try chkdsk but have low confidence this is the issue.
Unable to create volume snapshot is quite a generic error. Any way I can get more detailed logs?
Anhang | Größe |
---|---|
493723-165859.txt | 8.17 KB |
- Anmelden, um Kommentare verfassen zu können

The volume snapshot can be created on any of the drives where you are selecting data from for the backup task, and this tends to create the snapshot in unused areas of those drives.
I would recommend downloading and using the MVP Log Viewer tool (link below) and checking any of the other logs that Acronis creates, to look for any events being reported around the time when the backup to the NAS gives this error? The log viewer tool formats the logs to make them much easier to read, plus allows you to select the different types of log that are created.
- Anmelden, um Kommentare verfassen zu können

Do you have an SD card reader on this PC? If yes can you disable it and see if your problem goes away?
- Anmelden, um Kommentare verfassen zu können

Enchantech, tried with SD card readers disabled. Did not help.
Steve, I was using the log tool but now I discovered that the "Log View: Short" was the default selection in the tool. Toggling to "Log View: Regular" shows a great deal more detail about the error.
Not sure what the next steps could be to resolve this:
3/28/2019 10:49:01 AM: -07:00 14572 E000101F6: Error 0x101f6: Unable to create volume snapshot
| trace level: error
| line: 0x65b5eb7011094703
| file: c:\bs_hudson\workspace\790\processor\diskadm\da_commit.cpp:348
| function: DaProcessor::CommitImpl::OnDaError
| line: 0x65b5eb7011094703, c:\bs_hudson\workspace\790\processor\diskadm\da_commit.cpp:348, DaProcessor::CommitImpl::OnDaError
| $module: ti_demon_vs_17750
|
| error 0x70021: Unable to create volume snapshot
| line: 0xdf81da2c74ec50d5
| file: c:\bs_hudson\workspace\790\core\resizer\backup\output_stream.cpp:275
| function: `anonymous-namespace'::OutputStreamImpl::SetBitmap
| line: 0xdf81da2c74ec50d5, c:\bs_hudson\workspace\790\core\resizer\backup\output_stream.cpp:275, `anonymous-namespace'::OutputStreamImpl::SetBitmap
| $module: ti_demon_vs_17750
|
| error 0x10c44e: Failed to set snapshot bitmap.
| line: 0x3fec04e376b89f58
| file: c:\bs_hudson\workspace\790\core\fdisk\win_snapshot.cpp:610
| function: win_snapshot_volume::SetBitmap
| line: 0x3fec04e376b89f58, c:\bs_hudson\workspace\790\core\fdisk\win_snapshot.cpp:610, win_snapshot_volume::SetBitmap
| blocks: 0x0
| $module: ti_demon_vs_17750
|
| error 0x9: Unknown status.
| line: 0x2aacb7b2ab852ac
| file: c:\bs_hudson\workspace\790\core\fdisk\ver2\arch\windows\win_errors.cpp:40
| function: Fdisk::AddKstatusError
| line: 0x2aacb7b2ab852ac, c:\bs_hudson\workspace\790\core\fdisk\ver2\arch\windows\win_errors.cpp:40, Fdisk::AddKstatusError
| code: 0x57
| $module: ti_demon_vs_17750
|
| error 0xfff0: The parameter is incorrect
| line: 0xbd28fdbd64edb8f1
| file: c:\bs_hudson\workspace\790\core\common\error.cpp:307
| function: Common::Error::AddWindowsError
| line: 0xbd28fdbd64edb8f1, c:\bs_hudson\workspace\790\core\common\error.cpp:307, Common::Error::AddWindowsError
| code: 0x80070057
| $module: ti_demon_vs_17750
3/28/2019 10:49:02 AM: -07:00 14572 E013C0005: Error 0x13c0005: Operation has completed with errors.
| trace level: error
| line: 0x9f2c53c72e8bcec0
| file: c:\bs_hudson\workspace\790\products\imager\demon\main.cpp:714
| function: main
| line: 0x9f2c53c72e8bcec0, c:\bs_hudson\workspace\790\products\imager\demon\main.cpp:714, main
| $module: ti_demon_vs_17750
- Anmelden, um Kommentare verfassen zu können

Ed,
Your log shows a Windows error code 0x80070057. This is a sort of generic error code and there are a number of fixes on the net for it. Google it.
- Anmelden, um Kommentare verfassen zu können

I have tried everything that I could find about this error code and nothing is working :(
I've tried:
1. The decimal setting
2. The registry key
https://www.drivereasy.com/knowledge/solved-0x80070057-error-message-in…
Anything else I should try?
- Anmelden, um Kommentare verfassen zu können

Ed, I can only suggest going back to basics here to try to isolate what / where the problem is?
First, try creating another backup task to a local, external disk drive and see if you get the same VSS errors. This will help show that this is not specific to backups to your Synology NAS.
Next, if you are seeing VSS issues regardless of the backup destination.
Do a Repair install of your ATI 2019 application - this is done by simply reinstalling over the top of your existing application without doing an uninstall. Download the latest #17750 Installer from your Acronis account and run this as Administrator / from an Administrator account, then take the Repair option shown.
If this does not make any difference, then you are getting into the realm on this being a Windows issue as suggested by Enchantech earlier.
Open an Administrator command prompt and run the command SFC /SCANNOW to perform an integrity check of your OS files.
Identify the make of your internal disk drive(s) and go to the makers support site then download any full disk diagnostic tools they may provide - run a whole disk check of all internal drives.
Dedicated diagnostic utilities from the disk manufacturers take the longest time to complete the checks, but provide the most accurate methods of checking whether the disk is good or needs replacement:
- Western Digital drives: Data Lifeguard Diagnostic for Windows
- Seagate disks: SeaTools for Windows
- HGST disks: HGST Windows Drive Fitness Test (WinDFT)
- Intel SSDs: Intel Solid State Drive Toolbox
- Samsung drives: Samsung Magician
- ADATA drives: ADATA SSD ToolBox
- Kingston SSDs: Kingston SSD Toolbox, Kingston SSD Manager
- Transcend SSDs: Transcend SSD Scope
- Silicon Power disks: SP ToolBox
- Toshiba disks: Toshiba PC Diagnostic Tool Utility
- Anmelden, um Kommentare verfassen zu können