Macrium problems??

Not sure why this is happening, but tried to make a back up copy of C: to a spare SSD.
C: =256GB w/ 32GB used by system. Destination is 120GB. (Only 2 partitions on this MBR setup)

1. Tried a clone first, reflect refused said there was not enough memory on the destination drive. Done this before and it always shrunk the C: partition file to fit smaller drive.

2 Tried a restore of a 2 day old image of W10FCU. When the restore was finished it showed that a drive letter (F: ) was assigned to the system restore partition and no drive letter for W10 partition? Repeated same result. (Of course would not boot)

3. Fix was to remove drive letter for system restore and assign drive letter c: to the windows partition. Boots and runs normal. Any idea what is going on??

If you are making a "clone" (not a disc image) of the 256GB drive, a clone copies the entire drive, data, bad sectors, bad data, etc, not just the part used. Thus the 256GB is too much for the 120 GB drive.

What you need to is make a disc image of the 256GB drive (all partitions) to the backup drive. The disc image only copies the actual data, not bad sectors, bad data, etc.

I use Macrium and all I use is disc images.

fireberd said:

If you are making a "clone" (not a disc image) of the 256GB drive, a clone copies the entire drive, data, bad sectors, bad data, etc, not just the part used. Thus the 256GB is too much for the 120 GB drive.

What you need to is make a disc image of the 256GB drive (all partitions) to the backup drive. The disc image only copies the actual data, not bad sectors, bad data, etc.

I use Macrium and all I use is disc images.

Greetings It seems easier to make a clone (when needed) than making an image and restoring it to another drive>

From Macrium, "Cloning with Macrium Reflect creates an exact copy of partitions to a different drive. For example, Upgrading to a larger hard drive or moving from a large magnetic hard disk to a smaller and faster SSD. When you Clone a hard drive, you can boot from the target disk on the same system after cloning."

I do make 100 to 1 images but once in a while a like a clone. i.e. If, and I hope never, the C: dumps, I can put in a clone and resume almost immediately rather than using rescue media, then doing a restore. YMMV

After you have selected the Target Disk,have you tried modifying the partition sizes by clicking CLONED PARTITION PROPERTIES, and adjusting the size of a partition by using the PARTITION SIZE entry box? This works on HDD's,I don't have an SSD so don't know about that.

assign drive letter c: to the windows partition

What method did you use to do that?

Any idea what is going on??

Sounds like an issue with the bcd entry.

SIW2 said:

What method did you use to do that?
Sounds like an issue with the bcd entry.

I just assigned a vacant drive letter to the w10 partition when it had none and then when I booted from it, it was changed to C:, should have clarified that.

topgundcp said:

Making a backup image is always a better choice, especially if you have a paid version of Macrium, you can do a delta restore to the same disk a lot lot faster, it only restores the changes between the source and destination, hence will prolong the life of the SSD.

Tx for that, In my example of C: failure, I was talking about a complete hardware failure in which another complete drive would have to be used. I tried another clone attempt and this time both partitions were assigned drive letters G: & H: This one booted fine and of course the system changed H: to C: Will change G: to "none" just to get rid of the confusion.