Skip to main content

Disk cloning fails with no message

Thread needs solution

I attempted to clone the contents of my old drive onto my new SSD. After clicking the restart button, my computer rebooted and showed me a window saying that it was cloning the disk, with a checkbox to shut down once complete.

I unchecked the box, but after a few minutes my computer automatically rebooted again, this time booting up normally. I checked my new SSD, and Acronis has done nothing to it.

I tried again, but it did the same thing.

 

I've attached a system report.

 

Also, I am using Acronis True Image 2015 but when I went to the contact support page and was prompted to select my product, the only version in the list was OEM 2014. Because of this I can't contact support through chat.

Attachment Size
acronissystemreport.zip 447.87 KB
0 Users found this helpful

Welcome to these user forums.

Your system report information show that you are using a very old build version of ATIH 2015 build 4061 - the final build version for 2015 was build 6613.  You should download the latest version from your Acronis Account - note: you need to register your ATIH 2015 serial to your account.  You can also download an ISO image for the latest Acronis bootable rescue media to burn to CD.

Next, your disk information shows that your source drive - 1.5TB WD HDD has problems with Linux partitions that you have on this drive:

          PS         Speed IFace Hs-Bs-Tg Model                     
Num  NT    L9NO  Size FSsize Free FS     Type            Label       ABCHSV Error
---- ----- ---- ----- ----- ----- ------ --------------- ----------- ------ ----------
1-   d(0) MBR   1.4T    1K ATA   0-0-0    WDC WD15EARS-22MVWB0      
  -1  p(1) ----   17G   17G    5G NTFS   27 Windows RE H PQSERVICE.. -CC--V
  -2  p(2) --C-  100M  100M   76M NTFS   07 NTFS, HPFS   SYSTEM RESE ACC--V
  -3  p(3) --DC  941G  941G  595G NTFS   07 NTFS, HPFS   Gateway.... -CC--V
  -4                              table  05 Extended                 ------
  -5  p(4) ----   19G   19G   13G Ext4   83 Linux native ........... -EE--V Block bitmap corrupted
  -6  p(5) ----  412G  412G  404G Ext4   83 Linux native ........... -EE--V Block bitmap corrupted
  -7  p(6) ----  9.3G  9.3G       LSwap  82 Linux swap,  ........... -CC--V
2-   d(1) MBR   932G    1K ATA   0-0-0    Crucial_CT1024MX200SSD1   
  -1  p(1) ----   52G   52G   40G NTFS   27 Windows RE H PQSERVICE.. -CC--V
                 879G             free                               ------

You will need to resolve the bitmap corruption issues before attempting any further clone operations.  Also having Linux partitions on the source drive will force ATIH to use sector by sector copy mode which will significantly increase the size required for the destination SSD drive.

Finally, it is not recommended to attempt this type of operation from within Windows - you should always use the Acronis bootable rescue media to do a clone.

Please see KB document: 56634: Acronis True Image 2016: Cloning Disks for the correct process for cloning disk drives, this includes a video tutorial and applies equally to 2015 as to 2016.

Thanks for replying.

I went to the products page for my Acronis account (https://account.acronis.com/products), but again it tells me that I have Acronis True Image 2014 OEM. When I click the "Downloads" link for that, the resulting page appears to be messed up; no text appears and I cannot do anything. (It looks like this: http://image.prntscr.com/image/5f2414ebf9234cdd90a382947b3ca547.png)

How would I go about fixing the block bitmap corruption? Some searches I did suggested using chkdsk /R on the partitions, but I am unable to do so. (One suggested way was getting the volume name with mountvol, but that didn't show the corrupted partitions. Another was to assign them a drive letter, but I am unable to do this either; I can't do anything but delete them in the Disk Management tool.)

For the ATIH 2015 issue, I would recommend looking at your Account page within the ATIH 2015 application GUI, making a note of the serial number that you have used to activate this, then try registering that serial number in your online Acronis Account.  If the serial number is accepted then you have not previously registered it.  If it says it has already been registered, then you need to contact Acronis Support - see link below in my signature and ask them to resolve the serial number / registration issue - you may need to provide details of any other email address where the serial number may have been registered.

For the bitmap corruption, as this occurs on your Linux partitions, I would recommend restarting and booting into the Linux distribution that you have installed and let Linux do any disk checks as it boots.  Linux should do a fsck check or this can be triggered from the linux partition but only on unmounted partitions.  If you have a Linux distro boot CD or DVD you could run fsck from that as an alternative - most distros have 'Live' CD / DVD editions that you can try from the optical media before deciding whether to install it.

The ATIH GUI does not have an account page, but through the website I see that my serial number is registered for ATI OEM.

I contacted Acronis support, but I was told that they cannot tell me anything at all becasue I got Acronis bundled with my SSD.

 

I booted into Linux from my DVD and ran fsck on the corrupted partitions, but Linux tells me that they are "clean". (I generated another system report in ATIH to check if it did anything to fix them, but it did not.)

If you have ATIH 2015 then you should see a page like mine shown in the attached image below:

Not sure what else to advise for the Linux bitmap corruption issue other than to suggest using Backup & Restore to just move your Windows partitions from your HDD to the new SSD instead of trying to do this via cloning.

Are you able to make a good backup image using ATIH of your Windows OS partitions, including any hidden system partitions (System Reserved / UEFI if present etc)?

Attachment Size
378263-131977.png 17.2 KB

I now have just my Windows partitions on my SSD. It wouldn't boot initially, but a boot recovery disk fixed that pretty easily.

Thank you for your help!

Thanks for the feedback, glad to hear that you have this working now.