miamiair wrote:I noticed the blue light was not steady, but flashing
Queso wrote:Is it flashing randomly or is there a pattern?
Have you checked Device Manager to see if it shows up there, or if the controller is showing up?
miamiair wrote:Queso wrote:Is it flashing randomly or is there a pattern?
Have you checked Device Manager to see if it shows up there, or if the controller is showing up?
It shows as an unspecified device.
Cadet57 wrote:miamiair wrote:Queso wrote:Is it flashing randomly or is there a pattern?
Have you checked Device Manager to see if it shows up there, or if the controller is showing up?
It shows as an unspecified device.
Driver issue?
Queso wrote:Model number?
Queso wrote:Do you have another 'puter you can connect it to temporarily to help us narrow it down? I'm thinking this may be a problem with the controller in the external drive case.
miamiair wrote:Queso wrote:Do you have another 'puter you can connect it to temporarily to help us narrow it down? I'm thinking this may be a problem with the controller in the external drive case.
I can bring it to work tomorrow or try connecting it to my lap top.
Problem:
Code 10 status is displayed in Windows XP Device Manager for a USB or FireWire device.
Cause:
The device is not recognized or there is a problem with the device drivers. Commonly, the error message displayed will be similar to the following:
"This device is either not present, not working properly, or does not have all the drivers installed. (Code 10)
Solution:
Upgrade the device drivers for this device. To resolve this error code, make sure the device is connected to the computer correctly. For example, make sure all cables are plugged in fully and that all adapter cards are properly seated. Follow the suggested solution button provided by Windows and update the device driver. It may be possible to remove the device and redetect it using the Add New Hardware wizard.
Note: If the solution above does not help, the drive may have failed. It is recommended that you try to connect the drive to a second PC running Windows 2000 or XP. If the same error message is shown in the Device Manager of the second PC as well, the drive has failed and needs to be replaced.
AndesSMF wrote:Are these those 'book' drives?
AndesSMF wrote:Oh, crap...
The only thing I would suggest, and it should work just fine, is to remove the drives from their enclosure and then hook them up to a desktop computer. Then you should be able to recover everything just fine.
How you can remove the drive, IDK.
IFEMaster wrote:I had the exact same thing happen with the exact drive. It ended up being the logic board in the enclosure. I bought a new SATA2 enclosure for $20 and the drive has worked perfectly since.
AndesSMF wrote:IFEMaster wrote:I had the exact same thing happen with the exact drive. It ended up being the logic board in the enclosure. I bought a new SATA2 enclosure for $20 and the drive has worked perfectly since.
Wouldn't doubt it.
Most drives, even after they crash, remain quite readable.
What often happens is that the boot sector does not allow the drive to mount, but reconnecting the drive to another channel has always worked for me.
miamiair wrote:I have an AOG, so I am back at the office.
I brought it with me. The computer gives you all the flags in the lower right hand corner, but when I go to My Computer, it doesn't show up.