Skip to main content

Selective backups succeed - entire desktop backup fails

Thread solved

I have the following issue with Acronis True Image 2020:

My desktop computer is cosisting of two drives:
C:\  (Samsung SSD 830Series D-Kit, MLC, 128GB)
D:\  (Seagate Momentus XT, 7200rpm, 32MB)
When I make individual backups of these drives (and also of individual files),
Acronis True Image 2020 works perfectly.

However, when I intend to backup the ENTIRE content of my computer
(called 'Coolermaster'), i.e. both drives C:\ and D:\, it fails.

Acronis starts the backup procedure, runs it for a long time and then fails it
with the error message "failed because of error".

The event codes are as follows:
0x006400CF+0x006400DE+0x00AC0041+0x00AC0040
+0x01AF0006+0x01AF0005+0x00040011+0x0000FFF0
+0x80070002

There is suffient space on the external hard disk to which
the backup should go (WD My Passport Ultra 4 TB).

You will find enclosed a couple of snapshots and a
system-report.zip.

I am not so talented to understand most of the knowledge base.
Does anyone know a possible reason why I am able to backup
the drives C:\ and D:\, but noch the ENTIRE desktop computer ?

(Simplyfied, drive C:\ containing program files and drive D:\
containing datas).

Thank you for your assistance.

 

 

 

0 Users found this helpful

Steven, welcome to these public User Forums.

First, there are no attachments for your topic above and it is very unlikely that you would be able to upload an Acronis System Report zip file due to the max 3MB file size limit.

Yours is the first report I have seen of this type of issue, i.e. that backups of the two drives is successful when done individually but not when combined together.  That suggests to me that the two drives use different sector sizes, i.e. one may be only 512 bytes per sector and the other uses 4KB per sector and that this may be at the heart of the issue.

One final comment, I do not use the 'Entire PC' option for any of my own systems - my preference is always to backup each drive individually.  This keeps the backup image size much smaller and also makes it simpler to work with should an individual drive need recovering or if one should fail.  I have never had multiple drives fail in any system.  The other benefit of keeping these backups separate is to allow different schedules for when backups are run.

I would like to add my support for @Steve Smith comments about using (or rather not using) "Entire PC" backups.

Ian

These are the files that were missing. yes, system-report.zip is too big for uploading.

Thank you for your comments on my issue. I agree, it is very unlikely that I will get
into the situation to backup the entirety of my desktop computer.

However, up to mid-2021 the full-computer-backup worked perfectly. As I am a
curious man, I wondered why this is suddenly not possible anymore and leads
to an error message. As the two drives are still the same ones, it is unlikely that
the different sector sizes is relevant, if it would be the case.

I hoped that someone could 'read' the zip-file to find out where's the rub.

 

Attachment Size
604402-332265.pdf 50.32 KB
604402-332268.pdf 74.39 KB
604402-332271.JPG 79.27 KB
604402-332274.JPG 95.15 KB
604402-332277.JPG 90.58 KB
604402-332280.JPG 96.48 KB

Steven, if you want to share the Acronis System Report zip file via a cloud service such as OneDrive, Google Drive etc then I will take a look at the logs for you.  Send me a private message with the link to the shared file.

Steven, thank you for the private message with the link to the System Report zip file.

The backup logs for your 'Entire PC' backup task shows evidence suggesting that there is a disk error at work here giving rise to reports of a CRC error and associated with this, problems with reading snapshot data captured by Microsoft VSS for the task when it came time to commit that data and write it out to the destination disk drive.

