![]() ![]() One alternative you may prefer is to use a USB enclosure or (for even easier access) a USB drive dock instead. It seems unwise to move newly discovered devices to the top of the boot order as seems to have happened here, but if that's something your system does, you'll have to deal with it. ![]() ![]() If you can't disable/remove it, then put it at the bottom of the list, and from that point on the boot order should be maintained even as subsequent clone jobs run - but verify that. The bottom line is that when cloning a system disk to another internal disk, after running the first job that makes that target bootable, you definitely want to check your boot order and maybe even disable/remove the target from the boot list entirely if your system supports that. Technically you would have gotten some indication that something was amiss because Reflect would have prompted you to restart in order to run that job since you can't overwrite the partition containing the running Windows environment while Windows is running from it, but even that warning might have been easy to dismiss. ![]() In that case, running that same clone job again in the future could have caused your original source to overwrite your target that you'd been running from since the first job, thereby causing you to lose everything since your original clone job. You might actually have ended up worse off in the longer term if the clone had succeeded, since in that case your system might have started booting from the target drive without you even realizing it. Just as an additional note, this scenario of your system potentially switching to another boot device after a clone operation raises an even more hazardous condition. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |