tag:blogger.com,1999:blog-7933794355391496434.post7831851308568283887..comments2023-06-03T06:26:18.614-06:00Comments on A Million Chimpanzees: Cloning Two Hard Drives with Acronis True Image Home 2011james.pyleshttp://www.blogger.com/profile/11424800834517755783noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-7933794355391496434.post-85704494005813666972015-06-18T11:16:23.694-06:002015-06-18T11:16:23.694-06:00It happens often after cloning both drives have id...It happens often after cloning both drives have identical part numbers or serial numbers,<br />FIX: Open windows disk management and click on the SMALL red icon near the left / drive nameUnknownhttps://www.blogger.com/profile/08189327186235734790noreply@blogger.comtag:blogger.com,1999:blog-7933794355391496434.post-12775368542057632842012-05-21T18:49:36.569-06:002012-05-21T18:49:36.569-06:00Actually, I think I got the original boot sequence...Actually, I think I got the original boot sequence mixed up as I have it listed above. It's actually:<br /><br />1. Onboard or USB CD-ROM (which is probably the CD-DVD drive on SATA 2<br />2. ST332xxxxxx (old data drive on SATA 1)<br />3. ST1000xxxxx-9xxxxx (OS on SATA 0)<br /><br />But that shouldn't matter since the bootmgr and boot loader are both on the C drive.james.pyleshttps://www.blogger.com/profile/11424800834517755783noreply@blogger.comtag:blogger.com,1999:blog-7933794355391496434.post-81148038933274558052012-05-21T18:37:38.534-06:002012-05-21T18:37:38.534-06:00With all three drives plugged in (C: OS SATA 0, D:...With all three drives plugged in (C: OS SATA 0, D: old data drive, SATA 1, F: new data drive, SATA 3) I ran the bcdedit command and got this result:<br /><br />Microsoft Windows [Version 6.1.7601]<br />Copyright (c) 2009 Microsoft Corporation. All rights reserved.<br /><br />C:\Windows\system32>bcdedit<br /><br />Windows Boot Manager<br />--------------------<br />identifier {bootmgr}<br />device partition=C:<br />description Windows Boot Manager<br />locale en-US<br />inherit {globalsettings}<br />default {current}<br />resumeobject {721fabc1-edb4-11de-922e-cdab3013c52a}<br />displayorder {current}<br />toolsdisplayorder {memdiag}<br />timeout 30<br /><br />Windows Boot Loader<br />-------------------<br />identifier {current}<br />device partition=C:<br />path \Windows\system32\winload.exe<br />description Windows 7<br />locale en-US<br />inherit {bootloadersettings}<br />recoverysequence {721fabc3-edb4-11de-922e-cdab3013c52a}<br />recoveryenabled Yes<br />osdevice partition=C:<br />systemroot \Windows<br />resumeobject {721fabc1-edb4-11de-922e-cdab3013c52a}<br />nx OptIn<br /><br />C:\Windows\system32><br /><br />In other words, the exact same result as before.<br /><br />I did notice something interesting when I went into the BIOS though. <br /><br />Before changing anything, my computer is set to boot as follows:<br /><br />1. Onboard or USB CD-ROM (which is probably the CD-DVD drive on SATA 2<br />2. ST1000xxxxx-9xxxxx (OS on SATA 0)<br />3. ST332xxxxxx (old data drive on SATA 1)<br /><br />I don't know if this is important, but its set to RAID on with the other two options being RAID autodetect/AHCI and RAID autodetect/ATA.<br /><br />I exchanged the old data drive and the new data drive and something very interesting happens. Boot sequence is:<br /><br />1. Onboard or USB CD-ROM (which is probably the CD-DVD drive on SATA 2<br />2. ST1000xxxxx-9xxxxx (OS on SATA 0)<br />3. ST1000xxxxx-9xxxxx (new data drive on SATA 1)<br /><br />When the computer is actually going through its startup routine, you can see that each drive has an identical part number and different serial numbers, but in the BIOS, all you can see is that both drives seem to be identified by their identical part number. It's as if the BIOS sees both drives as the same but only one of them has the bootmgr.<br /><br />The boot sequence for this configuration looks like this:<br /><br />1. Onboard or USB CD-ROM<br />2. ST1000xxxxx-9xxxxx<br />3. Onboard or USB CD-ROM<br />4. ST1000xxxxx-9xxxxx<br /><br />When I put all three drives in, it gets even stranger. In the boot sequence is like this:<br /><br />1. Onboard or USB CD-ROM <br />2. ST332xxxxxx (old data drive on SATA 1)<br />3. ST1000xxxxx-9xxxxx<br />4. Onboard or USB CD-ROM<br />5. ST1000xxxxx-9xxxxx<br /><br />The computer really, really, really wants ST332xxxxx to be hooked up to SATA 1 and doesn't care what drives come after that.<br /><br />Ideas?james.pyleshttps://www.blogger.com/profile/11424800834517755783noreply@blogger.comtag:blogger.com,1999:blog-7933794355391496434.post-10863915635765613252012-05-21T05:53:01.256-06:002012-05-21T05:53:01.256-06:00Actually, just for giggles, I typed "bcdedit&...Actually, just for giggles, I typed "bcdedit" (as administrator) at the command prompt and got the result I was expecting. bootmgr is on the C drive:<br /><br />Microsoft Windows [Version 6.1.7601]<br />Copyright (c) 2009 Microsoft Corporation. All rights reserved.<br /><br />C:\Windows\system32>bcdedit<br /><br />Windows Boot Manager<br />--------------------<br />identifier {bootmgr}<br />device partition=C:<br />description Windows Boot Manager<br />locale en-US<br />inherit {globalsettings}<br />default {current}<br />resumeobject {721fabc1-edb4-11de-922e-cdab3013c52a}<br />displayorder {current}<br />toolsdisplayorder {memdiag}<br />timeout 30<br /><br />Windows Boot Loader<br />-------------------<br />identifier {current}<br />device partition=C:<br />path \Windows\system32\winload.exe<br />description Windows 7<br />locale en-US<br />inherit {bootloadersettings}<br />recoverysequence {721fabc3-edb4-11de-922e-cdab3013c52a}<br />recoveryenabled Yes<br />osdevice partition=C:<br />systemroot \Windows<br />resumeobject {721fabc1-edb4-11de-922e-cdab3013c52a}<br />nx OptInjames.pyleshttps://www.blogger.com/profile/11424800834517755783noreply@blogger.comtag:blogger.com,1999:blog-7933794355391496434.post-82361644908392556352012-05-21T05:41:33.581-06:002012-05-21T05:41:33.581-06:00Thanks for the insights. I'll have to wait unt...Thanks for the insights. I'll have to wait until I get home from work tonight to try this out. I'll post results when do.james.pyleshttps://www.blogger.com/profile/11424800834517755783noreply@blogger.comtag:blogger.com,1999:blog-7933794355391496434.post-81984917745615448762012-05-21T00:49:21.573-06:002012-05-21T00:49:21.573-06:00There are numerous possibilities why this might no...There are numerous possibilities why this might not work. Two of the most likely are the following:<br /><br />* The Master Boot Record tries to boot from the other HDD instead of the actual system partition because of a misidentification<br /><br />* Your Boot Manager is located on the Data Drive and by removing it it can't be found anymore.<br /><br />You can try the following to analyze this further:<br /><br />Unplug both old and new data drive and boot. If it boots then option 1 is most likely.<br /><br />If it doesn't boot (meaning same error as before) then data contains the boot manager.<br /><br />In either case you can open up a command window (cmd) and enter: bcdedit<br /><br />This way you can check what is what and the related uuid's. Post the result of the command here with all 3 drives connected.<br /><br />- Andreastcmsurferhttps://www.blogger.com/profile/04784767774912263977noreply@blogger.com