Failure to detect new internal HDD connected to SATA/USB connector to laptops

kevin138868

Prominent
Nov 12, 2017
3
0
510
Hi,

I bought a brand new Seagate Barracuda 2.5in 1TB (ST1000LM048) internal HDD to clone & replace my failing 500 GB HDD on my Dell Inspiron 5420 that is running Win10.

I connected the new HDD via a new SATA/USB2.0 Y - connector to my laptop. The laptop failed to detect the HDD neither in Disk Management nor Device Manager. I have tried connecting the HDD to all the 3 USB 3.0 ports either using single USB port or using 2 USB ports. The HDD spins & get heated up but the laptop just would not detect it.

Occasionally, the Device Manager would report "Unknown USB device (Device descriptor request failed)" but would remain silent when I plug in the HDD most of the times. At times, there would be RED LED indicator lighted up on the SATA/USB connector. According to the spec, it suppose to emit Blue light when power on & Orange light for HDD access but none of those happened.

I have tried connecting the same HDD to my Dell Inspiron 15 3559 (2 USB 2.0 + 1 USB 3.0 ports) also running Win10 with the same result.

Does anyone have an idea what could be wrong? I have spent 2 days testing & updating some of the device drivers on the Inspiron 15 3559 along the way but nothing change.

Would appreciate your kind help!!!
 
It's conceivable the Seagate HDD is defective; has that possibility occurred to you?

Also, we've found many of those SATA-to-USB cable adapters are quite erratic in operation. We generally prefer to use a USB external enclosure to house a drive when it's connected as a USB external device.

I'm assuming both your laptops properly function excepting the problem with the secondary HDD.

Can you get your hands on a PC that you can use to internally-install the Seagate as a secondary drive to determine if the system detects the drive and if so to test it with Seagate's SeaTools diagnostic program?
 

kevin138868

Prominent
Nov 12, 2017
3
0
510


Hi ArtPog,

You are right that the cable is the issue. Got it replaced by an external HDD encasement & was able to access the new HDD w/o issue. Thanks for your advice.:)