Solved Help getting a cloned Win 7 disk to work in dual boot PC needed please

[TarotRedhand]

I have a problem. I have a dual-boot XP and Windows 7 PC. Each OS occupies its own HD. Last week Windows 7 wouldn’t boot until windows (eventually) succeeded in fixing some disk errors (I’m guessing bad sectors). As all the hard drives (there are 3) in this PC are made by Seagate I used Seatools to examine them. The HD that has win 7 on it failed the built-in short diagnostic self test. I therefore bought a replacement HD (taking the opportunity to get a slightly larger drive). I have cloned the old HD to the new on four separate occasions using three different tools. Each time with the same result – a boot loader error (the error number has a load of zeros followed by the letter ‘e’). Just to be on the safe side I have done a full backup of the data on both disks to partition on a new 2 terabyte HD.

A couple of background notes. Originally the Windows 7 PC had Vista on it but I upgraded it to Win 7 Home Premium a couple of Months ago. This was a boxed on DVD full version (not the upgrade version) that I bought as soon as it came out because MS were doing a cheap deal on it. Strangely it would not boot properly at switch on. I had to run it under Vista to install it. I mention this because there is supposed to be a way to fix my problem manually (even tells you the steps to take in the error message).

Unfortunately because I can’t boot from my DVD at load time I can’t use this method.

I am testing by simply unplugging the old drive and (using the same leads) plugging in the new, Then turning the power back on and trying to boot. Xp boots fine, but I get the error mentioned above for Win 7.

This is the hardware I am dealing with.

Disk 0 – Windows XP – 320 gig Sata
Disk 2 – Windows 7 – 320 gig Sata
New Disk 500 gig cloned using Seagate Disk Wizard and a usb Sata adapter.

The tools I have available are – Seatools, Seagate Disk Wizard, AOMEI Backupper Standard Edition 2.0, AOMEI Partition Assistant Standard Edition 5.5 and EasyBCD 2.2 (just updated today). All are installed both under Win 7 and XP.

Now I am pretty sure that EasyBCD 2.2 could be used to fix this. My problem is that there is just so much information on their site that I can’t find the information I need in order to do so. Instead I end up a gibbering wreck in the corner. Please could someone help by giving me step by step instructions?

Thanks in advance for any help.

TR

 

[gregrocker]

Post back screenshot of Disk Mgmt showing all drives.

Set DVD drive to boot first in BIOS setup, reboot with DVD in drive. Does it prompt to Press Any Key to boot disk? If not reset BIOS to defaults after taking note of SATA settings. If disk still will not boot try flash stick. Both are provided in Step 6 http://www.sevenforums.com/tutorials/219533-troubleshooting-windows-7-failure-boot.html tutorial below as we'll as other steps. http://pcsupport.about.com/od/tipstricks/ht/bootcddvd.htm

With all other HD's unplugged boot into Disk or stick http://www.sevenforums.com/tutorials/668-system-recovery-options.html to confirm partition marked active Then run 3 Startup Repairs until Win7 starts. Your imaging app probably needs boot disk to apply settings to mark Active and transfer MBR and Track 1. You may need to apply image from disk with other HDs unplugged. http://www.sevenforums.com/tutorials/71432-partition-mark-active.html

Boot preferred HD afterwards via BIOS Boot menu key

 

[TarotRedhand]

Thanks for the help, but I managed to fix it myself. Turns out there was no weird problem with my Win 7 install disk, just not quite enough patience on my part. I didn't realise that it would take as long as it did from the mouse pointer showing up to the actual install wizard appearing. I only discovered it by accident, otherwise I would probably be still pulling my hair out even now. Anyway, once the select language menu came up, it only took less than a minute to fix my problem.

Even though it is now fixed, and you asked for screenies, I will post them anyway.

As my system was prior to cloning the disk including the failing drive.

Which equates to this report from easyBCD

