Dear guru
accept my regards
it has been for a long time that i am involved with a SAMSUNG HN-M101MBB drive with almost strange problem :

when I connect to the PC3K machine , it spins , gets ready state , but when I click to enter utility it becomes busy . (same as WD drives with slow responding problem) , with some effors I could read and save all the modules using terminal not by ATA .

when I try to read any module (for example SLIST) by ATA it becomes busy but I could open it by terminal and saved it (SLIST.BIN then I converted it to SLIST.RPM)

all the sectors are accessible , the only problem is after 5 seconds the drive becomes BUSY if I click on any menu in PC3K.

the terminal putput is as follow:

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:19
SO_1
SPU@30'C,4702mV
IS=6
CLA ..36/109
HO..OK
HO RPM=3566 OK
AC 849
ST..OK
mS1 00000003
GT:419
SC(L):4119/89
BE.N:11
LD..OK
SK C: 7170 H:0
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 0x1002E820
FdtTable Loaded. Rev:0x02
DAM
Reading Serial Num Pass
Up MC

PwrOn RRO1x @ H0
Table) cos = -397824, sin = 218368
Coeff) cos = -88651, sin = -48186

DiskSlip : 64 [SrvTrk]
DiskSlip : 71 [SrvTrk]

PwrOn RRO1x @ H2
Table) cos = -399616, sin = 227840
Coeff) cos = -96720, sin = -83916

DiskSlip : 65 [SrvTrk]
DiskSlip : 69 [SrvTrk]
TgtCyl: 832
Hd: 0 Zn: 0 Avg.:- 152
TgtCyl: 266976
Hd: 0 Zn: 1 Avg.: 963

SVCAL(0080,0000)-->PASS
DAM
DAM
DAM
DAM
DAM
RecordValid Ok : 0407E47D 0007E41D
ReadyTime = 3617894 us
ENG>mS1 00000003
SK C:156706 H:0
SC(U)..4119/172
UD..OK : 172
PK_4 C: 27 H:0

I will be appreciated if someone can help me on this special case .

be safe of Covid19

Mojtaba

probably module 93 is damaged.
pepe

_________________
Adatmentés - Data recovery

Thank you PEPE for the reply

I checked the module 93 , it seems it is OK , I upload it here , if you have a chance to check it I will be very appreciated .

Check mod E5 as well.

can you post log when it gets bsy?

_________________
Adatmentés - Data recovery

There is a chance that problem with FIPS

_________________
Angel Data Recovery

ISTR that some drives have a copy of the FIPS in the slack area at the end of some module(s).

_________________
A backup a day keeps DR away.

Fill it with FF is about to enough , or use from working donor drive . It is stored in ROM , log module .

_________________
Angel Data Recovery

There is a copy of the FIPS block in the MOVLY001 module at offsets 0x2E800 - 0x2F7FF, at least in this ST1000LM024 / HN-M101MBB example:

http://www.hddoracle.com/viewtopic.php?f=59&t=698&p=12233

_________________
A backup a day keeps DR away.

thank you everybody , I will post the results here and also the terminal messages . thank you again

could anybody provide me with ROM and OVL of version 2ARnfj9M_d67 ?

thx,
pepe

_________________
Adatmentés - Data recovery

http://files.hddguru.com/download/SHTR/Burn/

FWIW, there is a 2ARnfj9M.167 file in the burn list.

_________________
A backup a day keeps DR away.

thx, i will check that too. I got it in the meantime.

also checked the OP's fw, coz it hung massively, ie. SATA bsy, no terminal output, no DBG prompt, nothing. So i suspected it might be corrupted but no, it isn't. The case was solved using another fw and some patches, but i think this fw has some bug that got triggered by the sa problems.
This is not rare in samsungs

pepe

_________________
Adatmentés - Data recovery

Here I should appreciate PEPE, he did me a favor and solved the problem .

*************** thank you PEPE ***************

welcome.

what bothers me is that we still don't know what the original cause was
btw, you could try this:

rewrite modules 93,E5,F4 and F5, from another disk.
rewrite original ovl (73)
rewrite original rom
and check what happens

pepe

_________________
Adatmentés - Data recovery