01/06/2022 10:16:57:363 AM +02:00 6052 I00000000: type=commonerror; value=?5cA??@?Backup-Fehler.$moduleAdisk_backup_vs_650$fileAc:\jenkins_agent\workspace\mod-disk-backup\650\product\core\da_api\backup.cpp$funcAda_backup::Commit$lineNa??(????Lesefehler.$moduleAdisk_backup_vs_650$fileAc:\jenkins_agent\workspace\mod-disk-backup\650\product\core\resizer\archive3\backup_partition.cpp$funcA`anonymous-namespace'::PartitionBackuper::ReadDrive$lineNe????v???Failed to read the snapshot. Zu Details siehe VSS-Protokolle (Logs).$moduleAdisk_backup_vs_650$fileAc:\jenkins_agent\workspace\mod-disk-backup\650\product\core\fdisk\win_snapshot.cpp$funcAwin_snapshot_volume::IoOp$lineNU?R?*{??CRC error.$moduleAdisk_backup_vs_650$fileAc:\jenkins_agent\workspace\mod-disk-backup\650\product\core\fdisk\ver2\arch\windows\win_errors.cpp$funcAFdisk::AddKstatusError$lineN+=; id=1;

01/06/2022 10: 16: 57: 363 on i00000000: Type = Commonerror; Value =? 5ca ??@? Backup error. ?? (??? Reading error. PartitionBackuper :: ReadDrive $ linene ?? V ?? Failed to Read the Snapshot. See VSS protocol (logs). \ Product \ Core \ Fdisk \ Win_Snapshot.cpp $ Funcawin_snapshot_volume :: ioop $ linen u? R?*{? CRC error. \ Product \ Core \ fdisk \ Ver2 \ Windows \ Win_errors.cpp $ Funcafdisk :: Addkstatuseror $ linen+=; id = 1; 

Within the system report is a disk report text file (disks.txt) which also shows a warning against your second disk drive (D:).

DA-API report version 3

          PS         Speed IFace Hs-Bs-Tg Model                     
Num  NT    L9NO  Size FSsize Free FS     Type            Label       ABCHSV Error
---- ----- ---- ----- ----- ----- ------ --------------- ----------- ------ ----------
1-   d(0) MBR   119G SATA  0-0-0    SAMSUNG SSD 830 Series CXM03B1Q
                                  MBR                                -----v
  -1  p(1) --C-  100M  100M   67M NTFS   07 NTFS, HPFS   System-rese A-c--V
  -2  p(2) --DC  119G  119G   42G NTFS   07 NTFS, HPFS   Lokale Fest --c--V
  -3  p(3) ----  568M  568M   68M NTFS   27 Windows RE H ........... --c--V
                 2.3M             unallc                             ------
2-   d(1) MBR   699G SATA  0-0-0    ST750LX003-1AC154 SM12    
                                  MBR                                -----v
  -1  p(1) --ED  699G  699G  160G NTFS   07 NTFS, HPFS   Lokale Fest --w--V  <<<<
                 1.9M             unallc                             ------
3-   d(?) GPT   3.6T USB   0-0-0    WD My Passport 260D 2003  
                                  MBR                                ------
                                  GPTpri                             -----v
  -1       --FO  3.6T  3.6T  901G NTFS   07 NTFS, HPFS   WD My Passp --c--V
                                  GPTbck                             ------

Partition 2-1: file system
  FS:                NTFS
  File system warnings:    Lost blocks (clusters)
  FSSize:            1465143289 (699G)
  BlockSize:         8 (4K)
  BlockCount:        183142911 (699G)
  FreeBlockCount:    42052093 (160G)
  ReservedSectors:   16 (8K)
  FATSize:           0 (0b)
  FATCount:          0 (0b)
  RootEntries:       0 (0b)
  UsedRootEntries:   0 (0b)
  InodeSize:         1024 (1K)
  InodeCount:        149248 (146M)
  BytesPerInode:     0 (0b)
  VolumeLabel:       Lokale Festplatte...............
  SerialNumber:      5E 66 D4 64 9C D4 64 30 00 00 00 00 00 00 00 00
  CheckPerformed:    1
  UsefulInformation: 1151354411159 (1T)
  BadBlockCount:     2 (8K)
  FreeInodeCount:    17430 (17M)
  FilesCount:        119270
  DirectoriesCount:  10632
  HardLinkCount:     0
  SymLinkCount:      0
  BlockDeviceCount:  0
  CharDeviceCount:   0
  SocketCount:       0
  FifoCount:         0
  JournalSize:       16384 (64M)
  Options:         

See KB 1638: Acronis Disk Report for an explanation of the above information.

  1. The C column stands for Full partition check status:
    • C - no errors
    • E - error
    • W - warning

    If there is an E or a W, then it is recommended to check the partition for errors and repair:

    • Go to the Command Prompt (Start -> Run -> cmd);
    • Enter the command:

    chkdsk DISK: /r

    where DISK is the partition letter you need to check. Please note, that checking the C: drive may require you to reboot the machine.

After the partition is repaired, you may want to check if your Acronis product functions properly now.

Hello Steve, thank you so much for your detailed analysis; it is very valuable for me. You are probably not asthonished that I do not understand every line of your answer.

But evidence is shown that there are errors on both of my drives, which do not show up on individual backups, but on full desktop backup. They also does not show up on daily use of my computer.

As there is, to my opinion, no urgent need, I will try to settle it on a free weekend.

One question with regard to chkdsk:
As per my experience, using 'chkdsk' for checking, it takes hours, or even days, to scan a disk with eg. 700 GB. Am I misremembering ?

I hope I do not bother you too much, but curious men are like they are  :-)

Steven

Steven, I would suggest just running CHKDSK D: /R as an initial action - the time needed for this to complete can vary due to both size and number of issues encountered.  Hopefully, you should be able to run this from within Windows as it is not your main OS drive, which should allow you to still use the computer for other activities that don't need data from the D: drive.

Note: you can use a utility application such as Glary Utilities to perform some of these type of disk scans where it will tell you if any needs to be done after rebooting due to locks etc.

@ Steve Smith

Thank you for your recommendations. The coming night, I'll give chkdsk a chance to show me what's wrong on my drive D:

Otherwise I'll go on with Glary Utilities.

I'll keep you informed, it might take a couple of days.

thanks, Steven

image 654

@ Steve Smith

All afternoon I tried to send you a personal message with comments on my procedure and the link to a new zip-file.

But how ever I formulate the message, avoiding special characters, the above mentioned warning plops up.

Where can I find a list of these 'forbidden characters'?. I am slowly getting nervous about not being allowed to send you a personal message.

Steven, sorry but have no idea why you should be seeing the pop-up message about forbidden characters?  Your previous private message came through fine so can only assume that there is some form of forum glitch at work here!

If you are able to reuse the same link as the previous zip file or just post the latter part of a new link using the same service (after the .com/...) I can try using that for the new zip file.

Steven, unfortunately I have no good news for you.

How did I proceed ?

 

- chkdsk D: /r   >>>   2 ½ hours, about 700 GB   >>>   100% repaired

- Acronis: trying to backup full desktop computer   >>>   failure

- chkdsk C: /r   <<<   ½ hour, about 120 GB   >>>   100% repaired

- Acronis trying to backup full desktop computer   >>>   failure

- Creating "SystemReport after chkdsk D and C 100% repaired.zip"

 

I cannot send you the chkdsk-log-files, because I have no access to the

System Volume Information, and I am a little bit hesitating to run the

procedure to take ownership of this folder. ("Never touch a running system!")

If it would be helpful for you, however, to have a look at the chkdsk-log-files for possible further recommendations, I try to overcome this resistance.

 

This is the link to the new version of the zip-file:

[will follow as personal message]

 

Your assistance is very much appreciated.

 

Steven

Steven, thank you for the link to the new system report zip file.

The new disks.txt report shows that the issue with the D: drive is fixed.

DA-API report version 3

          PS         Speed IFace Hs-Bs-Tg Model                     
Num  NT    L9NO  Size FSsize Free FS     Type            Label       ABCHSV Error
---- ----- ---- ----- ----- ----- ------ --------------- ----------- ------ ----------
1-   d(0) MBR   119G SATA  0-0-0    SAMSUNG SSD 830 Series CXM03B1Q
                                  MBR                                -----v
  -1  p(1) --C-  100M  100M   67M NTFS   07 NTFS, HPFS   System-rese A-c--V
  -2  p(2) --DC  119G  119G   42G NTFS   07 NTFS, HPFS   Lokale Fest --c--V
  -3  p(3) ----  568M  568M   68M NTFS   27 Windows RE H ........... --c--V
                 2.3M             unallc                             ------
2-   d(1) MBR   699G SATA  0-0-0    ST750LX003-1AC154 SM12    
                                  MBR                                -----v
  -1  p(1) --ED  699G  699G  181G NTFS   07 NTFS, HPFS   Lokale Fest --c--V
                 1.9M             unallc                             ------
3-   d(?) GPT   3.6T USB   0-0-0    WD My Passport 260D 2003  
                                  MBR                                ------
                                  GPTpri                             -----v
  -1       --FO  3.6T  3.6T  923G NTFS   07 NTFS, HPFS   WD My Passp --c--V
                                  GPTbck                             ------

At this point, I would suggest doing a full system restart to see if that clears the issue with doing the 'Entire PC' backup operation as there is a different error now being thrown which would also suggest either deleting the existing backup files or starting a new backup task.

07/06/2022 10:52:55:133 PM E00000000: Can't read slices: Error 0x40011: Die spezifizierte Datei existiert nicht.
07/06/2022 11:06:31:227 PM E01E50023: Error 0x1e50023: Fehler im Dateisystem gefunden. Sie sollten das Laufwerk auf Fehler überprüfen.
07/06/2022 11:07:01:420 PM E013C0005: Error 0x13c0005: Aktion mit Fehlern beendet.

07/06/2022 10: 55: 133 PM E00000000: Can't Read Slices: Error 0x40011: The specified file does not exist.
07/06/2022 11: 06: 31: 227 PM E01E50023: Error 0x1e50023: Error found in the file system. You should check the drive for errors.
07/06/2022 11: 07: 420 PM E013C0005: Error 0x13c0005: Action with errors. 

The new error about not being able to read slices is looking at your backup storage drive rather than the drives included in the source for the task.  It is possible that the file system error on the D: drive has caused the backup image files to be corrupted on the storage drive.

Steve,

Finally good news !

I have proceeded as per your recommendation and have deleted all the old backup versions that failed and created a new one which I called "COOLERMASTER NEW". It took me something like 2 hours plus the time for validation. And it succeeded !

I had a look in the inside of the backup and the newest files - as far as I remembered - were present.

I award you 10 points, this is the maximum of my range :-), and I hope you will be able to help many other users out of a bad situation.

Thank you and greetings,
Steven

Attachment Size
604699-333041.png 34.41 KB