Has anyone cloned ver 2004 using Macrium reflect?

Page 1 of 2 12 LastLast

  1. Posts : 22
    Win 10 1803
       #1

    Has anyone cloned ver 2004 using Macrium reflect?


    Macrium Reflect fails with "insufficient Space" message when I try to clone my Win 10 version 2004 system disk.

    I have regularly cloned my SSD system disk in the past, about monthly, writing over previous clones on a loose SSD. Last successful clone was of version 1909 on 22 May, anticipating the update.
    My system disk is an internal 450 Gb SSD card that contains 180 Gb of files (GetFolderSize). This much has been successfully written to 250 Gb Drives in the past.

    None of the 250s nor a pair of recently purchased, clean 500s will work with ver 2004, I tried them all.

    Reflect was removed, a fresh download procured, and installed - same problem.

    With only a free version, I cannot contact Macrium. If this is a ver 2004 problem, maybe somebody with a licence can tell them.
      My Computer

  2. Steve C's Avatar
    Posts : 6,373
    Windows 10 Pro 64 bit
       #2

    What happens if you use imaging rather than cloning?
      My Computers

  3. Bree's Avatar
    Posts : 19,144
    10 Home x64 (20H2) (10 Pro on 2nd pc)
       #3

    stonecherub said:
    Macrium Reflect fails with "insufficient Space" message when I try to clone my Win 10 version 2004 system disk....
    Steve C said:
    What happens if you use imaging rather than cloning?

    Should work fine, I have successfully imaged and restored my 2004 system disks with Macrium Reflect Free. I don't use cloning as a rule, but I can set up and test that in a VM with a pair of .vhdx virtual disks....

    Edit:

    ...confirmed. As the OP was cloning to a smaller disk, I set up a .vhdx of 100GB to take the clone of a 127GB system disk. I have two VMs available to test, one with a clean install of 1909 Pro, the other a clean install of 2004 Pro. Both are otherwise identical UEFI machines. In both I installed the current latest Macrium Reflect Free v7.2.4971.

    1909

    Has anyone cloned ver 2004 using Macrium reflect?-macrium-reflect-free-clone-1909.png

    ...producing this result:

    Has anyone cloned ver 2004 using Macrium reflect?-image.png

    2004


    Has anyone cloned ver 2004 using Macrium reflect?-macrium-reflect-free-clone-2004.png


    The next step will be to try and reproduce this on one of my physical machines wih the paid-for Reflect installed. Then I can report it on the Macrium forum. It will take some time as I have to find a suitable external drive to clone to. I'll need to see if I can rearrange some of my backup drives to free up one I can use for this test.
    Last edited by Bree; 23 Jun 2020 at 03:18. Reason: tested
      My Computers

  4. Bree's Avatar
    Posts : 19,144
    10 Home x64 (20H2) (10 Pro on 2nd pc)
       #4

    @stonecherub, while you wait for a fix, I have found a workaround to make the clone work in 2004.

    What appears to be the problem is that the resizing of the C: partition is not being correctly calculated. You can manually adjust the cloned size to make space for the clone to succeed.

    Run the clone so that it fails, then click the OK in the failure message.

    Has anyone cloned ver 2004 using Macrium reflect?-1.png

    Now select the clone of the C: partition in the destination drive, click Cloned Partition Properties, and adjust the free space to make room for the missing partition.

    Has anyone cloned ver 2004 using Macrium reflect?-2.png

    Now click and drag the missing partition from the source drive and drop it onto the destination clone drive.

    Has anyone cloned ver 2004 using Macrium reflect?-3.png

    The clone will now run successfully.

    Has anyone cloned ver 2004 using Macrium reflect?-4.png


    And as final confirmation that it is just the resizing calculation that's at fault for 2004, if I make the destination drive the same size or larger than the source drive the clone will run without error.


    Edit: I have now reported this fault on the Macrium forum: Cloning to a smaller destination drive fails in Windows 10 version 2004


    2nd edit: Turns out that this is due to Microsoft changing where the recovery partition is placed for 2004 and not Macrium's fault at all. Manual resizing of C: to make room for the recovery partition at the end will be needed from now on.
    Last edited by Bree; 23 Jun 2020 at 13:19. Reason: reported fault to Macrium
      My Computers

  5. Bree's Avatar
    Posts : 19,144
    10 Home x64 (20H2) (10 Pro on 2nd pc)
       #5

    Macrium have replied on their forum and pointed me to this Knowledge base article.

    Message Not all partitions copied. Insufficient space - KnowledgeBase v7.2 - Macrium Reflect Knowledgebase

    The reason this didn't happen in 1909 was that the C: partition was the last partition on the drive, and could therefore be shrunk to fit. In 2004 Microsoft have made the Recovery Partition the last one, after the C: partition. C: still gets shrunk to fit, but unless you then manually resize it to make room for the recovery partition there won't be any room left for it.
      My Computers

  6. ThrashZone's Avatar
    Posts : 7,125
    3-Win-7Prox64 2-Win10Prox64
       #6

    Hi,
    If you system image regularly just delete the recovery partition.
      My Computers

  7. dalchina's Avatar
    Posts : 30,472
    Win 10 Pro (1903)
       #7

    - and be aware of what you lose by doing so- a substitute for most being to have a bootable Win 10 disk.

    Bree said:
    In 2004 Microsoft have made the Recovery Partition the last one, after the C: partition. C: still gets shrunk to fit, but unless you then manually resize it to make room for the recovery partition there won't be any room left for it.
    Interesting- wouldn't that have been observed in earlier builds too, where a larger recovery partition was created after C: following an upgrade? E.g. my active Recovery partition is after my C: partition with 1903.

    Which is presumably why that article exists.
      My Computers

  8. ThrashZone's Avatar
    Posts : 7,125
    3-Win-7Prox64 2-Win10Prox64
       #8

    Hi,
    Well if the machine booted before the recovery partition at the end of C was there the machine will boot after it's deleted
      My Computers

  9. Bree's Avatar
    Posts : 19,144
    10 Home x64 (20H2) (10 Pro on 2nd pc)
       #9

    dalchina said:
    Interesting- wouldn't that have been observed in earlier builds too, where a larger recovery partition was created after C: following an upgrade? E.g. my active Recovery partition is after my C: partition with 1903.
    Both the VMs I tested this on were clean installs of 1909 and 2004 respectively, and the 1909 clone worked while 2004 didn't. The positioning of the recovery partition was the default for each install, MS seem to have changed it for 2004.
      My Computers


  10. Posts : 22
    Win 10 1803
    Thread Starter
       #10

    Bree:
    Once-upon-a-time, this all made sense to me but, as I become an octogenarian, I find both my knowledge and my confidence are deteriorating. I no longer get the picture.

    In my old machine that blew-up last spring, C:/ was a 250 GB SSD that I would regularly clone to a loose SSD of the same size; sometimes leaving the target as the active drive (assuring that my back-up worked), other times setting it aside.

    The machine I built to replace it has a M.2 internal SSD of 464.72 GB (nominal) capacity. Before 2004, I had been cloning that to one of the 250 GB SSDs because C:/ never had more than 200 GB worth of files. I bought a pair of Crucial 500 GB SSDs just in case, each is 447.13 GB size (nominal), smaller than the M.2 drive. This morning, I was able to image my 2004 C:/ drive to one of them.

    You said: "Turns out that this is due to Microsoft changing where the recovery partition is placed for 2004 and not Macrium's fault at all. Manual resizing of C: to make room for the recovery partition at the end will be needed from now on."
    I no longer know how to do that.

    I am re-thinking the whole enterprise. Swapping a damaged, loose 250 GB drive with a good one was trivial. Now, I must have control of Win10 and Reflect to write a good copy of C:/ onto the internal drive. And I just keep getting older!

    Dan Lynch
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 09:48.
Find Us




Windows 10 Forums