Skip to main content

clone the systempartition, what happen with the MBR?

Thread needs solution

if i clone my systempartition C: to a new disk
and want to boot from the new disk..

the message searchin the bootrecord comes up,
and so i think, disk direktor hasn't clne the MBR

I'm right?

can I create the bootrecord with the tools from win XP?

0 Users found this helpful

Ralph:

If you used Disk Director to copy a partition to a new, blank hard disk then the only information written to the first sector would be a partition table. You would need to use your XP tools to write the MBR boot code to this new disk. From the recovery console, use fixmbr.

www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/bootcons_fixmbr.mspx

hi Mark
thank you for the reponse!

I asked a friend about my problem and he said, that i should take image true...

do you have any experience with image true?
You can't move a single partition, must must move the hole disk...
so i go on... I started yesterday in der evening an today in the morning, it stand on 25% on the fourst partition..
and now at 8:00 pm, it standy by 27%....

so I think about, I shoud interrupt the process,
but what will be happens...
do you have an idea? or should I waiting?

Ralph:

Yes, I use True Image. You are correct about cloning - a clone will make a copy of the entire disk including all partitions. If you only want certain partitions then you need to make a backup of the desired partition(s), which produces an image file. You then restore this image file to a new disk.

Something is wrong if your clone operation is taking so long. 1 GB/minute is a more reasonable time estimate. One explanation might be bad sectors on the disk. You could try running chkdsk /r X: where X: is the drive letter of the partition being checked. Do this on the disk before making a clone or before making a backup image.

You may want to wait until tomorrow morning to see if any further progress has been made. If not, I would stop the operation, check the source disk for errors, and then try again.