terryd75 :
Is it an external drive? In some sort of enclosure? Is it USB? Have you tried connecting it with the computer already turned on? In ther words, wait until the computer is fully booted up, then try connecting it via USB? Sometimies, USB can have conflicts during boot process. If you've already tried that, then, tell us more about how you are connecting this drive? In other words, have you installed it into the computer and have it connected via SATA? need more info.....
Terry, it is a Cavalry external drive in an enclosure and normally would connect via USB to my PC, but when I power it on the external light displays and I hear a faint high pitch "electrical" noise but the drive is definitely NOT spinning. There aren't many internal board components so I assume the power brick is not supplying sufficient power or capacitor or other component failed....
That said, I took the drive out of the Cavalry and tried to install directly inside my PC to test it and also to get the data off to be safe. When I connect the internal PC power cable to the SATA Maxtor 6L200M0 (200G) it does spin up so was very happy the drive seemed to be working and looking forward to getting it setup inside my PC.
I haven't messed with HDD's since the days of IDE where you were required to move jumpers on the drives to set master/slave when using more than one inside your computer. From what I read about how the SATA interface works, each interface (SATA0, SATA1, etc) is independent and no jumpers are required to determine master/slave. However, when I connect this drive and turn on the PC, it gets through BIOS, displays a bar saying windows VISTA is loading, and then screen goes black and system hangs.
I verified in bios that the system is seeing the second drive. I also set the boot order to ensure the original drive is still the boot drive. Lastly as noted earlier, the original drive is a 300+GB and shows correct size when OS load. I only mention the last part as I also read that some older BIOS may have difficulty supporting drives over 32 Gig and could freeze or display weird sizes in the OS once it loads. So..... that's where I'm at and quite honestly not sure what to do at this point. Hopefully the additional details I provide add clarity to the situation. Looking forward to any suggestions and guidance. Thanks! Mike