Samsung HN-M101ABB not starting after repair

[haeuss]

Hi,

I have a Samsung HN-M101ABB with USB-3 on PCB where the USB 3.0 Micro-B connector was damaged and had no connection to PCB.
I soldered the connector and checked that all USB connections are ok now.
But after reassembling the disk was not recognized by computer (Mac and PC)
The PC installed driver but no volume was shown.
On the Mac console this entry appeared:

15.10.15 21:33:43,000 kernel[0]: USBMSC Identifier (non-unique): 433736303247313441413843304E 0x152d 0x539 0x100, 2
15.10.15 21:34:47,000 kernel[0]: USBF: 1433.716 AppleUSBEHCI::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 6, EP: 1)

The disk spins up. The heads are moving. No clicking sound.
But the status LED does not light up!

I made a terminal output of the disk at startup:


ActiveFW : 00
FWVer : 0001
SATA PLL cal done
DDR size detected = 8MB

DDR size detected = 8MB

*PAUNI_L2957*PA VID=0006 PN=0009 Rev=0002- PA_UNI Found
*PAUNI_L2957*PA VID=0006 PN=0009 Rev=0002- PA_UNI FoundU
S_0SHK NF Cal:27
SO_1
SPU@22'C,4701mV
IS=5
CLA ..36/90
HO..OK
HO RPM=593 OK
AC 2027
ST..OK
mS1 00000003
GT:390
SC(L):4121/90
BE.N:18
LD..OK
SK C: 7467 H:0
Boot Sector Error! Take a default.
Loaded FIT ( 0: 0: 1)
CalibTable Loaded. Rev:0x1B
ResoTable Loaded. Rev:0x01
Bump Limit Loaded. Rev:0x01
RRO1xTable Loaded. Rev:0x01
Fw Active 00
Ovly loaded to 0x00014D00
Ovly loaded to 0x1002E408
FdtTable Loaded. Rev:0x02
Reading Serial Num Pass
Up MC

PwrOn RRO1x @ H0
Table) cos = -707328, sin = -1427968
Coeff) cos = -50951, sin = 73006

DiskSlip : 225 [SrvTrk]
DiskSlip : 220 [SrvTrk]

PwrOn RRO1x @ H2
Table) cos = -575488, sin = -1190400
Coeff) cos = 34885, sin = -13376

DiskSlip : 187 [SrvTrk]
DiskSlip : 188 [SrvTrk]
TgtCyl: 832
Hd: 0 Zn: 0 Avg.:- 211
TgtCyl: 266768
Hd: 0 Zn: 1 Avg.: 986

SVCAL(0080,0000)-->PASS
RecordValid Ok : 0407E47D 0007E41D
ReadyTime = 4463001 us
ENG>
E_F
FSA1
C0

E_F
FSA2
C0
FSA_F1
FSA1
C0

E_F
FSA2
C0
FSA_F1
FSA1
C0

E_F
FSA2
C0
FSA_F1
FSA1
C0

and so on...


Perhaps any of you gurus could help me to get this drive to live again?!?


Thanks.

[fzabkar]

I can't help you, but ISTM that your soldering was good and the USB-SATA bridge IC appears to be working.

15.10.15 21:33:43,000 kernel[0]: USBMSC Identifier (non-unique): 433736303247313441413843304E 0x152d 0x539 0x100, 2

0x152D is JMicron's Vendor ID, and 0x539 appears to be the Product ID of the JMS539 bridge IC.

"433736303247313441413843304E" is the hex-encoded ASCII representation of the drive's P/N, namely "C7602G14AA8C0N". That should be at the bottom of the label.

[haeuss]

"433736303247313441413843304E" is the hex-encoded ASCII representation of the drive's P/N, namely "C7602G14AA8C0N". That should be at the bottom of the label.

That's correct.

But does the drive also receive data? I'm not sure.

After some minutes the disk appeared on the mac's disc utility but could not be accessed:
16.10.15 16:53:05,000 kernel[0]: disk4: I/O error.
16.10.15 16:54:54,000 kernel[0]: disk4: I/O error.
16.10.15 16:56:20,000 kernel[0]: disk4: I/O error.
16.10.15 16:57:49,000 kernel[0]: disk4: I/O error.

Could a PCB replacement help? The status LED doesn't even light up!

[fzabkar]

