Large HDD clone to smaller SSD Clone

Toggle sidebar Toggle sidebar
A

allgar

Honorable
Jun 25, 2014
25
0
10,530
So I'm trying to clone my boot drive to a new SSD. I'm in Windows 10. I'm going from a 1TB Seagate with about 50GB of total data on it, to a 120GB SSD.

I have been trying to use Macrium Reflect without success. I can drag and drop the partition I want on to the smaller SSD, and start the process. However, each time I get the following error:

restore failed - write failed - 22 - Invalid argument - WriteFilemSystemData failed - pDataRun == Null-RemapMFTRecord failed

IT occurs immediately following the SSD TRIM when it's copying over some file (will have to try it again to get the exact name but I think it's $MFT... Master File Table)

I've tried everything I can think of, I've reformatted and run Optimize on the new SSD. I've run defrag and optimize on the HDD. I have used the advanced options in Macrium to "Ignore bad sectors when creating images" (and of course did it first without checking that box).

I've created (successfully) a full backup image to an external drive, and tried restoring it to the SSD, but again it failed immediately after the SSD TRIM.

I truly am out of options. Really, I have no idea why the SSD won't accept the image. I can copy files to the SSD no problem. I've formatted it, and created a partition and marked it active... I mean, honestly I'm really not sure what's keeping it from accepting the new image.

Anyone have any ideas?
 
Sort by date Sort by votes
USAFRet

USAFRet

Titan
Moderator
Mar 16, 2013
171,486
17,932
184,590
I have been trying to use Macrium Reflect without success. I can drag and drop the partition I want on to the smaller SSD, and start the process. However, each time I get the following error:
Click to expand...

No, that is not the way to do this.
Select the drive you wish to clone, and click on "Clone this disk..."
HTBDkVk.jpg
 
Upvote 0 Downvote
A

allgar

Honorable
Jun 25, 2014
25
0
10,530


Sadly that isn't the way to do it when moving from larger to smaller. If you do that , it will just immediately tell you there is not enough disk space. They advise to drag and drop when moving from a larger to a smaller, but then it does leave behind the small partition, which presumably might be important... not sure how to get around that. Perhaps I'll try a different service.

 
Upvote 0 Downvote
USAFRet

USAFRet

Titan
Moderator
Mar 16, 2013
171,486
17,932
184,590


With Macrium, it takes only the actual used data. Not the entire partition.

http://knowledgebase.macrium.com/display/KNOW/Backup,+imaging+and+cloning
"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."
 
Upvote 0 Downvote
burdenbound

burdenbound

Splendid
Aug 9, 2011
3,225
0
22,960
Just yesterday I tried to clone the SSD on my laptop to a different SSD and I tried macrium, acronis, and easeus and they all wouldn't work. This was an older laptop (circa 2011) and it just wouldn't play nice, I have used acronis and easeus in the past no problem but I ultimately did a fresh OS install and moved on. Perhaps you are running into a similar unknown issue.
 
Upvote 0 Downvote
A

allgar

Honorable
Jun 25, 2014
25
0
10,530


Thanks for the feedback. I am quite familiar with Macrium, just never ran into this error before. I am using it correctly, but the error is the real problem here. I can assure you, drag and drop does work. You simply press clone this disk, select the destination drive, then drag and drop the partition from the origin disk onto the destination. Usually works like a charm. Sadly in this case it just won't work.
 
Upvote 0 Downvote
A

allgar

Honorable
Jun 25, 2014
25
0
10,530


Yeah, sadly I can't do that. I have continued to do research and it would appear that the error 22 has to do with a loss of connection between the two drives. So, I think there must be corruption on the SSD somehow. It is an old drive, so perhaps it's just not going to work.

Like you say, sometimes, it's just best to move on. I think I might just get a new SSD and try again with a new one.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom