WD My passport essential not detecting after power surge on hub port

Hi

I have extrernal WD My passport essential SE 1 TB hard disk. I have been using this HD for past 10 months. One day I connected this HD to my friend's desktop front USB port and it gave me "power surge on hub port-------" error, after that this HD is undetectable on any PC/Laptop (not in device manager, not in BIOS). The hard disk spins up, LED blinks for a while and then remains stable. There is not any weird noise from hard disk. I opened the enclosure and observed the PCB, it has no burn marks.
I want to recover some of the data from hard disk. Please someone help me.
My hard disk details are as follows.

WD P/N : WD10TMVW-11ZSMS5
DCM : HHMT2BBN
DCX : XZ55S77M9
WWN: 50014EE159BAAEE0
PCB : 2060-771814-001 REV P1

Regards,
Anzar
21 answers Last reply
More about passport essential detecting power surge port
  1. Get the disk out of the enclosure and connect it directly to a SATA port of a PC. You may be lucky and only the usb-to-sata is dead.
  2. This drive is probably encrypted. In any case the USB-SATA bridge is integrated onto the HDD PCB.

    http://farm8.staticflickr.com/7011/6440668801_72d479ed51_z.jpg
  3. Hi Guys,

    Yes, this device is encrypted on hardware level.
    Can you tell me which component to check on the PCB using Multimeter?
  4. Since the drive spins up, then the HDD related electronics is probably OK. This means that the problem is either an internal one, or perhaps there is a problem with the USB-SATA bridge electronics.

    If you decide to replace the PCB, then you will need to transfer at least one (U12), maybe two (U14), serial EEPROM chips, or their contents, from patient to donor.

    One possibility is that there may be an open circuit in one or more of the USB data pins. Many WD users are reporting physical connection problems with the USB connector. You could try a USB 2.0 cable instead of USB 3.0.

    You could also see whether Microsoft's UVCView utility can detect the USB-SATA bridge chip:
    http://www.users.on.net/~fzabkar/USB_IDs/UVCView.x86.exe
  5. Thanks for the reply.
    I tried UVCView already, device is not showing in that.

    I'll try different cable, and also go for PCB swap if necessary.
  6. fzabkar said:
    Since the drive spins up, then the HDD related electronics is probably OK. This means that the problem is either an internal one, or perhaps there is a problem with the USB-SATA bridge electronics.

    If you decide to replace the PCB, then you will need to transfer at least one (U12), maybe two (U14), serial EEPROM chips, or their contents, from patient to donor.

    One possibility is that there may be an open circuit in one or more of the USB data pins. Many WD users are reporting physical connection problems with the USB connector. You could try a USB 2.0 cable instead of USB 3.0.

    You could also see whether Microsoft's UVCView utility can detect the USB-SATA bridge chip:
    http://www.users.on.net/~fzabkar/USB_IDs/UVCView.x86.exe


    hi, below is my uvc report can you please guide me what to do next... my device is continuously blinking and its not showing anything...

    ---===>Device Information<===---
    English product name: "My Passport 0740"

    ConnectionStatus:
    Current Config Value: 0x01 -> Device Bus Speed: High
    Device Address: 0x03
    Open Pipes: 2

    ===>Endpoint Descriptor<===
    bLength: 0x07
    bDescriptorType: 0x05
    bEndpointAddress: 0x81 -> Direction: IN - EndpointID: 1
    bmAttributes: 0x02 -> Bulk Transfer Type
    wMaxPacketSize: 0x0200 = 0x200 max bytes
    bInterval: 0x00

    ===>Endpoint Descriptor<===
    bLength: 0x07
    bDescriptorType: 0x05
    bEndpointAddress: 0x02 -> Direction: OUT - EndpointID: 2
    bmAttributes: 0x02 -> Bulk Transfer Type
    wMaxPacketSize: 0x0200 = 0x200 max bytes
    bInterval: 0x00

    ===>Device Descriptor<===
    bLength: 0x12
    bDescriptorType: 0x01
    bcdUSB: 0x0210
    bDeviceClass: 0x00 -> This is an Interface Class Defined Device
    bDeviceSubClass: 0x00
    bDeviceProtocol: 0x00
    bMaxPacketSize0: 0x40 = (64) Bytes
    idVendor: 0x1058 = Western Digital Technologies, Inc.
    idProduct: 0x0740
    bcdDevice: 0x1019
    iManufacturer: 0x01
    English (United States) "Western Digital"
    iProduct: 0x02
    English (United States) "My Passport 0740"
    iSerialNumber: 0x05
    *!*ERROR: no String Descriptor for index 5!
    bNumConfigurations: 0x01

    ===>Configuration Descriptor<===
    bLength: 0x09
    bDescriptorType: 0x02
    wTotalLength: 0x0020 -> Validated
    bNumInterfaces: 0x01
    bConfigurationValue: 0x01
    iConfiguration: 0x04
    *!*ERROR: no String Descriptor for index 4!
    bmAttributes: 0x80 -> Bus Powered
    MaxPower: 0xFA = 500 mA

    ===>Interface Descriptor<===
    bLength: 0x09
    bDescriptorType: 0x04
    bInterfaceNumber: 0x00
    bAlternateSetting: 0x00
    bNumEndpoints: 0x02
    bInterfaceClass: 0x08 -> This is a Mass Storage USB Device Interface Class
    bInterfaceSubClass: 0x06
    bInterfaceProtocol: 0x50
    iInterface: 0x06
    *!*ERROR: no String Descriptor for index 6!

    ===>Endpoint Descriptor<===
    bLength: 0x07
    bDescriptorType: 0x05
    bEndpointAddress: 0x81 -> Direction: IN - EndpointID: 1
    bmAttributes: 0x02 -> Bulk Transfer Type
    wMaxPacketSize: 0x0200 = 0x200 max bytes
    bInterval: 0x00

    ===>Endpoint Descriptor<===
    bLength: 0x07
    bDescriptorType: 0x05
    bEndpointAddress: 0x02 -> Direction: OUT - EndpointID: 2
    bmAttributes: 0x02 -> Bulk Transfer Type
    wMaxPacketSize: 0x0200 = 0x200 max bytes
    bInterval: 0x00
  7. It seems like your PCB is fine. When PCB is damaged, you will not hear any sound from PCB or maybe a little click. You can try of course one of hdd suppliers, but it is not cheap http://www.harddrivesforsale.com/wd10tmvw-11zsms5-1.html Also your hard drive has encryption on it, most of WD passport hard drives do. I would actually recommend you taking it to data recovery place. Make a research and go to the one with good reviews. In case data is not that important, create RMA with WDC they will replace it for you, no questions asked. http://support.wdc.com/warranty/index_end.asp?lang=en
  8. hi there my 2.5 externel drive log is that. what can i do?where is the failure

    ---===>Device Information<===---
    English product name: "Elements 10A2"

    ConnectionStatus:
    Current Config Value: 0x01 -> Device Bus Speed: Unknown
    Device Address: 0x02
    Open Pipes: 2

    ===>Endpoint Descriptor<===
    bLength: 0x07
    bDescriptorType: 0x05
    bEndpointAddress: 0x83 -> Direction: IN - EndpointID: 3
    bmAttributes: 0x02 -> Bulk Transfer Type
    wMaxPacketSize: 0x0400 = 0x00 max bytes
    bInterval: 0x00

    ===>Endpoint Descriptor<===
    bLength: 0x07
    bDescriptorType: 0x05
    bEndpointAddress: 0x0A -> Direction: OUT - EndpointID: 10
    bmAttributes: 0x02 -> Bulk Transfer Type
    wMaxPacketSize: 0x0400 = 0x00 max bytes
    bInterval: 0x00

    ===>Device Descriptor<===
    bLength: 0x12
    bDescriptorType: 0x01
    bcdUSB: 0x0300
    bDeviceClass: 0x00 -> This is an Interface Class Defined Device
    bDeviceSubClass: 0x00
    bDeviceProtocol: 0x00
    bMaxPacketSize0: 0x09 = (9) Bytes
    *!*ERROR: High Speed Devices require bMaxPacketSize0 = 64
    idVendor: 0x1058 = Western Digital Technologies, Inc.
    idProduct: 0x10A2
    bcdDevice: 0x1033
    iManufacturer: 0x01
    English (United States) "Western Digital"
    iProduct: 0x02
    English (United States) "Elements 10A2"
    iSerialNumber: 0x03
    English (United States) "575837314141323035353734"
    bNumConfigurations: 0x01

    ===>Configuration Descriptor<===
    bLength: 0x09
    bDescriptorType: 0x02
    wTotalLength: 0x002C -> Validated
    bNumInterfaces: 0x01
    bConfigurationValue: 0x01
    iConfiguration: 0x00
    bmAttributes: 0x80 -> Bus Powered
    MaxPower: 0x70 = 224 mA

    ===>Interface Descriptor<===
    bLength: 0x09
    bDescriptorType: 0x04
    bInterfaceNumber: 0x00
    bAlternateSetting: 0x00
    bNumEndpoints: 0x02
    bInterfaceClass: 0x08 -> This is a Mass Storage USB Device Interface Class
    bInterfaceSubClass: 0x06
    bInterfaceProtocol: 0x50
    iInterface: 0x00

    ===>Endpoint Descriptor<===
    bLength: 0x07
    bDescriptorType: 0x05
    bEndpointAddress: 0x83 -> Direction: IN - EndpointID: 3
    bmAttributes: 0x02 -> Bulk Transfer Type
    wMaxPacketSize: 0x0400 = 0x00 max bytes
    bInterval: 0x00
    -> This is a Mass Storage USB Device Interface Class

    ===>Descriptor Hex Dump<===
    bLength: 0x06
    bDescriptorType: 0x30
    06 30 07 00 00 00

    ===>Endpoint Descriptor<===
    bLength: 0x07
    bDescriptorType: 0x05
    bEndpointAddress: 0x0A -> Direction: OUT - EndpointID: 10
    bmAttributes: 0x02 -> Bulk Transfer Type
    wMaxPacketSize: 0x0400 = 0x00 max bytes
    bInterval: 0x00
    -> This is a Mass Storage USB Device Interface Class

    ===>Descriptor Hex Dump<===
    bLength: 0x06
    bDescriptorType: 0x30
    06 30 07 00 00 00
  9. any idea fellas?
  10. Hi all,

    I connected this drive to USB 3.0 port and its detecting now.
    Cheers !!!!!!!!!

    still not detecting via USB 2.0 though. Any suggestions.
  11. Try a USB Y-cable. USB 2.0 ports are current limited to 500mA whereas USB 3.0 can handle 900mA. A Y-cable will pick up power from two ports.
  12. fzabkar said:
    Try a USB Y-cable. USB 2.0 ports are current limited to 500mA whereas USB 3.0 can handle 900mA. A Y-cable will pick up power from two ports.



    I dont have USB 3.0 Y cable but I have USB2.0 Y cable.
    Can I try USB 2.0 cable?
  13. Sure, I don't see why not.
  14. fzabkar said:
    Sure, I don't see why not.


    Hi,

    I tried USB 2.0 Y cable but it was not fitting to the hard disk port.

    Let it be, I have made new PC and it has USB 3.0 in it. So, i'll be using my hard disk using USB 3.0 only.

    Thanks to all of your suggestion.
    Special thanks to fzabkar.
  15. fzabkar said:
    Since the drive spins up, then the HDD related electronics is probably OK. This means that the problem is either an internal one, or perhaps there is a problem with the USB-SATA bridge electronics.

    If you decide to replace the PCB, then you will need to transfer at least one (U12), maybe two (U14), serial EEPROM chips, or their contents, from patient to donor.

    One possibility is that there may be an open circuit in one or more of the USB data pins. Many WD users are reporting physical connection problems with the USB connector. You could try a USB 2.0 cable instead of USB 3.0.

    You could also see whether Microsoft's UVCView utility can detect the USB-SATA bridge chip:
    http://www.users.on.net/~fzabkar/USB_IDs/UVCView.x86.exe


    Good Sir, I was hoping you can help me out on this one. I'm experiencing a similar problem with my WD My Passport 1TB hard drive, here is the UVCView Report. Any thoughts Sir? Thank you very much.

    ---===>Device Information<===---
    English product name: "My Passport 0748"

    ConnectionStatus:
    Current Config Value: 0x01 -> Device Bus Speed: Unknown
    Device Address: 0x01
    Open Pipes: 2

    ===>Endpoint Descriptor<===
    bLength: 0x07
    bDescriptorType: 0x05
    bEndpointAddress: 0x81 -> Direction: IN - EndpointID: 1
    bmAttributes: 0x02 -> Bulk Transfer Type
    wMaxPacketSize: 0x0400 = Invalid bus speed for USB Video Class
    bInterval: 0x00

    ===>Endpoint Descriptor<===
    bLength: 0x07
    bDescriptorType: 0x05
    bEndpointAddress: 0x02 -> Direction: OUT - EndpointID: 2
    bmAttributes: 0x02 -> Bulk Transfer Type
    wMaxPacketSize: 0x0400 = Invalid bus speed for USB Video Class
    bInterval: 0x00

    ===>Device Descriptor<===
    bLength: 0x12
    bDescriptorType: 0x01
    bcdUSB: 0x0300
    bDeviceClass: 0x00 -> This is an Interface Class Defined Device
    bDeviceSubClass: 0x00
    bDeviceProtocol: 0x00
    bMaxPacketSize0: 0x09 = (9) Bytes
    *!*ERROR: Low Speed Devices require bMaxPacketSize0 = 8
    idVendor: 0x1058 = Western Digital Technologies, Inc.
    idProduct: 0x0748
    bcdDevice: 0x1019
    iManufacturer: 0x01
    English (United States) "Western Digital"
    iProduct: 0x02
    English (United States) "My Passport 0748"
    iSerialNumber: 0x05
    *!*ERROR: no String Descriptor for index 5!
    bNumConfigurations: 0x01

    ===>Configuration Descriptor<===
    bLength: 0x09
    bDescriptorType: 0x02
    wTotalLength: 0x002C -> Validated
    bNumInterfaces: 0x01
    bConfigurationValue: 0x01
    iConfiguration: 0x04
    *!*ERROR: no String Descriptor for index 4!
    bmAttributes: 0x80 -> Bus Powered
    MaxPower: 0x70 = 224 mA

    ===>Interface Descriptor<===
    bLength: 0x09
    bDescriptorType: 0x04
    bInterfaceNumber: 0x00
    bAlternateSetting: 0x00
    bNumEndpoints: 0x02
    bInterfaceClass: 0x08 -> This is a Mass Storage USB Device Interface Class
    bInterfaceSubClass: 0x06
    bInterfaceProtocol: 0x50
    iInterface: 0x06
    *!*ERROR: no String Descriptor for index 6!

    ===>Endpoint Descriptor<===
    bLength: 0x07
    bDescriptorType: 0x05
    bEndpointAddress: 0x81 -> Direction: IN - EndpointID: 1
    bmAttributes: 0x02 -> Bulk Transfer Type
    wMaxPacketSize: 0x0400 = Invalid bus speed for USB Video Class
    bInterval: 0x00
    -> This is a Mass Storage USB Device Interface Class

    ===>Descriptor Hex Dump<===
    bLength: 0x06
    bDescriptorType: 0x30
    06 30 0F 00 00 00

    ===>Endpoint Descriptor<===
    bLength: 0x07
    bDescriptorType: 0x05
    bEndpointAddress: 0x02 -> Direction: OUT - EndpointID: 2
    bmAttributes: 0x02 -> Bulk Transfer Type
    wMaxPacketSize: 0x0400 = Invalid bus speed for USB Video Class
    bInterval: 0x00
    -> This is a Mass Storage USB Device Interface Class

    ===>Descriptor Hex Dump<===
    bLength: 0x06
    bDescriptorType: 0x30
    06 30 0F 00 00 00
  16. @Dumags, the USB-SATA bridge electronics appears to be OK. The problem would be somewhere in the HDD section, possibly an internal fault. If I were approaching this problem, I would convert the PCB to SATA mode, or replace it with a compatible SATA PCB (plus firmware transfer), and then try reading its firmware modules with SeDiv or WDMarvel or WDR. More info at HDD Guru or HDD Oracle forums.
  17. Hello Fzabkar

    I also have a similar problem, could you help me with this information of my WD 2To external disk ?
    Thanks

    ---===>Device Information<===---
    English product name: "My Book 1140"

    ConnectionStatus:
    Current Config Value: 0x01 -> Device Bus Speed: High
    Device Address: 0x03
    Open Pipes: 2

    ===>Endpoint Descriptor<===
    bLength: 0x07
    bDescriptorType: 0x05
    bEndpointAddress: 0x81 -> Direction: IN - EndpointID: 1
    bmAttributes: 0x02 -> Bulk Transfer Type
    wMaxPacketSize: 0x0200 = 0x200 max bytes
    bInterval: 0x00

    ===>Endpoint Descriptor<===
    bLength: 0x07
    bDescriptorType: 0x05
    bEndpointAddress: 0x02 -> Direction: OUT - EndpointID: 2
    bmAttributes: 0x02 -> Bulk Transfer Type
    wMaxPacketSize: 0x0200 = 0x200 max bytes
    bInterval: 0x00

    ===>Device Descriptor<===
    bLength: 0x12
    bDescriptorType: 0x01
    bcdUSB: 0x0210
    bDeviceClass: 0x00 -> This is an Interface Class Defined Device
    bDeviceSubClass: 0x00
    bDeviceProtocol: 0x00
    bMaxPacketSize0: 0x40 = (64) Bytes
    idVendor: 0x1058 = Western Digital Technologies, Inc.
    idProduct: 0x1140
    bcdDevice: 0x1003
    iManufacturer: 0x01
    English (United States) "Western Digital"
    iProduct: 0x02
    English (United States) "My Book 1140"
    iSerialNumber: 0x05
    English (United States) "574D415A4135393437373938"
    bNumConfigurations: 0x01

    ===>Configuration Descriptor<===
    bLength: 0x09
    bDescriptorType: 0x02
    wTotalLength: 0x0020 -> Validated
    bNumInterfaces: 0x01
    bConfigurationValue: 0x01
    iConfiguration: 0x04
    English (United States) "USB Mass Storage"
    bmAttributes: 0xC0 -> Bus Powered
    MaxPower: 0x04 = 8 mA

    ===>Interface Descriptor<===
    bLength: 0x09
    bDescriptorType: 0x04
    bInterfaceNumber: 0x00
    bAlternateSetting: 0x00
    bNumEndpoints: 0x02
    bInterfaceClass: 0x08 -> This is a Mass Storage USB Device Interface Class
    bInterfaceSubClass: 0x06
    bInterfaceProtocol: 0x50
    iInterface: 0x06
    English (United States) "MSC Bulk-Only Transport"

    ===>Endpoint Descriptor<===
    bLength: 0x07
    bDescriptorType: 0x05
    bEndpointAddress: 0x81 -> Direction: IN - EndpointID: 1
    bmAttributes: 0x02 -> Bulk Transfer Type
    wMaxPacketSize: 0x0200 = 0x200 max bytes
    bInterval: 0x00

    ===>Endpoint Descriptor<===
    bLength: 0x07
    bDescriptorType: 0x05
    bEndpointAddress: 0x02 -> Direction: OUT - EndpointID: 2
    bmAttributes: 0x02 -> Bulk Transfer Type
    wMaxPacketSize: 0x0200 = 0x200 max bytes
    bInterval: 0x00
  18. @leinad2, sorry for my late response, but ISTM that your bridge board is mostly OK. I would connect your drive directly to a SATA port on your computer's motherboard and see whether BIOS detects it.
  19. fzabkar said:
    @leinad2, sorry for my late response, but ISTM that your bridge board is mostly OK. I would connect your drive directly to a SATA port on your computer's motherboard and see whether BIOS detects it.



    Hello
    I already tried that and the disk is not viewed in the motherboard...
  20. fzabkar said:
    @Dumags, the USB-SATA bridge electronics appears to be OK. The problem would be somewhere in the HDD section, possibly an internal fault. If I were approaching this problem, I would convert the PCB to SATA mode, or replace it with a compatible SATA PCB (plus firmware transfer), and then try reading its firmware modules with SeDiv or WDMarvel or WDR. More info at HDD Guru or HDD Oracle forums.



    Sorry for not responding immediately. Thank you for your response. I'm not that of a technical person so I took the hard drive to a hard disk recovery facility. It was determined to have several bad sectors. In a nutshell the hard drive was damaged. They were able to recover a few 100 GB of data. They mentioned the problem usually occurs when improperly ejecting the hard drive. As power is still running through the USB cable, improperly disconnecting the portable hard drive will cause the head to attach to the spinning platter inappropriately, causing physical damage. Anyhow, lesson learned - PROPERLY EJECT YOUR HARD DRIVE.
Ask a new question

Read More

Hard Drives Western Digital Power Surge Storage