I can't see how it could be a PCB fault.

[pcimage]

"SK C: 7467 H:0
Boot Sector Error! Take a default.
Loaded FIT ( 0: 0: 1)"

This would indicate more serious issues.

[day1data]

"SK C: 7467 H:0
Boot Sector Error! Take a default.
Loaded FIT ( 0: 0: 1)"

This would indicate more serious issues.

+1

[haeuss]

"SK C: 7467 H:0
Boot Sector Error! Take a default.
Loaded FIT ( 0: 0: 1)"

This would indicate more serious issues.

Oh oh,

that does not sound good!

How could this happen?
The drive was working before, only the USB connector was damaged.

What can be done to rescue data?

[pcimage]

"SK C: 7467 H:0
Boot Sector Error! Take a default.
Loaded FIT ( 0: 0: 1)"

This would indicate more serious issues.

Oh oh,

that does not sound good!

How could this happen?
The drive was working before, only the USB connector was damaged.

What can be done to rescue data?

If you really need the data then it needs to go to someone who has the right tools for the job and knows what they are doing.

Quite often a damaged connector is a consequence of a user wiggling the connector to try and get the drive to work, thinking its a connection problem when the original problem lies elsewhere. Not saying it's the case here for sure, but we see it all the time.

We can take a look if you're willing to ship to UK.

[haeuss]

If you really need the data then it needs to go to someone who has the right tools for the job and knows what they are doing.

Quite often a damaged connector is a consequence of a user wiggling the connector to try and get the drive to work, thinking its a connection problem when the original problem lies elsewhere. Not saying it's the case here for sure, but we see it all the time.

We can take a look if you're willing to ship to UK.

I think you are right. This job should be done now by a professional.

But when i received the drive from a friend it was only to get to work, when the USB connector was extremely bended.
The connector on the PCB was loose and had no connection to the pad.
So took off the PCB, re-soldered the connector, screwed on the PCB and had the problem described above...

How could I damage the hard drive by disassemble and assemble the PCB?

What happens if I run the PCB without connected HDD? I think I did this after it was not working at first.

[day1data]

Running the PCB by itself won't cause any damage. You will most likely just get a LED error in terminal.

As said previously obviously your soldering skills are good, judging by the terminal output you posted the PCB is not the issue. like Pcimage said the drive had problems previous to the issue with the USB connector.

Whoever was using the drive just assumed the USB connector was at fault when the drive stopped functioning properly. Then they just made the situation worse by breaking the USB connector which was not the issue in the first place.

Sorry to say but the only chance is with professional data recovery.

[fzabkar]

It appears that a working drive should identify itself with a USB Vendor ID of 0x04E8 (Samsung) and a Product ID of 0x60A8. These IDs are stored in a serial EEPROM.

http://www.pc-help.cz/viewtopic.php?t=151885

(2) SAMSUNG HN-M101ABB
----------------------------------------------------------------------------
Enclosure : Samsung S2 Portable 3 USB Device (V=04E8, P=60A8, sa1)
Model : SAMSUNG HN-M101ABB
Firmware : 2AR10001
Serial Number : C7112G14AA9EET

IME a USB bridge IC will identify itself with the bridge IC manufacturer's VID and PID (JMicron) if the external serial EEPROM is bad or has a bad checksum. I suppose this could also be symptomatic of the bridge firmware's inability to communicate with the HDD.

[haeuss]

Update:
In the meantime I received my replacement PCB from China.
I swapped the BIOS chip and tried the disk but without success (just the LED is working again).
As some of you mentioned before it was not the PCB!

I think I need the firmware to be checked by a professional - I don't have the tools to do this.

But going to a local data recovery company would be to expensive.
Because the disk contains no business data "just" private files of a friend, who won't pay hundreds of Euro.
She even saved the money for a backup!
But I really want to help her.

Perhaps someone of you has the ability or knows someone, who does it for a fair price?

[pcn]

Sorry but as the other pros told you it seems the pcb is ok & " flash / bios / firmware " also. Its a problem with heads and/or media damage (disk i/o errors). Stop to play with the drive, things get worse and worse.

Do not open the drive. If data is important contact a pro. If your friend can not afford the costs for DR atm, do it later. Messing with the drive/data will lead to all data lost for sure.

best regards,

PS: You can contact day1data or us to check the drive or contact a DR pro near your location.