Need help - cloning action has split boot and sys acrsoos 2 disks

Once you cloned the HD the fact C has no System flag tells you that you still need to repair or write the System boot files to it.

To do this unplug the other HD, make sure the clone is set first to boot in BIOS setup, then run Startup Repair - Run up to 3 Separate Times until C holds the System Active flag.

Now you can plug back in the other HD, boot it if needed by tapping the one-time BIOS Boot Menu key at boot. If you want to use it for storage, wipe it with Diskpart Clean Command then partition it in Disk Mgmt.

gregrocker said:

Once you cloned the HD the fact C has no System flag tells you that you still need to repair or write the System boot files to it.

To do this unplug the other HD, make sure the clone is set first to boot in BIOS setup, then run Startup Repair - Run up to 3 Separate Times until C holds the System Active flag.

Now you can plug back in the other HD, boot it if needed by tapping the one-time BIOS Boot Menu key at boot. If you want to use it for storage, wipe it with Diskpart Clean Command then partition it in Disk Mgmt.

Many thanks for the above. Will certainly note if for future reference. Thread bookmarked. Cannot implement it now has that ship has sailed.

BUT I WOULD LOVE TO KNOW WHY it is that when cloning from Soruce to Target, one can be left with a different Source ! To date, I naively assumed this could never happen. To date I thought if I have a perfrect working bootable Source Drive, and cloned it, I would then simply have is a populated target drive (and perhas need to repair to boot it on its own later0. I had never dreamed in a million years that the Source would be affected and my system would no longer boot as it did before, or teh sys and bootmg fiels would move to the target drive. and that I would have to do some heroic expert level gymnastics jsut to get things back too how they were. Is is just a flakey EaseUS cloning processes, or is all cloning like this?


For me, the act of cloning was a death sentence to at least 8 hours of followup work, and even then not quite getting back to wehre you started.

A great lesson learned for me. I will never clone again, unless I tiruly have no use for soruce ( ie clone source to target, remove source, do heroics on the target untul it works)

Bottom line, this is not cool and essentially an impossible task for a casual users, This is 2012. Two year olds can master ipads. It should not have to be this complicated. And this is ust one of a hundred examples. Thnigs should be quantum leaps frendlier than they are. Jsut look at the volume and the details in the tutorials on this forum and the neccesity for them. They are incrediblly done, but OMG, the poor user!!

I've been computing since 1983. Witnessed amazing progress,,, but some things have juat gotten worse, and time is getting way too preciious. I will be staying 1000 miles ways from Windows 8, and I am not looking forward to the day when I need to migrate to Windows 9, 10 or 11. Perhaps by then my 5 home pcs will be a thing of the past, everything will be on iPad-like devices, backed up locally and on secure clouds.

Untill then, its good to be member oof a great forum :)

We don't recommend Easeus cloning here that I've seen. What most often is recommended is free Macrium - Image your system.

I like Acronis free premium cloning/imaging app which comes free with a WD or Seagate HD in the mix. Acronis never fails for me.

Often there is a setting to copy the MBR and Track0, as well as Mark Active and always a primary partition if System Boot files are onboard C. Lacking these settings can cause the clone to not start, although failure to start is common enough we give out the repair steps regularly. I'm just sorry it took so long.