Salta al contenuto principale

Cloning - Original won't boot but copy will

Thread needs solution

New here, so I hope I am posting in the right place.

I used Acronis to clone a system drive from a specialized musician product (OS is Windows XP) connected by USB to make a clone copy for backup. The cloned copy works perfectly in my CAVS machine and boots with no problem.

But puzzlingly, the process appears to have corrupted my original hard drive for the CAVS. When I use the original from my CAVS I get an error message "NTLDR is missing".

If I put the original back on to my laptop via USB so I can look at it, the system partition won't read and shows zero bytes under the properties command. The second partition for music data is perfect.

Why would cloning keep the original from booting but allow the new copy to boot?

Fortunately I didn't lose both drives. I am afraid to try this again until I learn more about it

Shouldn't Acronis be able to clone a disk from one USB connection to a disk on another USB connection using a laptop to do the work? My CAVS machine has no capability to do the job on the CAVS.

Smoky

0 Users found this helpful

Hello Smoky,

Yes, you're in the right place, I will assist you to resolve this situation.

It looks like your boot partition has been corrupted during the data transfer.

Shouldn't Acronis be able to clone a disk from one USB connection to a disk on another USB connection using a laptop to do the work? My CAVS machine has no capability to do the job on the CAVS.

Yes, the process completes successfully in most cases. But when you're cloning from USB to USB, the drive may not boot as when you plug it back as the internal one. That's why we always recommend to clone between the same internal interfaces (when both drives are plugged to the same SATA controller, for example).

Let's do the following in your case: first of all, check whether boot issue is caused by particular loader files missing by fixing them. The cause of the error about NTLoader is missing is that:

  • NTLDR or Ntdetect.com files are not present on the active partition:
    • NTLDR is the boot loader for all Windows NT operating systems, including Windows 2000, Windows 2000 Server, Windows XP and Windows Server 2003
    • Ntdetect.com is responsible for detecting hardware necessary to start the operating system;
  • Boot.ini file is corrupt or points to incorrect partition

NTLDR or Ntdetect.com files are not present on the active partition

  1. Start the machine from Windows installation CD;

    (!) You may need to change the boot order in the system BIOS to let the machine boot from CD.

  2. At the Welcome to Setup screen, press R to repair the Windows installation using Recovery Console;
  3. Type the number that corresponds to the Windows installation that you want to repair, and then press Enter. E.g., type 1, and then press Enter;
  4. Type the Administrator password, and then press Enter;
  5. Type the following commands:

    cd..
    dir /p

  6. Check if NTLDR and Ntdetect.com files are listed in the root of the drive. If the files are present, then please proceed to Boot.ini file is corrupt or points to incorrect partition. If these files are not present, proceed with the steps below;
  7. Type map and then press Enter;
  8. Note the drive letter that is assigned to the CD\DVD-ROM drive that contains the Windows CD;
  9. Type the following commands:

    copy [drive]:\i386\ntldr [letter]:\
    copy [drive]:\i386\ntdetect.com [letter]:\

    where [drive] is the drive letter of your CD\DVD-ROM drive and [letter] is a letter of the drive Windows is installed on.

    Press Enter after you issue each of the two commands.

    If you are prompted to overwrite the file, type y, and then press Enter.

  10. Reboot the machine.

Windows should be bootable now. If it is not, please proceed to Boot.ini file is corrupt or points to incorrect partition.

Boot.ini file is corrupt or points to incorrect partition

  1. Start the machine from Windows installation CD;

    (!) You may need to change the boot order in the system BIOS to let the machine boot from CD

  2. At the Welcome to Setup screen, press R to repair the Windows installation using Recovery Console;
  3. Type the Administrator password, and then press Enter;
  4. Issue the following command:

    Bootcfg /rebuild

    This command will find the existing Windows installations and add the necessary strings to boot.ini.

  5. At Enter Load identifier enter any name for the found operating system;
  6. When you are prompted for OS Load options type fastdetect and press Enter;
  7. Reboot the machine and choose the just added operating system from boot menu.

Windows should be bootable now. You can also edit the boot.ini file manually from Windows as described in the Microsoft Knowledge Base Article 289002.The instructions were taken from this article.

If this still does no solve the boot issue, I would recommend you to create a backup archive of your working HDD, and then restore it back to the problem drive. The full description of the process is available in Chapter 6 of this User's Guide.

Please let me know whether it resolves the issue you experience. Also, do not hesitate ot ask if something is not clear for you.

Regards,