Samsung 1tb; PCB ok, head ok, no access!!!

[hugov]

Hello friends.

Do you know any solution for this error?

*PA VID=0000 PN=0004 Rev=0002- 785x Found002- 785x Found
*PA VID=0000 PN=0004 Rev=0002- 785x Fou *PA VID=0000 PN=0004 Rev
nd
ChipRev = 63B0
=0002-
U

S_0
RV En Sensor Circuit
En Shock Sensor Circuit U
SO_1
SpinStartUp: mcSpinRPM = 0En Sensor Circuit
RPM at Handoff: 588 Sensor Circuit
Temp : 28 degC
SO_1
Sp
SpinOkUp: mc
mS1 00000003
SK C:111981 H:0 at Handoff: 58
POK
POK
Boot Sector Error! Take a default.
SpinOk
mS1 00000003
Loaded FIT ( 0: 0: 1)
CalibTable Loaded. Rev:0x14
Selective MARC NX Loaded
ResoTable Loaded. Rev:0x01
Ovly loaded to 0x0001CD00
Ovly loaded to 0x1005B800
FdtTable Load
Hd: 0 Zn: 1 Avg.: 51

SVCAL(0080,0000)-->PASS
| 147 | IN_SITU | 20 | 0 | 836 | 1140 |
>>InsituStart: t=1285, c=29
| 147 | IN_SITU | 20 | 0 | 836 | 1140 |
| 249 | NINSITUL | 45 | 0 | 2 | 1140 |
GeoId = 49, Idx=49
fodstep: 00000069 dgain: 0000007E
GeoId = 49, Idx=49
fodstep: 0000006C dgain: 00000089
GeoId = 49, Idx=49
fodstep: 0000006D dgain: 00000085
GeoId = 49, Idx=49
fodstep: 00000065 dgain: 0000005A
GeoId = 49, Idx=49
fodstep: 00000072 dgain: 00000061
GeoId = 49, Idx=49
fodstep: 0000007A dgain: 0000005E
GeoId = 49, Idx=49
fodstep: 0000006A dgain: 0000005E
GeoId = 49, Idx=49
fodstep: 00000072 dgain: 00000066
GeoId = 49, Idx=49
fodstep: 00000075 dgain: 00000064
GeoId = 49, Idx=49
fodstep: 0000005F dgain: 0000006A
GeoId = 49, Idx=49
fodstep: 0000006B dgain: 00000072
GeoId = 49, Idx=49
fodstep: 00000071 dgain: 0000006D
EPOK
W-MC e(00007704) (20: 0: 864:0x08:0x003F)
EPOK
>>Flag=0000028B BadHd=0001 dFod=0019 001E 0019 0015 (t=2479 c=28)
W-MC e(00007704) (20: 0: 864:0x08:0x003F)
| 244 | ZONHEAL2 | 43 | 0 | 0 | 1140 |
| 167 | DRM | 33 | 0 | 0 | 1140 |
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A21 L0 1005BDB3]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A21 L0 0000EC77]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A21 L0 0000EC77]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A21 L0 0000EC77]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A21 L0 0000EC77]
[DEBUG HALT @MDL_RSRC_BufferAlloc()
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A21 L0 0000EC77]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A21 L0 0000EC77]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A21 L0 0000EC77]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A21 L0 0000EC77]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A21 L0 0000EC77]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A21 L0 0000EC77]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A21 L0 0000EC77]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A21 L0 0000EC77]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A21 L0 0000
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A21 L0 0000EC77]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A21 L0 0000EC77]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A21 L0 0000EC77]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A21 L0 0000EC77]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A21 L0 0000EC77]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A21 L0 0000EC77]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A21 L0 0000EC77]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A21 L0 0000EC77]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A21 L0 0000EC77]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A21 L0 0000EC77]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A21 L0 0000EC77]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A21 L0 0000EC77]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A21 L0 0000EC77]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A21 L0 0000EC77]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A21 L0 0000EC77]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A21 L0 0000EC77]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A21 L0 0000EC77]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A21 L0 0000EC77]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A21 L0 0000EC77]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A44 L0
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A21 L0 0000EC77]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A21 L0 0000EC77]
[DEBUG HALT @tProfile():10034A21 L0 0000EC77]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A21 L0 0000EC77]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A21 L0 0000EC77]
Cur_SP=04005D20
FIQ_SP=04005D20
IRQ_SP=04005D20
SVC_SP=04005D20

*** HALT ***

Thanks to those who help.

[sempre]

Hello!!

Verify modules!!

[hugov]

have some alternative way, without being with UDMA?

[shahij]

did you get the solution yet?

I have a same error with HD503HI.

Always BSY.

also added terminal log...

INCREASE A SECTOR SIZE IN MC!

[shahij]

FULL LOG is attached... Please advice.

Attachments

LOG.zip

(923 Bytes) Downloaded 343 times

[BlackST]

have some alternative way, without being with UDMA?

Write your own software.
P.s. Either the pcb is not native or someone played hard with firmware or ROM (OR used non native PCB) ?

[shahij]

have some alternative way, without being with UDMA?

Write your own software.
P.s. Either the pcb is not native or someone played hard with firmware or ROM (OR used non native PCB) ?

The PCB is native. 100% confirm. Nothing has been done. After the loss, the drive came directly to me.

The drive is always busy. Got access to SA by HotSwap. Smart Reset, A-list clear. Here is SAME LOG even after doing this so.

Now, I will have to check whole SA. Do you still have any idea now?

[BlackST]

have some alternative way, without being with UDMA?

Write your own software.
P.s. Either the pcb is not native or someone played hard with firmware or ROM (OR used non native PCB) ?

The PCB is native. 100% confirm. Nothing has been done. After the loss, the drive came directly to me.

The drive is always busy. Got access to SA by HotSwap. Smart Reset, A-list clear. Here is SAME LOG even after doing this so.

Now, I will have to check whole SA. Do you still have any idea now?

I'm missing something : hugov and shahij are then actually the same person or same case ?

[shahij]

have some alternative way, without being with UDMA?

Write your own software.
P.s. Either the pcb is not native or someone played hard with firmware or ROM (OR used non native PCB) ?

The PCB is native. 100% confirm. Nothing has been done. After the loss, the drive came directly to me.

The drive is always busy. Got access to SA by HotSwap. Smart Reset, A-list clear. Here is SAME LOG even after doing this so.

Now, I will have to check whole SA. Do you still have any idea now?

Hey BLACK, I think, you didn't read the post completely... he posted jan12 and I did in last 3 days... his case is 1TB but my case is 500GB (HD500HI).

Anyway, do you have any clue or explanation regarding the case? I would be happy if you like to share or also you can PM me to avoid public...

FYI: The HDD failed during a DATA CONVERSION of SQL database. Suddenly the HDD stopped/PC shut off and the user didn't get the drive detected anymore and sent to me directly for the recovery.