Problem with copy my harddrive to move to a new HD

First off I'l post my info: Windows 7  64bit, sata to sata.
I'm using the copy my harddrive function.

Partitions :

Disk 0 :

System : 100MB NTFS,  healthy, system, Active, Primary partition
OS (C:) : 452,75 GB NTFS, Healthy, boot, page file, primary partition
HP recovery (D:) 12.91 GB NTFS, Healthy, primary partition

Disk 1 :

System : 100MB NTFS,  healthy, Active, Primary partition
OS : 931.41 GB NTFS, Healthy, Primary partition

I'm getting the missing hardware error, when I plug Disk 0 back in, it boots perfectly again.

I have created disk one by first copying the system, creating a partition and then copying OS onto it.

I've actually attempted to boot the new drive without the old one at first, no luck.

The old one still boots without the new one attached.

I haven't copied anything to something wich was assigned a letter, the new HD is unassigned.

I don't need the recovery drive, I plan to make a new backup with the HP tool. :)

 

drives.png

First off I'l post my info: Windows 7  64bit, sata to sata.
I'm using the copy my harddrive function.

Partitions :

Disk 0 :

System : 100MB NTFS,  healthy, system, Active, Primary partition
OS (C:) : 452,75 GB NTFS, Healthy, boot, page file, primary partition
HP recovery (D:) 12.91 GB NTFS, Healthy, primary partition

Disk 1 :

System : 100MB NTFS,  healthy, Active, Primary partition
OS : 931.41 GB NTFS, Healthy, Primary partition

I'm getting the missing hardware error, when I plug Disk 0 back in, it boots perfectly again.

I have created disk one by first copying the system, creating a partition and then copying OS onto it.

These statements are incompatible or are they?

 

I have created disk one by first copying the system, creating a partition and then copying OS onto it.

 

I haven't copied anything to something wich was assigned a letter, the new HD is unassigned.

What I ment was : I have first copied over the system folder, then I had to create a partition, otherwise it would overwrite the rest.

I have not assigned a drive, or did I do it wrong?

 

Edit: I think I figured out what I did wrong, I'm redoing my backup and will post an update, but I expect it to work now.

Allright, I'm out of ideas now. This is what I did:

I formatted the drive, copyed over the hidden system folder, copyed over the OS folder.

I then had both foldes + unalocated space, I disconnected the primary harddrive, booted, still got the error.

I then allocated the unallocated space to the OS partition that norton ghost created, still get the error.

Primary disk still works fine.

 

When I copyed the system partition, I selected make active and copy MBR, also allocated no drive.

When I copyed the OS partition, I selected copy MBR, also allocated no drive.

Have a read of this simple practical step by step instruction Here

Follow it to the letter and you should have a "Cloned" drive that works.

Remember you must have a validated .v2i backup available, also remember to tick the box "show hidden drives" when backing up.

It won't hurt to start again to get a good valid backup that you can use.

 

Deric

Thanks for the advice, I'm not trying to be difficult, but I don't have the option to create a giant backup. It's telling me I need over 660MB of space for the backup and I only have these 2 drives. I doubt I can put the backup on the target HD.

My primary is a 500GB drive and my new one is a 1 TB drive.

I think it is possible you have drive letter / disk signature issues. I think even though you formatted the drive, it still had the disk signature. Brian has a nice post on how to clear the mounted devices registry key of the offline system.

Try this.

 

Also what version of Ghost are you using?  I assume 15. Is it updated to SP1?


HypnoticFrog wrote:

 This is what I did:

I formatted the drive,


I still don't understand what you are doing. To format a drive you must have created a partition. You can't format unallocated space. We are saying you must not create any partitions.

 

What is the full text of the error message you see?

This is the full error I'm getting :

 

Windows failed to start. A Recent hardware or software change might be the cause. To fix the problem:

1. Insert your windows installation disc and restart your computer.
2. Choose your language settings, and then click next
3. Click "repair your computer."

Status: 0xc000000e
Info: The boot selection failed because a required device is inaccessible

 

What I mean when I say I formatted is : when I copy over system and OS, it automatically creates partitions when being copied over, partitions that aren't assigned a drive letter.

Before I start copying over system, it is unallocated space.  When I have copyed over system, the disk has a system partition and unallocated space, the unallocated space is then where I copy over OS.

Then I end up with system & OS partitions and unallocated space.

I am not creating partitions, norton ghost is doing that when copying over partitions.


HypnoticFrog wrote:

This is the full error I'm getting :

 

Windows failed to start. A Recent hardware or software change might be the cause. To fix the problem:

1. Insert your windows installation disc and restart your computer.
2. Choose your language settings, and then click next
3. Click "repair your computer."

Status: 0xc000000e
Info: The boot selection failed because a required device is inaccessible

 


OK. Have you tried doing a repair from a Win7 DVD? You have to do two repairs.

 

Do you have Ghost 15 SP1?

 

 

I have ghost 15 SP 1, I just did one repair and right now I'm on the new disk, and it's asking me for a restart, so it's looking good! :)

I am now on the new drive, everything seems fine!  Thanks alot everyone for the help! :)

Sometimes a repair is needed after using Ghost. It was more frequent prior to SP1.

Brian. Would deleting the mounted devices registry key fixed this?


redk9258 wrote:

Brian. Would deleting the mounted devices registry key fixed this?


Red,

 

No, it wouldn't. It is a BCD issue and not related to driver letters. Weird that it should have happened here with SP1.