Help me diagnose MQ01UBD100

[imperia]

Hello,

I am trying to understand what the problem is with one MQ01UBD100 toshiba hdd.
When I connect the drive in linux i see:

With USB3 cable:

Code:

[ 4944.196537] usb 2-1: new high-speed USB device number 6 using ehci-pci
[ 4944.460182] usb 2-1: New USB device found, idVendor=0480, idProduct=a007
[ 4944.460187] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 4944.460190] usb 2-1: Product: External USB 3.0
[ 4944.460192] usb 2-1: Manufacturer: Toshiba
[ 4944.460194] usb 2-1: SerialNumber: 20121216004037F
[ 4944.534244] usb 2-1: can't set config #1, error -32


With USB2 cable:

Code:

[  292.251004] usb 2-1: new high-speed USB device number 5 using ehci-pci
[  292.615565] usb 2-1: New USB device found, idVendor=0480, idProduct=a007
[  292.615571] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[  292.615574] usb 2-1: Product: External USB 3.0
[  292.615577] usb 2-1: Manufacturer: Toshiba
[  292.615579] usb 2-1: SerialNumber: 20121216004037F
[  292.661177] usb-storage 2-1:1.0: USB Mass Storage device detected
[  292.661459] scsi3 : usb-storage 2-1:1.0
[  292.661541] usbcore: registered new interface driver usb-storage
[  293.661250] scsi 3:0:0:0: Direct-Access     Toshiba  External USB 3.0 0    PQ: 0 ANSI: 6
[  293.661543] sd 3:0:0:0: Attached scsi generic sg2 type 0
[  293.687826] sd 3:0:0:0: [sdb] Test WP failed, assume Write Enabled
[  293.697289] sd 3:0:0:0: [sdb] Asking for cache data failed
[  293.697408] sd 3:0:0:0: [sdb] Assuming drive cache: write through
[  293.752284] sd 3:0:0:0: [sdb] Attached SCSI disk


In Windows I see that Disk is DOWN
Unknown
Not initialized
Capacity of the drive is shown as 0 GB


Diode light is white with USB2 and blue with USB3 cable. It's not blinking.

The drive spins smoothly, without any bad noise.
The spindle doesn't make any clicking or so.

I would like to know what the problem may be before sending it for professional repair (eventually).
Or maybe I buy SATA compatible board and convert it to SATA myself.

Thanks.

[pcimage]

Either firmware corruption, a bad/weak head or media issues (bad sectors).

SATA PCB conversion won't "solve" your problem as such, but "may" make it possible to clone with something like ddrescue.

To convert to SATA you MUST transfer the "ROM" chip (careful, they are very delicate and if you break it, it's game over on this model)

[jermy]

(careful, they are very delicate and if you break it...)

or overheat it

[imperia]

Either firmware corruption, a bad/weak head or media issues (bad sectors).

SATA PCB conversion won't "solve" your problem as such, but "may" make it possible to clone with something like ddrescue.

To convert to SATA you MUST transfer the "ROM" chip (careful, they are very delicate and if you break it, it's game over on this model)

Thanks for your answer.

When I have bad sectors, shouldn't I at least hear some clicks from head trying to read sector or head moving when powering up the disk?
Because I can only "feel" the motor spinning up. I can't hear anything else.

More likely to be firmware issue?
What If i buy the same PCB(usb one) do I still have to transfer ROM to the new board?

[labtech]

+1 for suggestions so far
Also, have you tried a different USB cable? The cables on these can get iffy. Likely not the problem, but something to easily rule out.

[imperia]

+1 for suggestions so far
Also, have you tried a different USB cable? The cables on these can get iffy. Likely not the problem, but something to easily rule out.

I've tried one USB2 cable and one USB3 cable. The errors shown are different tho.

[labtech]

+1 for suggestions so far
Also, have you tried a different USB cable? The cables on these can get iffy. Likely not the problem, but something to easily rule out.

I've tried one USB2 cable and one USB3 cable. The errors shown are different tho.

Ok, what you could do now to rule out the failed drive's cable is to actually test it on the good drive that the good replacement cable were taken from. If the failed drive's cable works on the good drive, then the USB cable is not the problem.