TI 2020 - VSS errors
I can't seem to find a way to correct the following error in VSS Doctor (see attached). Disk Manager and CHKDSK both say the partition is just fine. Need some guidance here. TIA
Anhang | Größe |
---|---|
Joel-DiskMgmt.png | 42.79 KB |
Joel-VSS-error.png | 88.44 KB |


- Anmelden, um Kommentare verfassen zu können

Thanks for your response. I used the VSS Doctor to assign a drive letter and then ran CHKDSK /f to the affected partition. No effect. That trick worked on the other EFI / Recovery partition, but not so lucky here.
I'm sure I'm not the only one to ever have this problem. Maybe I need to explore the vssadmin command.
- Anmelden, um Kommentare verfassen zu können

Unfortunately I am out of ideas, but I am sure Steve (Smith) or Enchantech will be able to assist you as I am well beyond my comfort zone on this one.
- Anmelden, um Kommentare verfassen zu können

The space issue is shown for your 628MB Recovery partition at the end of the drive and I do not see how running CHKDSK against that partitions (after allocating a drive letter) would free up extra space unless there were some file system errors affecting free space calculation.
The options here would be to use a partition manager tool to increase the size of the Recovery partition to say 900MB or else ignore this error if it does not affect your backup tasks!
If you want to do the resize then download a copy of the free MiniTool Partition Wizard software which will allow you to do this easily. Note: make a backup before making any such changes if you don't already have one!
- Anmelden, um Kommentare verfassen zu können

Steve, appreciate the input.
ATI won't backup the drive (errors out). Which is why I ran VSS Doctor, as previously advised. Now VSS Doctor has errors (this one) which can't seem to be resolved either.
So you see I can't, in good conscience, run Partition Wizard (prefer the full program) because I have no backup before doing so.
What about running vssadmin to make VSS adjustments for that partition?
TIA
- Anmelden, um Kommentare verfassen zu können

Keith, what are the errors you get when backing up the drive? Post a zipped copy of the Backup Worker log if possible.
There is a new MVP Assistant log viewer tool that has now been made available by Acronis via the Community Tools page..
If you have Disks & Partitions backups created on ATI 2020 or later using .tibx files, then look in the Backup Worker logs.
If you have Files & Folders backups using .tib files (or Disk backups from earlier versions using .tib files) then look in the Demon logs.
Other logs are shown by the MVP Assistant under the 'Active Logs' heading of the Log Viewer page of the Assistant.
The log files should be zipped to preserve their original file names if sharing in the forums and would need to be less than 3MB in size, otherwise you would need to share the zip file via a Cloud share service such as OneDrive, Dropbox etc.
Note: you can boot the PC from the Acronis Rescue Media to create a backup offline from Windows. Alternatively, you could deselect just the Recovery partition from your backup source to confirm that this is causing the errors seen. Click on 'Full partition list' in the Source selection panel to see hidden / system partitions.
- Anmelden, um Kommentare verfassen zu können

Steve, thanks for the help.
The error I've been seeing (see below) I clipped from the ti_demon_???.log fie:
Can't read slices: Error 0x40011: The specified file does not exist.
Question: if I deselect the affected partition, would the resulting backup still allow a restore to be 'bootable' after the restore? Even without this 1 partition?
Whatever happens, I need to be able to restore the C: drive WITH Windows & all installed programs ready to reboot and go to work after restore. Does that make sense?
TIA
- Anmelden, um Kommentare verfassen zu können

Doing a little research I have found that this kind of problem can sometimes be resolved by deleting the USN Journal files on the recovery partition. Here's a link to a PartitionWizard description. Look at Solution 2.
https://www.partitionwizard.com/partitionmagic/backup-not-enough-space.html
I was looking on my system and I cannot assign a drive letter to the recovery partition via Disk Management but was easily able to using MiniTool PartitionWizard Free. I ran a query and it looks like very little space used on mine.
- Anmelden, um Kommentare verfassen zu können

