Solved: Infinite reboot issue

Status
This thread has been Locked and is not open to further replies. Please start a New Thread if you're having a similar issue. View our Welcome Guide to learn how to use this site.

RBurger

Thread Starter
Joined
Jan 2, 2011
Messages
3
hola.

Yesterday I cloned my old SATA hard drive (200 GB) to new SATA hard drive (2 TB) - the image had Windows XP Professional installed on it - before this i had dual-booting set up, so i could boot into either XP or Windows 7 (the latter is installed on a partition on another hard drive).

Now with this new hard drive installed in place of the old one, for some reason i'm getting infinite reboot loop even before being presented with the boot manager window (with OS selections), i.e. I am still able to get into the BIOS if I want to, but it doesn't get much further... in my BIOS settings I have the new hard drive (with XP) listed first in the drive sequence. I've even unchecked the 'Automatically restart' checkbox in System Properties -> Advanced -> Startup and Recovery -> System failure, without any change in observed behaviour.

But, curiously enough if i have Hiren's Boot CD in my DVD drive and and boot from it, and then choose 'Boot from Hard Drive', it all works as before (I get shown 'XP' or 'Windows 7' options, both work).

Any ideas as to what I should/can try? I had a brief look at boot.ini on the Windows XP partition and bcdedit settings on Windows 7 partition and didn't see anything obviously wrong...

thanks,
Greg
 

RBurger

Thread Starter
Joined
Jan 2, 2011
Messages
3
Boot.ini file contents on the older 200 GB hard drive and newer 2 TB hard drive is identical, and both files are marked hidden and system.

Another thing I'm trying to understand, in my setup, on boot-up after I get the option to enter Setup and before any OS selection window is shown, is it Windows 7 bootmgr that's being accessed or XP boot.ini? Both seem to be located on the first partition of the first drive... the first partition of the second drive isn't marked as active, nor does it have any boot.ini/bootmgr files, which is why this auto-reboot loop almost looks like wrong drive is being used... although even then, shouldn't there be a fallback onto the other drive configured in BIOS.
 

RBurger

Thread Starter
Joined
Jan 2, 2011
Messages
3
After re-running the cloning, this time using Norton Ghost with disk cloning (as opposed to partition cloning), the problem seem to have disappeared. The initial clone attempt was done using Ghost4Linux's 'Click'n'Clone' method... perhaps the fact that source drive was 200 GB and target 2 TB caused some issues with boot sector/MBR when G4L bit-by-bit clone option was used.
 
Status
This thread has been Locked and is not open to further replies. Please start a New Thread if you're having a similar issue. View our Welcome Guide to learn how to use this site.

Users Who Are Viewing This Thread (Users: 0, Guests: 1)

As Seen On
As Seen On...

Welcome to Tech Support Guy!

Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations.

If you're not already familiar with forums, watch our Welcome Guide to get started.

Join over 807,865 other people just like you!

Latest posts

Members online

Top