You have a GPT DISK which doesn't support MBR booting. The screenshots conflict but I'm Assuming its the target HD as Win7 wouldn't boot otherwise.
If so rightclick on the Disk # in Disk Mgmt to Convert to MBR which should bring it to Unallocated space then try the clone. More options should appear or you can mark Active then repair afterwards with all other drives unplugged.
by GPT I think you are referring to the 3tb drive. This disk is not in question and working fine?
edit: ok I apologize I selected the wrong one.
Now I have a drive letter option but again I can't use c as its taken and I have the option to use primary,active, or logical. I kind of want primary and active no?
also set aliment to vista/7 was set to xp
This is handled by Auto setting in Acronis. But for something so critical required for every OS clone it's gotta be in the Manual.
Primary Active
in the mean time I checked with EBCD and used the bcd store option. I had to assign it a letter to see it. and it read the loader as:
but when I try to boot to it no boot loader is shown. No os is found. The drive is now primary and active.There is one entry in the Windows bootloader.
Path: X:\Boot\BCD
Default: Windows 7 64 ssd
Timeout: 5 seconds
EasyBCD Boot Device: X:\
Entry #1
Name: Windows 7 64 ssd
BCD ID: {default}
Drive: C:\
Bootloader Path: \Windows\system32\winload.exe
Please someone correct me if I'm wrong but since I have used computers say well before windows was around a driver letters mean nothing at MBR level. This is what confuses my about today times. Maybe its a win7 thing I dont know, but we used to tarted drive(0) part(1) ect... not by driver letters. So what does
Drive: C:\
Bootloader Path: \Windows\system32\winload.exe
mean? How can a boot loader know what a C: is? Is EBCD converting the disk location to a readable letter, should I change that to x: ? I dont want my OS to use x:\ as %system root%
ok I used MbrFix64 to fix the mbr and sector. Now the new drive shows a boot loader. But instead of booting to its OS its looking at my old OS. So I guess I have to tell the boot loader to boot to x: but I really dont want to do this.
Edit: I changed the bootloader to boot to "boot" instead of c:\ and it started to boot, then did an autocheck failed then blue screen. So this drive letter stuff is just overly confusing IMO. I guess using the win7 disc at this point may get it work.
Is there some reason you can't follow the Manual or Help to image your OS and then apply the image?
If the instructions are not clear then I'd use the free Acronis app for WD drives which has a Manual anyone can understand right on the Downloads page at WD Support
I dont see anywhere in the manual where it talks about my issue. I belive my issue is no longer the imaging process but a catch 22.
Both drives can not be C:\, in order to boot the new drive I need it to be c:\. Normally in a disc clone you discard the source drive. I guess going from a partition to a disk is a big deal?
Unfortunately I just can find the answer I need to figure it out at the moment. I'm just going to have to find out how the win7 boot loader works, was hopping someone already new.
Are you unplugging all other HD's ?
After cloning are you unplugging the source HD?
If not are you setting the cloned HD first to boot in BIOS setup?
Try again following the video making sure to unplug all other drives.
If this fails I would change to imaging, save image externally or to another HD, unplug source HD, boot Rescue Media to apply image to unallocated space.
Yes that is what I was doing, and the drive has a boot loader and it boots, then I get a black screen about auto check disc then a blue screen. So I put in the windows 7 install CD and let it run its checks and on the second go if found the problem and told me it cant fix it. Under the details it complained about a bad driver.
The cloned Disc is a SSD, maybe the MB stata driver is causing issue? So I was going to boot in to safe mode and now the MBR is broke again, guessing windows did this. So my plan is to fix it yet and again and this time boot to safe mode.
Strangely I enjoy this stuff, I'll report back.
Have you marked the clone partition Active, unplugged all other drives, then run Startup Repair - Run 3 Separate Times?
Please confirm you are doing exactly this since we know from countless cases this can start a balky clone or image.
Quote