Acronis 201400 problem on W10 Pro
Just got the new version and installed it on 2 PC's, a W10 Home Ver. 1903, September 10, 2019—KB4515384 (OS Build 18362.356), and a W10 Pro, same version and KB build.
Works FINE on the HOME system.
I failed to run on the Pro system. Got a message that CHKDSK that can be run and looked at the log:
9/25/2019 11:10:34 AM: -----
9/25/2019 11:10:34 AM: ATI Demon started. Version: 24.4.1.21400.
9/25/2019 11:10:34 AM: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
9/25/2019 11:10:34 AM: Operation LARAINE-XPS8500 started manually.
9/25/2019 11:10:35 AM: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
9/25/2019 11:10:35 AM: Operation: Backup
9/25/2019 12:17:41 PM: Error 0x1e50023: File system error is found. Consider checking the disk using Check Disk Utility.
9/25/2019 12:17:42 PM: Error 0x13c0005: Operation has completed with errors.
Start: 9/25/2019 11:10:34 AM
Stop: 9/25/2019 12:17:42 PM
Total Time: 01:07:08
Ran CHKDSK /F on ALL drives... no problems found, restarted...
9/25/2019 12:51:33 PM: -----
9/25/2019 12:51:33 PM: ATI Demon started. Version: 24.4.1.21400.
9/25/2019 12:51:33 PM: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
9/25/2019 12:51:33 PM: Operation LARAINE-XPS8500 started manually.
9/25/2019 12:51:34 PM: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
9/25/2019 12:51:34 PM: Operation: Backup
9/25/2019 12:51:34 PM: Can't read slices: Error 0x40011: The specified file does not exist.
Start: 9/25/2019 12:51:33 PM
Stop: 9/25/2019 12:51:34 PM
Total Time: 00:00:01
All the time, TI itself looked like this capture attached.
Well, it sat there for OVER 1 hour (supposedly only 700GB to be backed up). Then it started, saying over 8hrs (NORMAL use set for Performance), and now it seems it failed?
9/25/2019 12:51:33 PM: -----
9/25/2019 12:51:33 PM: ATI Demon started. Version: 24.4.1.21400.
9/25/2019 12:51:33 PM: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
9/25/2019 12:51:33 PM: Operation LARAINE-XPS8500 started manually.
9/25/2019 12:51:34 PM: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
9/25/2019 12:51:34 PM: Operation: Backup
9/25/2019 12:51:34 PM: Can't read slices: Error 0x40011: The specified file does not exist.
9/25/2019 1:35:44 PM: Error 0x1e50023: File system error is found. Consider checking the disk using Check Disk Utility.
9/25/2019 1:35:44 PM: Error 0x13c0005: Operation has completed with errors.
Start: 9/25/2019 12:51:33 PM
Stop: 9/25/2019 1:35:44 PM
Total Time: 00:44:11
Restarted and the partial log:
9/25/2019 1:41:19 PM: -----
9/25/2019 1:41:19 PM: ATI Demon started. Version: 24.4.1.21400.
9/25/2019 1:41:19 PM: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
9/25/2019 1:41:19 PM: Operation LARAINE-XPS8500 started by schedule.
9/25/2019 1:41:20 PM: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
9/25/2019 1:41:20 PM: Operation: Backup
9/25/2019 1:41:21 PM: Can't read slices: Error 0x40011: The specified file does not exist.
Start: 9/25/2019 1:41:19 PM
Stop: 9/25/2019 1:41:21 PM
Total Time: 00:00:02
Still running, as before, it created a 51.9GB file and doesn't show how long... just like before...
Any ideas?
Allegato | Dimensione |
---|---|
Capture.JPG | 76.02 KB |

- Accedi per poter commentare

Irv, I am doubtful that this file system error issue is being caused by the ATI 2020 #21400 build and only impacts users with Windows 10 Pro systems.
The acid test here would be to revert back to the prior #20770 build initially and see if the error goes away.
File system errors can occur on hidden / system partitions which do not have drive letters and therefore cannot be checked by running CHKDSK. Plus when using CHKDSK for this type of issue, be prepared to use CHKDSK /R if no errors are found by using /F. /R will take more time but will confirm that there are no bad sectors being encountered on the drive.
If you still see no errors, then go to your drive manufacturers support site and download any whole disk diagnostic tools they offer to users.
- Accedi per poter commentare

Steve, well, this is a TOTAL disaster!
First, the 4TB backup drive with CHKDSK /R will take and estimated 14+hrs.!!! The D: which is less that 1TB is almost 2 hours...
So I went to install the 20770 install file. WILL NOT INSTALL IT! Says I have a later version (I did NOT delete it) and all I can do is open the application!
There is another post here with a similar 'slice' problem, but no answer...
It was WORKING FINE before the 201400 update. How can I get this working? Uninstall TI completely and rebuild everything and try again?
I find it hard to believe there is a disk problem anywhere as well. I am backing up PARTITIONS, not full disks, and the /F flag would check those. There is nothing in the log that even hints at the 3 partition involved is bad? Nor what file is missing?
- Accedi per poter commentare

Irv,
You say you are trying to backup individual partitions on a disk. What partitions are they? Do all of them have drive letters?
For the TI app to error out with a file system error carries a different meaning than what a format error does.
I understand that you have run chkdsk on the partition in the equation but if you are using the NTFS filesystem you might have more success using chkntfs. The syntax would be chkntfs /X where X is the drive letter of the partition you wish to run it on..
More info in the link below:
- Accedi per poter commentare

Enchantech wrote:Irv,
You say you are trying to backup individual partitions on a disk. What partitions are they? Do all of them have drive letters?
For the TI app to error out with a file system error carries a different meaning than what a format error does.
I understand that you have run chkdsk on the partition in the equation but if you are using the NTFS filesystem you might have more success using chkntfs. The syntax would be chkntfs /X where X is the drive letter of the partition you wish to run it on..
More info in the link below:
Darn, I forgot about CHKNTFS!!! However that is basically doing CHKDSK /F at boot time. The two system drives, C: and E: (which holds the swapfile and is NOT backed up) were done that way.
Yes, ALL partitions are backup up by drive letter except of C: where the WHOLE drive is as that is a boot SSD and I want the system file areas in case I need to restore that. Other two, D: and E: reside on a 2TB disk that at one time was the only drive and has boot files and the old C: on it WHICH ARE not backed up. Only the D: and E: by drive letter (partition).
I have another backup scenario as the screen capture shows. The ENTIRE C: SSD to the External M: drive. I just ran that and it WORKED!!! That should rule out C: for sure, and even the External M: drive for disk errors.
Since it did, I've decided to DELETE my other scenario backup and recreate it. It has been running for about 10 minutes now and I peeked at the LOG and NO SLICE error? Said it was starting backup.
I just peeked at the log with the Nextgen log app again, no new entries and it is still showing calculating time on the main TI screen. We'll see what happens. I didn't make all settings I wanted though, no e-mail, no priority change, no schedule, but if it works I'll do that.
Possible the old backup scenario had something that wasn't handled correctly?
Well, 27 minutes later the backup actually has started... Time is changing rapidly (just over 700GB's need to be backed up it says), now at 17GB's backed up and 7 hours to go... a few minutes later, 22GB's backed up and 5 1/2 hours to go...
Maybe it is working? Will post when/if done.
- Accedi per poter commentare

All is well now? 704GB's backed up into a 550GB file, a little over 2 hours run time.
New setup scenario, possible something was wrong with the old one, but it works fine now?
- Accedi per poter commentare

Excellent news Irv. Thanks for letting us know!
Ian
- Accedi per poter commentare