Installed new Sata boot drive to replace IDE...

  • Thread starter Thread starter Paul S
  • Start date Start date
P

Paul S

I copied all the appropriate files from the old IDE drive using Seagate's
drive utility, but when I try to boot up directly from the new SATA drive, I
get the invalid system disk message.

However, if I put in the Windows XP setup disk (but don't boot from it) it
loads XP without any issues. Is there a timing issue, where the drive hasn't
started up yet, and that's why it's claiming it's an invalid disk? BIOS is
showing the correct drive in the primary slot, so it's not booting up to the
incorrect drive...

I tried FIXMBR and FIXBOOT from the Recovery Console, and that didn't appear
to have any effect.
 
Did you make sure the new SATA hard drive had an Active partition? The
"how-to" info for doing that should be somewhere in the Seagate info.
 
Youre lucky to have gotten that far....Most MB have either SATA or IDE
(IDE usually/only) operatable,SATA needs to be enabled and/or you need
to set the board to work with both,the BIOS has these settings,read the
owners manual..
 
I can't comment on your method of copying files, however note that you must
copy ALL files (especially hidden/system) and this must be done from outside
the OS on the disk, for example from a bootable CD OS such as UBCD4Win or
Knoppix.

Then, boot from your Windows setup CD, and allow the setup to run until the
first 'copying files' section is over, and the computer reboots. Do not
proceed any further with setup. This should restore the bootsector and
boot.ini settings. Now edit boot.ini to remove the setup option, leaving the
installed OS as the default option.
 
Paul S expressed precisely :
I copied all the appropriate files from the old IDE drive using Seagate's
drive utility, but when I try to boot up directly from the new SATA drive, I
get the invalid system disk message.

However, if I put in the Windows XP setup disk (but don't boot from it) it
loads XP without any issues. Is there a timing issue, where the drive hasn't
started up yet, and that's why it's claiming it's an invalid disk? BIOS is
showing the correct drive in the primary slot, so it's not booting up to the
incorrect drive...

I tried FIXMBR and FIXBOOT from the Recovery Console, and that didn't appear
to have any effect.
Click to expand...

If there is a delay option in the BIOS, try a setting of 20sec or so.
I did this on a Lenovo M58 with a similar problem. Afterwards I
(forcibly) added the SATA-driver to Windows, removed the delay and
changed the SATA-mode to AHCI.
 
Back
Top