Can't read slices: Error 0x40011

welcome to these public User Forums.

The error message 'can't read slices' normally refers to the destination backup storage drive rather than the source drive(s) for the backup task.

Acronis uses the term 'slices' for the parts of the backup task that have been created, this can be the initial Full backup archive, or the incremental backup 'slice' that gets added to the same archive via consolidation.

With ATI 2020, there is a new log viewer called MVP Assistant which is needed to view the new Backup Worker log created by Disk backups and which hold lots more detailed information.

Download a copy of the MVP Assistant log viewer tool and use this to look at the logs to see if they show any issues during the operation process?

The latest version of the new log viewer tool is at the link below. 
MVP Assistant update for Acronis Cyber Protect Home Office (Version 1.1.6.0)

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) or using Cloning 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 Schedule2 log contains information related to scheduled task but is one of the more difficult logs to read / work through.

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.

Steve,

Firstly, thank you for your assistance so far.

I have installed MVPAssistant V1.1.6.0.

The job that I am having problems with creates .tibx files.

I have viewed the files under the Structure Active Logs/Backup Worker/

I am uploading files as a zip file.

Thanks for the backup worker logs.

Working backwards through the logs (starting from the latest) - the first two logs are incomplete, i.e. only show the task starting then the log ends.

The third log shows a Microsoft VSS snapshot issue!

