Skip to main content

Cloan failure

Thread needs solution

Here is an odd problem that has never happened over the very many years I have been using Acronis to clone the hard drive (HD) with no problems at all. I always check for updates for True Image 2020 before I use Acronis and I always install the Windows updates.

The new computer does not have a traditional HD for the operating system/application programs. C: is a package containing 500 meg of ram like an Optane or NVMe drive that is directly attached to the mother board. A separate traditional HD is connected to the mother board with a traditional cable and is identified as D: All the data files are on D:.

I ran the Acronis clone application to clone C: to a traditional HD connected to the mother board for the first time. After the process completed, I turned on the computer and had it boot to the the cloned HD and it started normally. After I removed the cloned HD, the computer would not boot and the routine Windows fix the problem would not work. I tried to boot it several times with no success. I had to take the computer to a store and have the operating system rebuilt. I have not run the clone again.

Is there a problem related to the clone process on this new type of drive? I am at wwpearce@comcast.net

 

0 Users found this helpful

The new computer does not have a traditional HD for the operating system/application programs. C: is a package containing 500 meg of ram like an Optane or NVMe drive that is directly attached to the mother board.

Warren, what version of Windows OS do you have on this PC as 500 meg of ram for your C: drive is not large enough to install any recent version of Windows?

I would recommend opening a Support Case direct with Acronis given this design scenario.

Warren, I am assuming that C: is an NVMe SSD or Hybrid perhaps.

Anyway, it sounds like what you did was to clone and then boot with both drives in the system at the same time. This is not a good thing... and to quote Steve (who is probably asleep as I'm responding)...

  • DO NOT attempt to boot into Windows with the cloned Source and Target drives both connected.  Cloning duplicates the drive signature which will confuse Windows at best and could potentially cause both drives to be corrupted.

Best to read his Cloning warnings here.

Warren

Please edit your initial post to delete you email address - this will avoid it being harvested by purveyors of junk mail.

I have a dim recollection that using Optane cache drives can cause issues, but not sure that they would explain the issue you are having.

On rereading Steve's response, I suspect that if the size of the Optane drive is correct, it is for caching purposes only and may not need to be backed up. I find it strange that the HDD to which the clone was made is booting. If there is an Optane cache drive there should be a separate drive that contains the OS, which is likely to be a HDD (there would, I suspect be little point in having Optane cache drive if the OS was on and NVMe M.2 dive, and may not make much difference if the OS was on a SATA SSD.

I think one possibility why you cannot boot is that the BIOS/UEFI setting supporting Optane caching somehow has been disabled.

I think we need a lot more information about your system; in particular the model of the motherboard on you system. A listing of all internal drives would also be helpful.

Ian