asked on

Help cloning a SCSI to IDE and changing boot.ini on Win2K server

I've got a Windows 2000 Server which has a single SCSI hard drive which is failing. Upon boot up the server displays a blue screen wtih "inaccessible boot device". Clearly a failing HD. The SCSI drive is dynamic and I was able to use Ghost 11 to capture a full image of the drive even with the bad sectors. I used the "force clone" and "igrnore bad cluster" options in ghost. Now, I've dumped that image onto a standard IDE drive and connected the drive direclty to the IDE controller which is built into the motherboard of the server. The server actually begins to boot up and the windows progress bar that appears on the bottom begins to move across the screen. However, about 10 seconds later the server but reboots itself.

This is the original boot.ini

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Server" /fastdetect

Do you think this is because I've gone from SCSI to IDE, is it a problem with the boot.ini, or is it more likely that the image I took with ghost is just too corrupted due to all the bad sector to perfrom properly. The only difference with the IDE drive is that the system just reboots without any blue screen where as with the SCSI drive it says "inaccessible boot" .

Any ideas?

ASKER CERTIFIED SOLUTION

Henrik Johansson

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

djadambomb

ASKER

You were correct the image was too corrupt. But I was able to run scan disk and replace the registry file from a backup file. After that the IDE drive booted up with the full OS Intact!