Neither my original or new drive will boot into Windows XP SP2.
Instead I get an error screen (BSOD) "Windows could not start because of a computer disk hardware configuration problem.
Could not read from the selected boot disk. Check boot path and disk hardware.
I was using the Acronis True Image Echo Workstation software to clone a WD 36GB Raptor SATA drive to a new Maxtor 750GB SATA drive. This was at Seagate's recommendation because their MaxBlast5 software that came with the drive didn't "see" the new drive to allow software use.
The Acronis software was a download from their site which was then installed and rebooted to a DOS like environment to do the cloning. It did the cloning and I unplugged the old SATA disk, the WD, and tried to boot. I got a BSOD with an error message - not the same message I have now - I think it said, "Error: Failed to successfully scan disks for Windows Installations. This error may be caused by a corrupt file system.. Use CHKDSK to detect any disk errors.
I booted the PC the first time with only one HDD connected.
- First time with only new drive no USB, Flash drives, secondary drives, etc
- Second time with only new drive connected - still nothing else
When I booted the machine it would not boot into Windows (XP SP2). I booted with the Windows XP CD and it did not detect any Windows installation so only offered a new install or the Recovery Console. It did not offer to fix an existing installation.
When looking at the HDD from the Recovery Console, I could see the entire disk tree in the C; drive and it appears fine
From the Recovery Console I ran: FIXMBR C:, then FIXBOOT C:, then Copy NTLDR C:, then Copy NTDETECT C:,, then BOOTCFG /REBUILD which failed saying "Error: Failed to successfully scan disks for Windows Installations. This error may be caused by a corrupt file system which would prevent Bootcfg from successfully scanning. Use CHKDSK to detect any disk errors. I ran CHKDSK /R which required running first as /F and then /P
I ran the same commands with each HDD, the old and new - with only (again) one disk in the machine. Both disks seem perfectly readable from the Recovery Console.
Running BOOTCFG with the switches /Add /Scan and /Rebuild returned an error "Failed to successfully scan disks for Windows installations. This error may be caused by a corrupt file system....use CHKDSK to detect disk errors
I also copied an XPsp2 boot.ini and ntoskrnl.exe files into C:\ and C:\WINNT\System32 respectively from another working machine.
Any ideas? anyone? I'm suspecting one of the partition or bootloader files is missing or corrupted and a small change will make the difference.
Are there utilities that can look for these kinds of problems? a file I (still) need to copy? or something to edit
I'm trying to learn as well as fix this headache I've created without a full reload.
BTW, the Windows disk also doesn't "see" the installation because it doesn't give the "repair" choice when reloading Windows from the Upgrade CD.
Acronis is out of ideas. They think the problem may have been caused by cloning an Upgrade version of XP from W2000 instead of a full new install of XP.
Thank you......
Instead I get an error screen (BSOD) "Windows could not start because of a computer disk hardware configuration problem.
Could not read from the selected boot disk. Check boot path and disk hardware.
I was using the Acronis True Image Echo Workstation software to clone a WD 36GB Raptor SATA drive to a new Maxtor 750GB SATA drive. This was at Seagate's recommendation because their MaxBlast5 software that came with the drive didn't "see" the new drive to allow software use.
The Acronis software was a download from their site which was then installed and rebooted to a DOS like environment to do the cloning. It did the cloning and I unplugged the old SATA disk, the WD, and tried to boot. I got a BSOD with an error message - not the same message I have now - I think it said, "Error: Failed to successfully scan disks for Windows Installations. This error may be caused by a corrupt file system.. Use CHKDSK to detect any disk errors.
I booted the PC the first time with only one HDD connected.
- First time with only new drive no USB, Flash drives, secondary drives, etc
- Second time with only new drive connected - still nothing else
When I booted the machine it would not boot into Windows (XP SP2). I booted with the Windows XP CD and it did not detect any Windows installation so only offered a new install or the Recovery Console. It did not offer to fix an existing installation.
When looking at the HDD from the Recovery Console, I could see the entire disk tree in the C; drive and it appears fine
From the Recovery Console I ran: FIXMBR C:, then FIXBOOT C:, then Copy NTLDR C:, then Copy NTDETECT C:,, then BOOTCFG /REBUILD which failed saying "Error: Failed to successfully scan disks for Windows Installations. This error may be caused by a corrupt file system which would prevent Bootcfg from successfully scanning. Use CHKDSK to detect any disk errors. I ran CHKDSK /R which required running first as /F and then /P
I ran the same commands with each HDD, the old and new - with only (again) one disk in the machine. Both disks seem perfectly readable from the Recovery Console.
Running BOOTCFG with the switches /Add /Scan and /Rebuild returned an error "Failed to successfully scan disks for Windows installations. This error may be caused by a corrupt file system....use CHKDSK to detect disk errors
I also copied an XPsp2 boot.ini and ntoskrnl.exe files into C:\ and C:\WINNT\System32 respectively from another working machine.
Any ideas? anyone? I'm suspecting one of the partition or bootloader files is missing or corrupted and a small change will make the difference.
Are there utilities that can look for these kinds of problems? a file I (still) need to copy? or something to edit
I'm trying to learn as well as fix this headache I've created without a full reload.
BTW, the Windows disk also doesn't "see" the installation because it doesn't give the "repair" choice when reloading Windows from the Upgrade CD.
Acronis is out of ideas. They think the problem may have been caused by cloning an Upgrade version of XP from W2000 instead of a full new install of XP.
Thank you......