Skip to main content

Cannot create volume snapshot

Thread needs solution

I started receiving error messages that Acronis cannot create volume snapshot. No changes to system since last successful backup - no software installed, no updates, nothing visible to me. I've tried with volume shadow copy service set to manual and off. I've tried setting Options-> Advanced->Performance->Snapshot for backup to Acronis snapshot, which just leads to a different error about unable to read part of the disk.
I've uninstalled, reinstalled, updated to latest, created new backup profiles. Same results all the time.
This is a disk/partition backup, which has been working for years.
Windows 7 Pro, 64 bit
Acronis 2017 build 8058

I tried to attach the system report, but attachments don't seem to be working

0 Users found this helpful

David, please download a copy of the Acronis VSS Doctor tool and run this as Administrator on your computer to see what issues this finds.  If the tool offers an option to fix any issues found, then allow it to do so.

The VSS Doctor report is attached.

Shadow storage is disabled on C and D disk, hence the warning about misconfigured storage sizes.

The volume with insufficient storage is some sort of restore volume created by the vendor.

No idea why group policies block reading shadow writer status.

Seems sort of strange that the system report utility would create a nearly 9MB zip file and this forum sets the max upload at 8MB.

Attachment Size
520028-176344.txt 47.9 KB

David, in the VSS Doctor output, it shows:

VSS Shadow Storages Status

Status: Warn
Description: Some VSS shadow storages are misconfigured

Storages:

ForVolume: C:\
OnVolume: C:\
Used: 2525 MB
Allocated: 2952 MB
Maximum: 7322 MB
Minimum: 320 MB
VolumeSize: 238 GB
Available: 64 GB
TargetMaximum: 23 GB
MaximumGreaterThenMinimum: True
MaximumIsEnough: False
MaximumIsNotReached: True
AvailableIsEnoughForMaximum: True
IsOk: False
Description: Recommended Maximum storage size is 10 percent of volume size

Did you see an option for the tool to fix the above issue?  If it is given, please try taking it.

The small 99MB partition should not be an issue as this is a hidden/system partition (either System Reserved or EFI System) and are shown as you see on most computers.

There appear to be problems with the SSD which may be showing up as the shadow copy problem in ATI. Although the SSD passed chkdsk with no problems, using a different backup program I still encounter errors that appear as failures to read sectors, typically 10-20 in a row at widely spaced addresses. I tried backing up booting from an Acronis rescue disk and also encounter the bad sectors. It seems pretty clear there is a problem with the SSD. Whether that is what causes Acronis to complain about failures creating the shadow copy is an open question.

David, if you are seeing unreadable / bad sectors on any drive, then that would be a concern and should be addressed with urgency before the drive decides to turn up its toes!

Do you have any earlier / older backups for the SSD that you could use for a recovery to a new drive?  If yes, then do file copies of any other non-system data that may have changed since that time or try making a Files & Folders backup of the same (depending on the amount of data).

Shadow copies are stored in unused space on the volume being backed up, so VSS could also be hitting the same read errors on the same drive.

I ordered a new drive earlier today, even before your reply. Having had a drive failure once in the past, I'm painfully sensitive to the issue, so yes, I have backups of the system disk. I back up to three different external drives, located in two different physical locations. Two drives are backed up with ATI, one with a different product. And then of course, there is my BackBlaze cloud backup,.. I've had a file backup of the drive running for something like 8 hours. It's going painfully slow, presumably as it tries to work around the bad sectors. As I mentioned above, shadow storage is disabled, so there are no shadow copies, so that doesn't account for VSS errors.