Data Migration for Samsung SSD goes wonky...

[JesseZ]

Here is a post from http://reddit that I posted with little luck getting a response. Basically I cloned my WD Caviar SE16 wd3200aaks to my NEW Samsung 1tb 850 EVO SSD. My problem is when I try to boot using the cloned SSD my 2nd monitor doesn't work, my graphics driver appears to have gone wonky, and I'm in safe mode. If I turn off safe mode my computer restarts, but boots from the old hard drive with no problems.

How do I get my settings to work on the SSD and take advantage of the faster boot time?

Thanks and I apologize if this has been answered before, but I've been trying to fix this the past few days and broke my bootmgr and only just got my comp back up and running.

 

[ArtPog]

It would seem that something went awry in the disk-to-disk cloning operation. I'm sure that must have occurred to you. Did you try repeating the d-c operation? I presume you're using the Samsung Data Migration program, yes?

And did you check the SSD with Samsung's Magician program?

Now we're assuming that after you "broke my bootmgr" and "got my comp back up and running", your current HDD boot drive functions without ANY problems in that it boots without incident and the system subsequently functions problem-free, right?

 

[USAFRet]

1. What tool did you use?
2. If you remove the new SSD, does the system work as before, with the old HDD?
If so, you need to redo this, as mentioned above.

This is the steps I use for a cloning operation.
-----------------------------
Verify the actual used space on the current drive is significantly below the size of the new SSD
Download and install Macrium Reflect (or Samsung Data Migration, if a Samsung SSD)
Power off
Disconnect ALL drives except the current C and the new SSD
Power up
Run the Macrium Reflect (or Samsung Data Migration)
Select ALL the partitions on the existing C drive
Click the 'Clone' button
Wait until it is done
When it finishes, power off
Disconnect ALL drives except for the new SSD
Swap the SATA cables around so that the new drive is connected to the same SATA port as the old drive
Power up, and verify the BIOS boot order
If good, continue the power up

It should boot from the new drive, just like the old drive.
Maybe reboot a time or two, just to make sure.

If it works, and it should, all is good.

Later, reconnect the old drive and wipe as necessary.
Delete the original boot partitions, here:
https://social.technet.microsoft.com/Forums/windows/en-US/4f1b84ac-b193-40e3-943a-f45d52e23685/cant-delete-extra-healthy-recovery-partitions-and-healthy-efi-system-partition?forum=w8itproinstall
-----------------------------

 

[StitchExperiment626]

I would do a disk check and see if there are any errors on the hard drive. If there are then I would do disk check with repair.

Then I would format the SSD with a 4K sector.

Then you need to go into disk management and and activate the drive with a right click and make a bootable drive. Now if I got any of these steps mixed up I'm doing it from memory. Assign it a drive letter I think.
Then go to your disk copy software and select the drive 0 as source and all sub partitions. Then select drive 1 as destination. Then you don't want to choose file copy. You want to choose bootable if given the option and you want to copy all disk partitions and select all partitions. Then you want to select disk copy, NOT file copy.

Now on your hard drive there might be a jumper setting it as master. Do some research.
Sometimes the master drive needs to be plugged into into SATA 0 or 1 depending on the number and also sometimes in the BIOS it has to point to the SSD drive. And I don't remember but the right type of protocol has to be selected when there are multiple drives and some have to do with software R.A.I.D. or jobd just a bunch of drives.

Now you might pull the SATA connector from the hard drive and see if everything works before adding in the hard drive again.

Some programs and hardware are simple and others have many choices.

Please press the I like this answer button to get this off the unanswered queue.
Bruce G.