Skip to main content

Build 6581 - Disk Clone Fails!

Thread needs solution

 

I have just now upgraded ATI 2016 to build 6581.

Build 6581 fails on attempting to clone my SSDD Win 10 system disk when initiated from ATI running under Win 10 64 bit- BUT disk clone worked fine before I upgraded to 6581.

Is this a known issue?  When will it be fixed??  

I have found a way around this but do not have a spare system to test it out on - and I am not prepared to risk my 'production' machine.  See below

 

Here is the problem in some detail:

 

58827: Acronis True Image 2017: Cloning Fails with "A specified authentication package is unknown"

Applies to:

 

Symptoms

  1. In Windows, you start Acronis True Image and select Clone Disk.
  2. Cloning fails with this error:
    Failed to run the task.
    Failed to execute the task script. 0x10002 Error #1364.
    A specified authentication package is unknown 0xFFF0.
    Error 0x00640067+0x0009FFFF

Cause

Issue in the product.

Solution

  1. Help us investigate the issue: send system report from the affected computer via Feedback form within product interface. Acronis developers need to analyze this diagnostic information to find the root cause of the issue and to release a fix for it. This article will be updated as soon as the issue is fixed.

 

 

HERE IS MY WORK AROUND - UNTESTED!!

 

I created a ATI Rescue Disk (on a CD)  from build 6581 then booted my PC from that.  

First up my wireless mouse did not work with this config BUT I found that a USB connected mouse would work.  

Running from the Rescue Disk I was able to clone my SSDD system disk to another SSDD - apparently error free BUT I do not have a spare system to test it on and I'm not prepared to risk my 'production' system.

And YES - I have reported this to Acronis using the Feedback facility in the app.

 

 

0 Users found this helpful

Martyn, thanks for raising this new topic for the clone issue.

When you write about SSDD drives, do you mean SSD - Solid State Drive or SSHD - Solid State Hybrid Drive, i.e. one with a small SSD in conjunction with a HDD to give a hybrid drive?

If it is the latter, then this is not supported for cloning operations, and you should be using Backup & Restore instead.

See KB documents: 56634: Acronis True Image: Cloning Disks  and  1540: Difference between Backup and Disk Clone which give more details on these processes.

Thanks for posting your workaround, using the Rescue Media - this would suggest that you were also trying to perform the clone from within the Windows ATI GUI application - this is also stongly discouraged by the MVP community due to the very large numbers of problems this causes because ATI has to modify the Windows boot configuration to do this and can lead to an unbootable system and possibly corruption of both drives involved.

Martyn, thanks for clarifying the drives are SSD's.  As stated above, all cloning should always be done using the Acronis Rescue Media to boot the system.  One other key point is to never boot with two identical drives connected, i.e. the original and the cloned drive - these will both show the same disk signature and can cause problems.

Hi Steve,

Thanks for your complete and informative reply.  With ATI being a mature  and trusted software tool I am suprised that the Clone function is considered (and found by me) to be unreliable when initiated from the menu option within the ATI Windows Application.

We are not talking about a bit of play time shareware here - its a serious product that folks rely upon and as such should work  PERIOD.   If ANY function within it cannot be trusted to work all the time, every time then it should either be fixed and fully tested before re-release or it should be removed from the product till such time as it is fixed.   With even one dodgy function it makes one question the reliability and safety of the rest of the product.

Right now I expect that it would be a simple matter under the windows application when one selected "CLONE DISK" to display a message that this Disk Clone should ONLY be performed using the Acronis Rescue Media.   Even the Acronis Knowledge base - as you have seen from my earlier post - does NOT include this helpfull information.

I know you are not an employee - but a valuable volunteer and I thank you for that

Its about time for those actually on the payroll to start earning their $$$$$.    They are quick to collect my $$$ when it comes to licences.

Martyn

Hi Martyn, I understand and agree with your comments but unfortunately not all systems are created as equals, and a number of the problems we see for users launching a clone from within Windows has more to do with the unique way the BIOS interacts on those particular systems.  This is especially true for newer systems with EFI (UEFI) boot loaders as there is not a single recognised standard that the Motherboard / BIOS vendors have agreed to stick to, therefore what will work on one system will throw a wobble on another - all of which is compounded by the introduction of Secure Boot which is intended to restrict the type of OS which can work on the system to those 'approved' by Microsoft or compliant to their implimentation of Secure Boot.

The simple test as to whether a clone would work from within the Windows GUI is whether you can boot successfully from the standard, Linux based Rescue Media or not.  If that media doesn't boot / work correctly, then neither will the Windows launch of the clone application, as both use the same code to effect this action.  

