new HD boot issues!!

January 17, 2009 at 12:02:05
Specs: Windows XP, amd 64bit 3k
Hey guys.

I recently bought a new Sata 320gb internal drive to replace my 60gb sata internal.
I wanted to start clean on the new drive, so I partition it at 20gb(for OS) and 300gb.

Installed the OS on the 20gb partition and everything seems okay.

I wanted to copy some of the media/docs from my old drive before removing it, so I left it installed during the OS install.

After copying stuff over..I removed the drive to find that I could not boot to my new drive by itself. If I install the old HD and select the OS on the new drive, it works fine. So, seems like the new drive lacks a master boot record, but im not sure how windows formats initially.

Is there any way to salvage this, or will i need to reformat the new drive (without the old HD installed) and reinstall the OS?


Thanks in advance.


See More: new HD boot issues!!

Report •


#1
January 17, 2009 at 12:20:00
Go into the BIOS and make sure that it is set to boot from the internal hard drive first. You probably do not have to reinstall XP on the new drive. And don't leave the old drive installed when you try to boot up to the new drive. If you still have problems after checking the boot order in the BIOS, then boot up to the XP CD and run fixboot and fixmbr from the Recovery Console.

Report •

#2
January 17, 2009 at 12:31:03
The old HD was internal as well, and the boot order is CD-ROM, HD. And in the subsection, I selected the new physical disk as the primary.

The problems occur when I remove the old drive and boot up with the new one only.
It says there's no system disk which lead me to believe that when windows formatted, it didnt create an MBR on the new drive since there was already a Windows install present on the old drive.

As far as fixboot and fixmbr, is there anything i need to know so i wont screw something up more?

I ran bootcfg earlier in there and set a new boot but to no avail.

Thanks again!


Report •

#3
January 17, 2009 at 13:30:48
I don't think that running fixboot and
fixmbr will screw things up more, but there's never any guarantee. It might not help, but I think it's worth a try.

Report •

Related Solutions


Ask Question