Cloned OS to SSD = boot loop at Windows login Win7 64bit

J_Walker

Honorable
Jun 13, 2012
9
0
10,510
So I had a 1TB drive with 2 partitions - Windows 7 64bit on C: and Data partition on the rest (F:)
Bought a Samsung SSD 830 256GB

I used Norton Ghost 15 (actually followed Samsung's Data Migration manual that came with the drive) to clone the old OS drive to the SSD. After the clone, I shut down the system, unplugged the old drive, booted the system. Boots fine until it gets to the Windows login screen, sits there for maybe 10 seconds, i'm lucky if I can get my password typed in, then it just reboots. If I plug the old drive back in (so both drives are plugged in), it will boot without issue. After doing so and logging in, Windows is definitely running off the SSD, and the SSD is assigned drive letter C: and marked the boot partition. The old OS partition is drive G:. I tried running startup repair with only the new SSD connected, and it didn't even list any drives. Not sure if I need drivers, it's connected to the Intel SATA3 controller on an Asus P8P67. Ran it anyways and it didn't do anything, as expected.

Obviously, I can't boot from just the old drive, as it complains of missing media.

Ran EasyBCD and it seems like everything is pointing to C: in the MBR. That's about as deep as I've gotten, and I don't have much experience beyond that.

Can anyone give me any ideas as to what's going on here?

drives.jpg


So basically, Windows won't boot unless both drives are connected.
 


Someone ought to tell Samsung that so they don't put it in their manuals? I have done this before without issue.
 
You have an ideal setup with the 1tb drive having two partitions and having your data on the second partition. All you need to do is disconnect the hard drive and do a fresh install of Windows on the SSD. Once your satisfied with the install and it's working fine you can delete the partition that has Windows on it and use the whole drive for storage.
 


Don't you think I would've done that in the first place if I didn't care about retaining my current Windows install?
 
I have used Acronis TrueImage Home many times to clone HDDs onto SSDs, or SSDs onto larger SSDs. None ever failed to work. I could have sworn I saw something somewhere about Norton Ghost compatibility problems, but I honestly don't remember. It might be worth trying another cloning program.
 


Why would I be cloning the OS drive? That should clue you in.
 
Redo the "Migration" Using EasyUS (free download).
http://www.todo-backup.com/?gclid=CPOHytr_v7MCFVBgMgodLHkAog

1) What happend is You "cloned the OS, UT NOT the MBR which is still on the HDD.
You Need to Migrate the Both the OS Plus the Boot sector.

PS You do NOT want to do a "clone" True clone is a sector-by-sector Copy. You want to Migrate from One HDD to a SSD. Migrating should both enable trim and align your partition correctly.

I personally pefer EZ-Gig, but that like about 15 bucks. The program is free, but requires a Special Sata -> USB cable.
 


Ghost copies the MBR, as there is a check box specifically for it. Also, you should seriously contact Samsung and tell them to rewrite their manuals, because I followed their "Migration" manual as outlined. They even include a copy of Ghost 15 on the CD. If it didn't copy the MBR, the SSD connected by itself wouldn't have even booted Windows at all.
 
^ What happened is the same as when you do a Clean install, but leave the Old OS drive connected during the install. Some info required to complet loading is placed on the HDD, not the SSD. So when booting if both drives are connected - No problems. If only the SSD is connected this info is NOT there so SSD can not complet loading.

Clonning, in the true form, will not move this info, Migration does. I have Not had any problems using both EasyUS nor with EZ-Gig. have not used Norton Ghost.

Bottom Line.
To correct this (a) leave HDD connect, but if that HDD fails you have the same problem. (b) redo the Migration.