From a safety / data integrity perspective, using the Rescue Media is recommended over making changes to the Windows boot loader configuration, and all the MVP's would prefer to see this as being the only method where cloning involves the active OS drive.

Sound advice by Steve.  Bios settings/limitations are the #1 reason that starting a Clone or Recovery from within windows is NOT recommended by MVP's.  Most systems, within the last 3 or so years, are shipping from the factory with UEFI enabled instead of legacy.  With UEFI, comes a whole  new level of bios security features (secure boot, tpm, ability to enable or disable CSM\legacy mode, etc.)  In most cases, security features are enabled by default and this prevents third party bootloaders from launching properly.  In other cases, the bios has been configured to not allow changes necessary to do this at all (example:  my ASUS T200 is strictly UEFI - it will never boot legacy mode so no legacy bootable media will ever work on it - it must be UEFI to work on this system).  In other cases, the systems are being shipped with the SATA mode as RAID (most new systems that have a single NVME PCIE hard drive are also RAID) - the default Linux media, does not have RAID controller drivers for the majority of systems.  Keep in mind the default rescue media is Linux based and starting the process from Windows, attempts to inject the Linux based media and boot from it.  If it's missing drivers or the bios is not configured correctly, you may find yourself, not just able to launch Acronis for cloning, but your OS may end up in a non-bootable state as a result.

For the 30 seconds of time it saves you to start a clone from Windows, vice using a rescue media USB flash drive, when compared to the heartache and pain you may incur if your system does not allow Acronis to load as a third party bootable device, it's just not worth it.  If need be, create your flash drive and leave it plugged in 24/7, but set it as the 2nd boot priority in the bios.  Then, when you need it, reboot and press F12 or whatever your system uses to access the one time boot override menu and select the USB flash drive.  It's almost just as fast and a whole lot safer for your OS bootability.

FYI - using bootable media should be done to match your OS install.  Boot it in UEFI mode if your OS is a UEFI/GPT install or boot it in legacy mode if it's legacy/MBR OS install.  Not sure? Check this out:  https://forum.acronis.com/forum/121829#comment-378318  and https://www.eightforums.com/tutorials/29504-bios-mode-see-if-windows-boot-uefi-legacy-mode.html

Last - I'd recommend you build your rescue media as WinPE. It has better driver support, and drivers can be added if need be for third party hardware like customized RAID controllers or newer hardware that is new to market.  The MVP's have developed a tool to help with the build process and make injecting drivers much easier.  Give it a try.  https://forum.acronis.com/forum/127282.  The WinPE (use the advanced build) is really nice and has a ton of other features that makes using the WinPE much more enjoyable too. 

Hi Steve,

In my case your simple test was not valid.  I was NOT able to get Clone to work from within the Windows GUI but I WAS able to boot my system and then get Clone to work under the standard (not WinPE) Rescue Media.  I cannot explain why.

For completness I will follow this post with one that fully describes my Windows system.

Martyn 

My Windows 10 PC Config:

MB: Gigabyte Z79X-UD3H;  CPU: i5-4690 @ 3.5GHz;  RAM:  8 Gb;  OS: Win 10 Pro 64 bit;  Video: AMD Radeon HD 5700.  Running in UEFI/GPT mode.

Storage:  System (C) 500Gb SSD;  Storage Space (D) 9TB [2 physical drives ea 4TB]; File History (E) 1.5TB;  Backup Drive(s) eSATA connect.

I have taken the advise of Steve and Bobbo and built a fresh WinPE Recovery Disk using their advanced build.

Thanks for all your help.

Martyn

Glad the rescue media is booting in both cases - it should be helpful and will save you time in the long run (and trouble).  There are other factors that may prevent the Windows option from kicking in and booting properly as well, - I suspect that with the rescue media, it shows up as a proper boot option that you can select or the bios recognizes.  I really can't say what the issue is in this case when starting from Windows.  Ultimately, this is exactly what bootable media is for and since it's the safer option, it's really the best one to use. 

Kevin, sorry but too little information to understand exactly what you have spent hours trying to do here?  I would recommend starting a New Topic of your own and providing the details of what you have, what you are doing, how you are trying to do it, what results you are seeing etc?

kevin wrote:

Straight up! Been hours and trying every work around. 0 star review

??? - Ditto to Steve. If you want help from a user forum, need info.  Etiquette goes a long way to if you want free user forum support.  Otherwise, use the technical support that's still active on the product as it's 2 years from release so 2016 has tech support until 2018 release comes out later this fall (assuming similar release dates remain as they have in the past).