Kelly,
I don’t think there is anything wrong with your hard drive. Everything points out to your problem being relate to “Direct Image.”
If you are running a clean install of Windows 2000 or XP you may try checking the event log for further details on this error and post them here.
Quote:
Originally posted by MTU Support
Error 626 Operation is to be performed on a hard drive not visible from boot-mode
|
The error message you are receiving is very specific to this type of problems. A hard drive failure will not give this message, nor will any cable related problems. Here are some possible causes and solutions from the PowerQuest web site.
Problem environment: Partition Magic,
Drive Image, Drive Copy, Server Magic.
Cause 1: This error is caused when you are trying to perform an operation on a drive that Windows sees as a fixed drive but DOS cannot detect at all. This normally occurs with Fire Wire, USB, or
PCMCIA hard drives, none of which are visible in DOS. Since
Drive Image, PartitionMagic, and ServerMagic must all reboot to DOS to perform operations on disks that have open files on them, these programs cannot perform operations involving disks that cannot be seen in DOS.
Fix: To avoid this error, make sure that all operations you perform on USB, FireWire, or
PCMCIA hard drives can be performed within Windows. In other words, if you want to create images of or resize partitions on these drives, you cannot have operating systems running on them or do anything else that would cause files to be open on them. Also, when you are creating an image of a partition that has open files on it (such as the active operating system partition), you cannot save the image file to a USB, FireWire, or
PCMCIA drive because the computer must reboot to DOS to create the image.
Before you attempt to create an image of a partition that has open files on it, make sure you have access to a different drive or partition that is visible in DOS (for example, a partition on an IDE drive) so you can save the image file to that location.
Cause 2: This error may also be caused if a drive is jumpered incorrectly or is not detected in the BIOS.
Fix 2: Consult your drive's documentation to make sure that the drive is jumpered correctly, and then go into your BIOS Setup program to verify that the BIOS is correctly detecting the drive.
NOTE: Windows is capable of seeing drives even if the BIOS has not detected them; therefore, just because a drive is visible in Windows does not mean that the BIOS has correctly detected the drive.
(My comment: you may have lost your BIOS settings, this can happen without you knowing it. I would check here first)
Cause 3: If this error is reported when resizing a partition on a large RAID drive in boot mode, the problem is that the partition is on a slave drive on the RAID controller and is detected as drive 3 in the chain. Drives 0, 1, and 2 are left undetected when the drives post.
Fix 3: Change the affected RAID drive to master so the system can detect it as drive 0.
Good luck,
Jon