[CRITICAL BUG] Acronis seems fails to clone any disks - no comprehensive error message

There is one other situation where ATI cannot clone.  ATI cannot clone Dynamic disks.  The disks must be Basic.  Do you know if either disk is Dynamic?

no all my computers use basic disks. I try to avoid any virtual disk things like the Win 8.1 / Server 2012 R2 introduced virtual storages etc. They work well though compared to the previous dynamic disks.

Karl Heinz wrote:

no all my computers use basic disks. I try to avoid any virtual disk things like the Win 8.1 / Server 2012 R2 introduced virtual storages etc. They work well though compared to the previous dynamic disks.

Then I believe you have a legitimate complaint.

I hope so. I don't expect this got solve by end of 2015 but I need to understand why this happens quite regularly now.

Previously I expressed my wish that Acronis should be or better need to fix NTFS issues prior any action as I have experienced that restores or backups will take hours using Linux Recovery environment if there are issues like MFT Bitmap issues, and even after hours of operation these operations will even fail. source: https://forum.acronis.com/de/node/102309

I think both problems on each own are linked to the same cause.

Karl,

Have you tried cloning to a RAW unformatted disk?  I have performed a couple of clones that way with success on GPT disks.

Yes I have tried that too. Hence mostly choose "add new disk" to initialize it. I think both methods should be successful, what do you think?

I agree yes, both methods should be successful.   lf I can find the time to give clone a try I will do that.  As I have not run a Clone with 6027 I might run into the issue myself.

Thank you very much. This problem is really worrying me and I have no clue why Acronis is so nitpicking here. I really want to solve this problem, but in case that DD12 already said there would be an NTFS problem, which I decline, it would be probably wasted to contact the official Acronis support.

At the moment I don't have the time and free SSDs to build a lab. I would be interesting though to know if the System Report brings any light into this.

Take a look at the disk.txt file in your system report.  It is showing a file system error on the 128GB drive.  You probably need to run chkdsk on the hidden partitions.  If those scans come back clean try sfc /scannow.

Karl,

I finally got home where I could have a look at your system report and although I am not an expert in reading those things I have to agree with Joey.  The error shows to be on Disk 2 Partition 1 which should be a hidden partition in all likelihood.  You can find the error at the end of the system report if you want to have a look.

In this case the hidden partition is the 100 MB EFI / GPT partition on the source drive (128 GB) https://technet.microsoft.com/en-us/library/hh825702.aspx

I wonder why ATIH is able to backup and restore this without issues but failing to clone. Maybe the "full backup" skips to backup the 100 MB EFI partition at all.

You know how much of a work it is to make this partition visible and checkable with diskpart. No normal user would do that to be honest. If the clone mechanism is so nitpicking here I really can just reinforce that ATIH needs to bring an own chkdsk support instead of forcing users to take a deepdive into Windows mechanics.

This is unbearable. This is the second time I run into this trap of an "error".

I think this error might be caused by cloning to a previously prepared (formated) GPT disk.  When I have run a clone in the past I do not first format the disk.  In the case of a new (just unwrapped from the package) drive I just attach it, boot to the recovery media, and run the clone.  In the case of a previously used disk I run diskpart clean all command on the drive and once completed I then boot to recovery media and run the clone.  So far that has always worked.

One thing will automatical happen when cloning fails. After the error message the target disk will contain no visible data anymore, means also the partitions are deleted, so it is basically like a raw disk, isn't it? I tried to clone on this unformatted disk too but as I am using the Linux recovery tool and not WinPE of course I did not use diskpart clean on the target disk.

The logfile notes errors on the source disk, not the initialized target disk. Would you have some time to test both ways after xmas holidays?

Partitoning information would remain on the disk and that may not matter.  I realize that your error is on the source disk, it is not known however when that error/corruption ocurred whether befor the clone attempt, or during the clone attempt. 

I will try to find the time to test and let you know my findings.  I have a gut feeling though the problem is specific to your machine.

"I have a gut feeling though the problem is specific to your machine"

Well somehow I agree but then I tested to clone a sum of 2 pair disks on 2 different computers recently. That's why I raised the issue, because just dissatisfaction about cloning - which is one of the best features of ATIH - doesn't work for me"as expected".

This also covers my recent talk to my bro. He said that he stopped using ATIH, while he was very satisfied with it before 2011 and used it a lot but then he also said that it does not work as expected often enough with ATIH 2012/2013 so he simply don't use it at all - this said without having any specific knowledge about his problems but I couldn't bother him to explain them. Perhaps he was just impatience to care about possible solutions.

Hi everyone, I hope you had a pleasent christmas time. Was anyone able to repro this problem?

Hello,

I'm sorry for the delayed response.

In the provided logs, I see the following errors:

    <event id="5" level="4" module="1" code="502" time="1450632863" message="Dateieintrag beschädigt" line_tag="0x65B5EB7011094700">
        <field name="$module" type="TULong64">
            0
        </field>
        <event id="6" level="4" module="7" code="25" time="1450632863" message="Dateieintrag beschädigt" line_tag="0xEF8B1618A4C0DD9A">
            <field name="$module" type="TULong64">
                0
            </field>
        </event>
    </event>
    <event id="7" level="4" module="100" code="251" time="1450632863" message="Laufwerk klonen fehlgeschlagen." />

The above errors occurred because of errors on the disk 2:

2-   d(?) GPT   119G    1K SATA  1-0-0    OCZ-VERTEX4               
  -1       --CC  119G  119G    0b NTFS   07 NTFS, HPFS   ........... -EE--v Dateieintrag beschдdigt

Cloning operation fails if there are errors on disks. This is expected behaviour.

If the disk has been checked and no errors were detected by chkdsk and no events with code 55 (ntfs error) were registered in the system event log, it makes sense to contact our Support team for further investigation.

The issue has not been reproduced with my SSD disks.

Best regards.

Dear Alexander,

The problem is, that the NTFS issues happened (somehow) on a hidden system partition. Please consult the postings of Mustang about GPT Layout.

There is quite no way for an average user to fix these ntfs issues and in consequence I urgently and repeatingly need to ask Acronis to implement a chkdsk validation for prior every backup / restore operation on all affected source / target partitions as not only this issue happens as described but some task will also take very long time (hours) but may even fail at the end due to NTFS issues, mostly problems in the MFT table.

in the above case you provided the logfile for, the visible NTFS partitions were definetely not troubled. It is too long ago to provide "evidence" from Windows log files.