Dear Friends,

I am installed Windows XP and Fedora 17 in 80GB SATA hard disk.
I disk cloned to another hard disk 320GB SATA HDD using Clonezilla(Disk to Disk Method)

Now in 320GB hard disk Fedora Linux working fine. But Windows XP wont boot.

when enter Windows XP in GRUB menu the system wont boot.

So I used fixboot and fixmbr using windows xp repair mode

But windows XP not boot.

What is the mistake.


Please reply.

Thanks

A.Kannan

Hi there,

I've never used Clonezilla, only know it by name, so maybe what I'm asking is pointless:

* Did you clone each partition separately, or the whole disk with all partitions included?
* What did you do about the extra space? Did you resize partitions, or create another one?

I know that Windows is critical about cloning partitions only, but cloning the entire disk usually works fine.

Which means what exactly? Just a blank screen? An error message? If so, what does it say? Does the system stall in GRUB already, or do you see the splash screen of XP?

That should've resurrected Windows, but killed GRUB instead. I'm amazed.

[X] Doc CPU

Sir,

thanks for your reply. Actually i used disk to disk option(entire disk). Grub loaded successfully and also fedora 17 working fine. But I enter windows xp in grub menu the system display blinking cursor.

you are aware that fedora 17 is dead and unsupported
and so is fedora 18
only fedora 19 and the current fedora 20 are supported

please install fedora 20
you really DO need to stay current

You cloned sda to sdb windows maybe thinking the drive is sda & fedora is looking for windows on sdb. Windows most likely (Hd0,1) & is now (Hd1,1)
This is my theory.
Check your fstab & windows drive entry, it may be as simple as changing drive # in grub or drve mapping

i there,

interesting thought, but why?? Of course, during the cloning process, both HDDs must be attached at the same time; presumaby the new 320G via USB. But I had assumed that the smaller 80G drive was disconnected aremoved after that (though that wasn't mentioned), which would automatically make the 320G drive become sda again and eveything should work.

But yes, if the OP left both HDDs connected at the same time, that may be an issue.

[X] Doc CPU