20/06/2022 01:45:21:051 PM +01:00 10356 I00000000:
type=commonerror; value=?5cA??@?A backup error.
$funcAda_backup::Commit
$lineNa??(????Read error.
$funcA`anonymous-namespace'::PartitionBackuper::ReadDrive
$lineNe????v???Failed to read the snapshot. See VSS logs for details.
$funcAwin_snapshot_volume::IoOp
$lineNU?R?*{??CRC error.
20/06/2022 01:45:21:051 PM +01:00 10356 I00000000: type=log; level=inf; message=lsm#1: dedup_map nr_lookup=2284347 nr_found=1146435 false+=1141900 (49.99%/99.60%);
20/06/2022 01:45:21:051 PM +01:00 10356 I00000000: type=retcode; value=4095; id=1;

The same VSS snapshot error is reported at 20/06/2022 01:02:35:788 PM in the 4th log and at 20/06/2022 12:20:17:270 PM in the 5th log.

The first recommendation is to download & run the Acronis VSS Doctor tool and let it fix any issues that it identifies and offers to fix.

Note: the VSS snapshot will normally try to use unused free space on the source drive for the backup task so it is possible that there are errors on that drive that CHKDSK /F hasn't found but which may be found using CHKDSK /R.

Steve,

Thank for the above.

I have downloaded VSS Doctor and run it (and have uploaded the report).

My PC had rebooted itself whilst it was doing the back and hence the incomplete logs.

I am backing up the D drive to the I drive where I get the errors.

VSS Doctor does not give me an option to fix any errors.

What's next?

When I ran Chkdsk, I ran it with /f /r commands

The key information from the VSS Doctor tool report is that below:

Event Log

Status: Warn
Description: Some VSS-related errors or warnings occurred during the previous day

Events:

Timestamp: 22/06/2022 10:37:41
Type: Warning
Source: Ntfs
Message: {Delayed Write Failed} Windows was unable to save all the data for the file I:\$Mft. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.
InstanceId: -2147221454
SearchLink: https://www.google.com/#newwindow=1&q=Ntfs+event+id+2147745842

Timestamp: 22/06/2022 10:37:38
Type: Warning
Source: disk
Message: An error was detected on device \Device\Harddisk6\DR8 during a paging operation.
InstanceId: -2147221453
SearchLink: https://www.google.com/#newwindow=1&q=disk+event+id+2147745843

Timestamp: 22/06/2022 10:37:38
Type: Warning
Source: disk
Message: An error was detected on device \Device\Harddisk6\DR8 during a paging operation.
InstanceId: -2147221453
SearchLink: https://www.google.com/#newwindow=1&q=disk+event+id+2147745843

The above is saying that you look to have a hardware problem with Harddisk6 which is your I: storage drive.  The tool cannot fix this type of error.

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: Western Digital Dashboard

 - Seagate disks: SeaTools for Windows

 - HGST disks: HGST Windows Drive Fitness Test (WinDFT)

 - Intel SSDs: Intel Memory and Storage Tool (GUI)

 - 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

 - Crucial disks: Crucial Storage Executive

 - SanDisk disks: SanDisk SSD Dashboard tool / SanDisk SSD Dashboard user guide

Steve,

Thanks for the above.

I will download the appropriate tool, run it and report back (probably is a couple of days).

Once again, thanks for your help so far.

Steve,

I have taken the following actions:-

1. Run the Seagate drive tools against the I drive (this is where the backups are held/will be created);
2. Run CHKDSK /r on the I drive;
3. Formatted the I drive;
4. Run 3 jobs to back up to the I drive 2 jobs for entire drives and 1 to back a folder);
5. Ran 1 job to back up the entire D drive to another external drive;
6. Run CHKDSK /r on the D drive;

Results of the above:-

1. No problems reported by the drive tool;
2. No problems reported or had to be fixed by CHKDSK;
3. N/A
4. Backing up my C drive to I drive was successful, backing up folder “C:\Program Files (x86)\0A Pank Installed Programs” was successful, backing up the D drive to the I drive failed, cancel the job.
5. Backing up the entire D Drive to the J drive failed. Cancelled the job.
6. No problems reported or had to be fixed by the CHKDSK;

Observations on the backup

1. The entire D drive backups failed to both external drives (I and J). However the backup .tibx files were created and the failure message occurred after that and the jobs gave a message to say they would restart in a few minutes.

On all the D drive failures using Log Viewer 2.210 reports :-

25/06/2022 11:15:25 :734   +01:00 16856 E00000000: Can't read slices: Error 0x40011: The specified file does not exist.
| line: 0xaa33a143c434a5fc
| file: c:\jenkins_agent\workspace\ati-main-win\1824\home\backup_worker\impl\backup_worker.cpp:174
| function: `anonymous-namespace'::ReturnCodeToError
| line: 0xaa33a143c434a5fc; c:\jenkins_agent\workspace\ati-main-win\1824\home\backup_worker\impl\backup_worker.cpp:174; `anonymous-namespace'::ReturnCodeToError
| $module: ti_demon_vs_38600
|
| error 0x40011: The specified file does not exist.
| line: 0xc8d8731ce106f9c3
| file: c:\jenkins_agent\workspace\ati-main-win\1824\archive\ver3\adapter\error.cpp:53
| function: `anonymous-namespace'::ConvertArchive3Error
| line: 0xc8d8731ce106f9c3; c:\jenkins_agent\workspace\ati-main-win\1824\archive\ver3\adapter\error.cpp:53; `anonymous-namespace'::ConvertArchive3Error
| $module: archive3_adapter_vs_38600
25/06/2022 11:27:11 :622   +01:00 16856 E0004000F: Error 0x4000f: Canceled.
| trace level: error
| line: 0xaa33a143c434a5fc
| file: c:\jenkins_agent\workspace\ati-main-win\1824\home\backup_worker\impl\backup_worker.cpp:174
| function: `anonymous-namespace'::ReturnCodeToError
| line: 0xaa33a143c434a5fc; c:\jenkins_agent\workspace\ati-main-win\1824\home\backup_worker\impl\backup_worker.cpp:174; `anonymous-namespace'::ReturnCodeToError
| $module: ti_demon_vs_38600

Please note the D Drive contains .tib files and they have been included to be backed up.

I have uploaded files from MVPAssistant V1.1.6.0 and Log Viewer 2.210

Any ideas where to go from here?

Sorry but I am seeing just the same errors as advised before suggesting an issue when trying to commit the backup to disk, either as a disk file system error, CRC error or VSS snapshot error plus some of the logs were for cancelled tasks.

Are you using any overclocking on this PC as that can cause some strange issues?

Can you try backing up the drives to a different storage drive to try help isolate whether the errors are arising from the source drive or the target drive?

Steve,

The PC has had no modification done for overclocking.

Have tried to back up the D drive to a new drive J, and I get the same result. See 605615-336295.log and 605615-336296.txt above.

I note in log 605615-336298.txt a message that reads Consider checking the disk using Check Disk Utility.

Just before this line it also says “file: c:\jenkins_agent\workspace\ati-main-win\1824\home\backup_worker\impl\backup_worker.cpp:174, is it saying that the C drive needs to be checked for errors?

Additionally, prior to backing up the D drive to the I drive, I backed up the entire C drive and a Folders to the I drive and the jobs completed without any errors.

Would it be worth re-installing the program?)

The log is suggesting checking the source drive, i.e. D: using CHKDSK.

I cannot see how reinstalling the program will fix this type of error.

If you want to get another view on where the error is coming from, then download a copy of the free Macrium Reflect 8 program and try using that to backup the same drives and see if that also reports drive or file system errors?

Steve,

I ran CHKDSK /r against the D drive and that reported no problems.

I will download Macrium 8 as you suggest and report back.

Steve,

Installed Macrium Reflect 8, build 6758.

Backed up D drive to I drive, and it completed.

Ran the Analyse file system in the program for the D drive and it produced the following:-

Ran the Analyse file system in the program for the I drive and it produced the following:-

Where to now?

Using the MVP Assistant tool, use the option to create an Acronis Disk Report to see if that is showing a reason why Acronis is reporting issues with your drive?

Note: there is a new version of the MVP Assistant tool as per the link in my signature.

Steve,

Thanks for all the help so far.

I have uploaded a CHKDSK report for the D drive (which is the one that requires backing up)  (for your perusal).

Chkdsk was run after  I had run Macrium Reflect 8 which created a backup.

I have installed the new MVP Assistant tool as you have suggested, however when I select Acronis Configuration, selecting Acronis Utitilies from the Top Menu, the Create Disk Report option is greyed out and I can not select it, only the Create System Report is available. Any idea why?

Can you elaborate which drive you require a disk report for.

I am currently running a CHKDSK on the I drive (which is the one that should hold the backup of the D drive) and as it is a large drive it will take time to complete. I will upload its results when it is complete.

If the disk report option is greyed out then please open the Settings page for the MVP tool and download it as per the image below.

The disk report will look at all installed drives.

Steve,

Thanks for that.

Should I wait for the Chkdsk utility that is currently running to complete before I run your Create Disk Report?

Chkdsk, tells me that the last step will take 5.5 hours to complete.

The disk report should run fine even if CHKDSK is running as it is not performing the same type of check.

Steve,

Please find the report.

Thanks for the disk report, this shows that Acronis is finding a problem with your C: and D: drives as indicated by the E in the right column C for those drives (Disks 1 & 2 Partition 1). In both cases, the issue being reported is strictly related to not being able to create a Volume snapshot on those drives.

                     Speed IFace Hs-Bs-Tg Model                     
Num  NT    L9NO  Size FSsize Free FS     Type            Label       ABCHSV
---- ----- ---- ----- ----- ----- ------ --------------- ----------- ------
1-   d(?)       932G   13M       0-0-0    SAMSUNG HD103SJ 1AJ10001  
  -1  p(1) --CD  932G  932G  581G NTFS   07 NTFS, HPFS   Photos..... A-E--V
2-   d(?)       466G   11M       0-0-0    Hitachi HDS721050CLA362 JP2OA39C
  -1  p(1) --DE  466G  466G  215G NTFS   07 NTFS, HPFS   Music...... A-E--V
3-   d(?)       466G   11M       0-0-0    Hitachi HDS721050CLA362 JP2OA3EA
  -1  p(1) --EF  266G  266G  266G NTFS   07 NTFS, HPFS   XP......... A-C--V
  -2                              table  0F Extended LBA             ------
  -5  p(2) --FG  200G  200G  200G NTFS   07 NTFS, HPFS   iPod Cat... --C--V
4-   d(0)       954G  445M       0-0-0    INTEL SSDPEKNW010T8 002C  
  -1  p(1) ----  954G  954G       NONE   EE EFI header               --C--v
5-   d(?)         2T  6.9M USB   0-0-0    Seagate Expansion 0707    
                   2T             free                               ------
  -1  p(1) ----    2T    2T       NONE   EE EFI header               --C--v


Disk 1  Partition 1
  FS:                NTFS
  File system error: 33 (Unable to create volume snapshot)
  FSSize:            1953523113 (932G)
  BlockSize:         8 (4K)
  BlockCount:        244190389 (932G)
  FreeBlockCount:    152335592 (581G)
  ReservedSectors:   16 (8K)
  FATSize:           0 (0b)
  FATCount:          0 (0b)
  RootEntries:       0 (0b)
  UsedRootEntries:   0 (0b)
  InodeSize:         1024 (1K)
  InodeCount:        126720 (124M)
  BytesPerInode:     0 (0b)
  VolumeLabel:       Photos..........................

Disk 2  Partition 1
  FS:                NTFS
  File system error: 33 (Unable to create volume snapshot)
  FSSize:            976766969 (466G)
  BlockSize:         8 (4K)
  BlockCount:        122095871 (466G)
  FreeBlockCount:    56249725 (215G)
  ReservedSectors:   16 (8K)
  FATSize:           0 (0b)
  FATCount:          0 (0b)
  RootEntries:       0 (0b)
  UsedRootEntries:   0 (0b)
  InodeSize:         1024 (1K)
  InodeCount:        348928 (341M)
  BytesPerInode:     0 (0b)
  VolumeLabel:       Music...........................

I would suggest trying a Files & Folders backup task for backing up the contents of these drives (for your Photos and Music content) instead of doing a Disks & Partitions backup, as using F&F uses a different VSS snapshot method.

Steve,

I would like to firstly thank you for all the assistance you have offered so far to my query, it is appreciated.

For the sake of completeness, I have uploaded a Chkdsk report for the I drive (where the backup go), again it shows no problems with the drive.

You mentioned that the Disk Report shows a problem with the C and D drives.

I have therefore done an entire disk back up of the C drive, and no problems were encountered. I have uploaded its backup_worker log (backup_worker_2022-06-28-21-29-07.0).

I also did an entire disk back up of the D drive and it failed. It get towards the end (it actually writes out the back up file to the I drive), encounters an error and seems to start again, hence I cancelled the job. See log backup_worker_2022-06-28-22-06-30.0.

This morning I have gone with your suggestion to back up folders and files from the D drive to the I drive. This was successful (see log backup_worker_2022-06-29-11-08-54.0).

I have a couple of questions:-

1. Why did Macrium Reflect 8 manage to back up the D drive without any issues where as Acronis shows problems with the D drive?
2. Why can I back up the entire C drive even though Acronis is showing there are problems with the disk?

For the future, I am wondering whether to use Acronis or another product.

I welcome your thoughts.

Sorry, I misread the drive letters from the disk report - it is the D: & E: drives (Photos & Music) that are giving the Volume Snapshot issue for Acronis.

Some key differences between making a Disks & Partitions backup and a Files & Folders one is that the latter uses a different VSS snapshot method, plus also creates .TIB files (not .TIBX) and also uses the TI_Demon logs (not Backup Worker).

It is entirely possible that Macrium also uses a different VSS snapshot method!

If your D: & E: drives are purely used for data storage, then using Files & Folders to backup that data is the recommended option.

Steve,

After reading your last message, I decided to run a Chkdsk on my music drive (E), I attach a log of this, which shows there are no problems with the drive.

I then ran Acronis to back up the entire Music disk and that completed successfully (logs attached).

I have a couple of question for you:-

1. If I copy all the data off the Photo Drive (D) which Acronis is saying is corrupt to another drive and then format the Photo drive will it get rid of the corruption?

2. On your advice, I have change the Photo drive back up to back up all files and folders. If in the future the number of files and folders increase, will they automatically get backed up or would I have to use the options to back everything on a regular basis?

I have a couple of question for you:-

1. If I copy all the data off the Photo Drive (D) which Acronis is saying is corrupt to another drive and then format the Photo drive will it get rid of the corruption?

2. On your advice, I have change the Photo drive back up to back up all files and folders. If in the future the number of files and folders increase, will they automatically get backed up or would I have to use the options to back everything on a regular basis?

1.  The answer really depends on what the corruption is.  Volume snapshot data is stored in unused sectors on the drive so it is definitely worth trying this action.

2.  If you know that you have added new root folders to the Photo drive, then double check either before the backup runs or after it runs.  If checking before, look at the Source selection to ensure the new root folder in selected.  If checking after, look at the Recovery panel to see if the new root folder is shown included in the backup?

For changes to sub-folders and their content, these should be included automatically assuming that the root folder is already selected in the Source.

Steve,

Thank you for answering the questions.

I think I will try and copy all the data for D drive to else where, format D drive, copy data back and finally run an entire disk back up of the D drive to see what happens.

I will report back when the above has completed.

Steve,

I have done the following:-

1. Copied all the data from the Photo Drive (D) to elsewhere on the PC;
2. Long format the Photo drive;
3. Ran Chkdsk /r on the newly formatted drive (no errors reported);
4. Copied the data back to the Photo drive;
5. Did a whole disk backup of the Photo Drive and that worked. No errors reported as previously.

I note that when you set up a job to backup, under the Advanced tab under Performance, there is an option towards the bottom called Snapshot for backup.

The option is set to VSS. The other options available are No Snapshot, Acronis Snapshot and VSS without writers.

In one of your messages above you mentioned that I was encountering Volume Snapshot issues. To prevent this issue occurring, what should I set the Snapshot for backup to?

Lastly, thank you very much for the assistance you have offered in resolving this problem.

It is strongly recommended to keep with the default snapshot provider which is VSS other than perhaps for testing purposes.

Good to hear that your last actions look to have been successful but still worth considering about using Files & Folders for this task.

Steve,

Thank you for the answers to my questions.

I am happy for you to close this problem.

Once again, I thank you for your time and effort.