Windows 10: 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??

:)

 

Disk Imaging

Hi, this is Rob again.

Try Macrium Reflect - Free for home use.

How to Create a Full-Disk Backup of Your PC with Macrium Reflect

https://www.howtogeek.com/howto/7363/macrium-re...

Macrium Reflect - Free

Macrium Software | Macrium Reflect Free

Hope that helps and feel free to choose a rating and have a great day!

 

windows 10 installation fails "pagefault_in_non-paged_area" pssnap.sys

I have three PC's. Two of them have the new Macrium Reflect Free Edition, i.e. version 6. One PC still has the old version 4.2. The PC's with the new Macrium version 6 upgraded from Windows 7 Pro and from 8.1 Pro with no issues. The Windows 7 Pro PC
with the old Macrium version failed with the pssnap.sys page fault. I suggest removing Macrium prior to upgrading to Windows 10 and then installing Macrium version 6 after Windows 10 is up and running.

 

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.*Biggrin 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.

 

Not exactly. There are 2 types of cloning: Intelligent sector copy and forensic. With forensic, you must have the destination drive equal or larger in size and also cause conflict with disk signature (2 disks having the same id). Cloning with intelligent sector will not create an exact copy ie. it does not copy bit by bit/sector by sector.



The reason you did not have a letter assigment is caused by cloning since it cannot have the same drive letter. It is better to copy ie. on the target drive, delete all partitions then drag and drop each partition to the destination disk. With copy, you can also swap/adjust the partition size without using any third party partition manager.
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.

 

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.*Doh

 

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.

 

I was advised on the forum to use imaging rather than cloning when transferring the OS to prevent having two disks with the same ID connected to the PC.

 

Let's get things clear.

1) cloning is used when you want to replace an existing drive with an exact copy on a new drive.

Cloning wipes pre-existing data on target drive.

2) Image backups are used when you want to make a backup copy of existing drive, to be primarily used to restore back to original source drive.

It just so happens, you can effectively clone as well by restoring image to a new drive.

Image backups are just another file and do not wipe data on a target drive.

Cloning is only really useful when REPLACING a drive.