Keith Wheeler wrote:The error I've been seeing (see below) I clipped from the ti_demon_???.log fie:
Can't read slices: Error 0x40011: The specified file does not exist.
Question: if I deselect the affected partition, would the resulting backup still allow a restore to be 'bootable' after the restore? Even without this 1 partition?
Whatever happens, I need to be able to restore the C: drive WITH Windows & all installed programs ready to reboot and go to work after restore. Does that make sense?
Keith, you could have a working recovery without the Windows Recovery partition but you wouldn't have access to the tools provided by that partition without needing to boot from the Windows install or recovery media. The Recovery partition will be recreated when you install a new version / update for Windows, i.e. the forecast 21H1 update due soon, or do an in-place install of your existing build. The Recovery partition falls into the category of being 'nice to have' rather than 'cannot live without!'.
The 'Can't read slices' does look to implicate VSS if is being reported during a backup, as the slices are in essence the snapshots being created via VSS for the backup of live data.
- Anmelden, um Kommentare verfassen zu können

Thank you all for your advice.
BrunoC, I'll check on that. Thanks. Good catch. BTW - I assigned a drive letter inside VSS Doctor. I'll try clearing the USN Journals. Leave it to Microsoft, right?
Steve, is it possible if I run 'vssadmin' to redefine the amount of storage VSS can use on the Recovery partition I could clear this error? I'm looking at this basic syntax:
vssadmin resize shadowstorage /for=E: /on=E: /maxsize=50MB
On my system VSS Doctor assigns E: to the Recovery Partition. I'm wondering if the ShadowStorage on the Recovery Partition is set to 320MB and THAT's what's causing the error. Thoughts?
TIA
- Anmelden, um Kommentare verfassen zu können

vssadmin resize shadowstorage /for=E: /on=E: /maxsize=50MB
On my system VSS Doctor assigns E: to the Recovery Partition. I'm wondering if the ShadowStorage on the Recovery Partition is set to 320MB and THAT's what's causing the error. Thoughts?
I doubt that vssadmin will allow you to run the command you specify as it applies to Windows Server operating systems. You can try it but you will need to set your maxsize to 63MB which is 10% of the partition size of 629MB as 10% is the minimum allocation for shadow storage.
- Anmelden, um Kommentare verfassen zu können

Enchantech, thank you for the informative response.
Pursuant to this Microsoft Tech Note:
https://docs.microsoft.com/en-us/windows-server/administration/windows-…
It says right at the top it applies to Windows 10, so it should work fine per Microsoft themselves. Did not know about the 10% rule though, so thanks for the tip. I'll post back after I attempt with results.
Thx
- Anmelden, um Kommentare verfassen zu können

Keith,
Since the issuance of the linked article 03/05/2020 MS upgrade versions have deprecated some aspects of vssadmin for Windows 10 and below. Resize being one of them. It is apparent that MS believes it know best how to manage this space as changes using vssadmin will appear to be applied but when VSS runs the first time after the change if you look again you will see the change has reverted back to the original setting.
Looking forward to your results however..
- Anmelden, um Kommentare verfassen zu können

Enchantech, the vssadmin commands worked without issue. They have clearly NOT been deprecated!
However, that was not the correct command. THIS (see below) is the correct fix. It's via a Registry entry!
https://docs.microsoft.com/en-us/windows/win32/backup/registry-keys-for…
This fixed my VSS errors in VSS Doctor. Now I only have disk I/O errors. The SSD checks out as 100%, so how can I throttle ATI and avoid the I/O errors?
TIA
- Anmelden, um Kommentare verfassen zu können

Keith, what disk I/O errors are you seeing and in what context, can you post the error message in full?
- Anmelden, um Kommentare verfassen zu können

Keith,
Nice find on the reg mod. Thanks for positing.
- Anmelden, um Kommentare verfassen zu können