August 1st, 2014, 2:34
August 1st, 2014, 14:20
August 1st, 2014, 15:07
August 1st, 2014, 15:12
August 1st, 2014, 23:22
August 2nd, 2014, 0:05
August 2nd, 2014, 4:00
August 2nd, 2014, 13:26
August 2nd, 2014, 13:27
labtech wrote:Post a picture of the drive being detected in device manager.
August 2nd, 2014, 13:39
Frozwire wrote:It could be a possible head issue or an insufficient 12V power on the bridge board interface.
August 2nd, 2014, 13:40
dick wrote:Hi! You could do a simple test by connecting a spare drive to the bridge board. Initialize and format it. Then write data to it and check to prove the board and usb interface are working. One thing to note is sometimes certain makes and drive models seem to require more power (amperage) than the power pack can provide. You need to methodically check this.
August 2nd, 2014, 18:03
unhappy_wd_user wrote:labtech wrote:Post a picture of the drive being detected in device manager.
Hi, you can refer to my previous post with attachment. Thanks!
unhappy_wd_user wrote:If it is the heads issue as you mentioned, then why is the HDD detectable when I connect it without the bridge board?
August 2nd, 2014, 23:08
labtech wrote:The pic posted looks like drive is connected via the bridge.
Wanted to see what the drive shows up connected in Device Manager connected without the bridge per your question/wonder above.
August 3rd, 2014, 1:30
August 3rd, 2014, 9:38
labtech wrote:You are misunderstanding the purpose of the test. Connect the drive via SATA port directly to your desktop. This way we can identify whether your drive works properly or not, hence rendering the bridge as the culprit.
August 3rd, 2014, 23:23
mr_spokk wrote:labtech wrote:You are misunderstanding the purpose of the test. Connect the drive via SATA port directly to your desktop. This way we can identify whether your drive works properly or not, hence rendering the bridge as the culprit.
Precisely, as it is now only the usb chip on the usb-sata cable is identified.
August 4th, 2014, 6:14
unhappy_wd_user wrote:mr_spokk wrote:labtech wrote:You are misunderstanding the purpose of the test. Connect the drive via SATA port directly to your desktop. This way we can identify whether your drive works properly or not, hence rendering the bridge as the culprit.
Precisely, as it is now only the usb chip on the usb-sata cable is identified.
I'm sorry. I think I've misunderstood your meaning of "The pic posted looks like drive is connected via the bridge.". I was thinking "by bridge", you meant the bridge board that comes with the HDD.
Now I catch your meaning, the bridge means the bridge on the SATA to USB cable? I didn't know there are bridge board on the SATA to USB cable as well.
Anyway, I did a test to connect my HDD to my MOBO via SATA port (hoped this was what you wanted me to test) and it doesn't get detected no matter what sequence I went through (power on then connect or vice versa). Nothing in the Device Manager or whatsoever.
Then I do the same test on another working HDD and nothing was detected as well.
Could it be because my desktop is an old one (bought it around 8 to 9 years ago with 256MB RAM!!)?
August 4th, 2014, 8:09
mr_spokk wrote:If the drive is working you should see atleast the right model in Bios.
But the importent question is: how does the drive behaive when you plug it in to the motherboard, Does it spin? Does it spin up and after a Little while spin down?
August 4th, 2014, 9:09
unhappy_wd_user wrote:mr_spokk wrote:If the drive is working you should see atleast the right model in Bios.
But the importent question is: how does the drive behaive when you plug it in to the motherboard, Does it spin? Does it spin up and after a Little while spin down?
You mean I should be able to see the HDD model in the BIOS eventhough it is clearly not detected in Device Manager?
The drive behave as per what I mentioned before. Nothing out of the ordinary.
unhappy_wd_user wrote:It is like it came alive, then without 10-15 seconds, it die down and then it sort of 'retry' by spinning again and yet again within 10-15 seconds, it die down completely like it went to idle.
Is this because of insufficient power to retain the disc activities, or it is normal?
August 4th, 2014, 9:59
mr_spokk wrote:This behaviour is not in the "ordirnary"
Yes, IF the drive is working good enough to reach it's SA...
Powered by phpBB © phpBB Group.