Windows Boot Manager
--------------------
identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device partition=D:
description Windows Boot Manager
locale en-US
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default {78ea5d4c-3f55-11dd-b40e-a1b775e1b465}
resumeobject {78ea5d4d-3f55-11dd-b40e-a1b775e1b465}
displayorder {466f5a88-0af2-4f76-9038-095b170dc21c}
{78ea5d4c-3f55-11dd-b40e-a1b775e1b465}
toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout 30
custom:45000001 1

Windows Legacy OS Loader
------------------------
identifier {466f5a88-0af2-4f76-9038-095b170dc21c}
device partition=D:
path \ntldr
description Earlier Version of Windows
custom:45000001 1
custom:47000005 301989892
6

Windows Boot Loader
-------------------
identifier {78ea5d4c-3f55-11dd-b40e-a1b775e1b465}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
recoverysequence {6a203036-baa7-11e3-acaa-001e8c2b8ef8}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {78ea5d4d-3f55-11dd-b40e-a1b775e1b465}
nx OptIn
custom:42000002 \system32\winload.exe
custom:45000001 2
custom:47000005 301989892
3

With the cloned (but unfixed drive)

Which gave this report in easyBCD

Windows Boot Manager
--------------------
identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device partition=H:
description Windows Boot Manager
locale en-US
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default {78ea5d4c-3f55-11dd-b40e-a1b775e1b465}
resumeobject {78ea5d4d-3f55-11dd-b40e-a1b775e1b465}
displayorder {466f5a88-0af2-4f76-9038-095b170dc21c}
{78ea5d4c-3f55-11dd-b40e-a1b775e1b465}
toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout 30
custom:45000001 1

Windows Legacy OS Loader
------------------------
identifier {466f5a88-0af2-4f76-9038-095b170dc21c}
device partition=H:
path \ntldr
description Earlier Version of Windows
custom:45000001 1
custom:47000005 301989892
6

Windows Boot Loader
-------------------
identifier {78ea5d4c-3f55-11dd-b40e-a1b775e1b465}
device unknown
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
recoverysequence {6a203036-baa7-11e3-acaa-001e8c2b8ef8}
recoveryenabled Yes
osdevice unknown
systemroot \Windows
resumeobject {78ea5d4d-3f55-11dd-b40e-a1b775e1b465}
nx OptIn
custom:42000002 \system32\winload.exe
custom:45000001 2
custom:47000005 301989892
3

And finally after my Win 7 install disk had fixed it.

Which gives the current report from easyBCD

Windows Boot Manager
--------------------
identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device partition=D:
path \bootmgr
description Windows Boot Manager
locale en-US
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default {6a203038-baa7-11e3-acaa-001e8c2b8ef8}
resumeobject {78ea5d4d-3f55-11dd-b40e-a1b775e1b465}
displayorder {466f5a88-0af2-4f76-9038-095b170dc21c}
{6a203038-baa7-11e3-acaa-001e8c2b8ef8}
toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout 30
custom:45000001 1

Windows Legacy OS Loader
------------------------
identifier {466f5a88-0af2-4f76-9038-095b170dc21c}
device partition=D:
path \ntldr
description Earlier Version of Windows
custom:45000001 1
custom:47000005 301989892
6

Windows Boot Loader
-------------------
identifier {6a203038-baa7-11e3-acaa-001e8c2b8ef8}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7 Home Premium (recovered)
locale en-US
recoverysequence {6a203036-baa7-11e3-acaa-001e8c2b8ef8}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {c526ca1b-cfa2-11e3-b62d-806e6f6e6963}

So thanks again and it now works (yay!)

 

[gregrocker]

I'm not familar with Aoemei partition asst and only use Partition Wizard which reverses the meaning of the System and Boot flags, which is why I asked to see the Disk Mgmt screenshot.

In Disk Mgmt whichever is marked System means it is booting the OS, or multiple OS's if applicable. The Boot flag only means the OS which is currently booted. PW reverses these flag's meanings.