Skip to main content

Clone Failure

Thread needs solution

I have Acronis True Image Version 2021, Build 40173 on a Windows 10 desktop with all Acronis and Windows updates.

This problem has happened before. I started the clone process, select Automatic mode,  and I did the usual processes of selecting the source and destination disks. I then indicated that the disk would replace a disk on the source computer.

I selected Proceed and after about 1 second,  the Disk Cloning Process dialog box came up saying “The disk was successfully cloned”. Nothing was copied to the destination disk. This happened several times.

How do I fix this?

I can be reached at    wwpearce@comcast.net        

 

1 Users found this helpful

Warren, as this is a public forum I would recommend removing your email address from your initial post above as it can be harvested by spam bots etc!

Next, build 40173 is not for ATI 2021 - it is for ACPHO which is the successor product and subscription only.  The final build for ATI 2021 was 39287.

I would only be guessing as to why the clone did as you describe so the best place to start would be to look at the log for that operation to see if it offers any explanation.

What type of computer is involved here?  Desktop / Tower or Laptop / Notebook?

What type of disks?  SATA HDD or SSD or card drives such as PCIe NVMe drives?

How were the disks connected, i.e. source internal, destination via USB or Dock ?

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 - New 2.0 with Rescue Media Builder (New Version 2.1.1)

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.

Hi and thanks

The computer is a desktop. The C: disk is a solid state type of drive that is a PCie drive like a RAM package directly connected to the Motherboard. It is not connected with a traditional cable.

I wonder if the issue is that C: is a PCie drive as I have never had this problem.

In the past, I got the Windows problem where it does not see that the backup traditional HD and only the Partition Assistant program can see the drive and assign a letter to it. Then Windows would see the drive with the letter like E:.

Now, Windows and Partition Assistant do not see the HD at all after the clone process had its 3 second completion process. The drive is essentially destroyed.

 

Warren, how exactly are you trying to do the clone operation?

If you are starting this from within Windows using Acronis then it will want a restart to continue and that restart is into a temporary Linux based environment which most likely has no support for the PCIe card drive.

The safest method of working with NVMe M.2 (PCIe) SSD's is to use Backup & Recovery, not Cloning.  It has always been recommended to make a full disk backup of any drive being cloned so after doing so, you could simply remove the current source drive, put it safely on a shelf, then do a recovery (using bootable rescue media) to the new / target drive.  That way the original drive is completely safe from any change etc.

Note: the bootable rescue media should be created using the Acronis 'Simple' option so that it is WinPE based and picks up device drivers from the Windows Recovery Environment for the installed drive.

Hi and thanks for your response.

A goof - I have Acronis Cyber Protect Home Office Premium, build 40173 on a Windows 10, desktop computer.

The Desktop C: drive is a PCIe SSD that is directly attached to the motherboard. The destination drive is a tradition drive connected to the mother board with a cable.

The files on C: are the routine files associated with Windows and all the applications. All my data files are on D: that is a separate, traditional drive.

I have been cloning the C: drive for many years with a traditional drive using the Acronis Clone process and never had a problem when I had the traditional drives. I have always done clone once a month. This problem started when I got a new computer that has C: on a PCIe SSD drive.

I ran the Rescue Media Builder and generated a DVD. When the C: drive has a complete failure and is replaced, will this DVD restore all of the old C: to the new drive?

 

Warren, this is a case when cloning is not the best option to use when you are working with a PCIe (NVMe) SSD card drive.

I would recommend making a scheduled backup of the SSD to another drive such as an external USB storage drive, then if the worse happens you can restore the most recent backup to a new / replacement SSD using Acronis rescue media.

See forum topic: Steve migrate NVMe SSD where I have documented (with images) the process that I have used multiple times for my own laptops using Backup & Recovery. 

KB 59877: Acronis True Image: how to distinguish between UEFI and Legacy BIOS boot modes of Acronis Bootable Media

KB 69472: Acronis Cyber Protect Home Office: how to create bootable media

KB 69477: Acronis Cyber Protect Home Office: how to back up files or disks

KB 69474: Acronis Cyber Protect Home Office: how to back up entire computer

KB 69427: Acronis Cyber Protect Home Office: How to restore your computer with WinPE-based or WinRE-based media

Steve Smith wrote:

Warren, this is a case when cloning is not the best option to use when you are working with a PCIe (NVMe) SSD card drive.

<<<snip>>

 

I agree with Steve. I have upgraded OS M.2 NVMe SSDs on several  PCs, and have found the method suggested by Steve the best (even when the PC supports 2 or more M.2 drives.

Ian