SAMSUNG Stuck on Busy

Hello Huys,
I have this Samsung ST1000LM024, it get stuck on Busy and never get ready..

I have the following information on from Terminal which I don't understand...



..OK : 36
PK_1 C: 7883 H:0
GT:442
SC(L):4078/44
BE.N:26
LD..NoGray
UD..OK : 44
PK_3 C: 0 H:0
GT:443
SC(L):4083/0
BE.N:26
LD..OK
SK C: 3968 H:1
AP:1 C: 3968-> 7285 H:0->0 AP Cnt: 196
UF 3 1stGrayErr Hd:0
UF 3 1stGrayErr Hd:1
UF6 GE
UF 3 1stGrayErr Hd:3
UF 3 1stGrayErr Hd:0
UF 3 1stGrayErr Hd:1
UF6 GE
UF 3 1stGrayErr Hd:3
UF 3 1stGrayErr Hd:0
AP:2 C: 3968-> 93697 H:0->2 AP Cnt: 196
UD..OK : 0
PK_3 C: 93732 H:0
GT:443
SC(L):4076/-1
BE.N:22
LD..OK
SK C: 7935 H:1

S_0SR:0
AP:1 C: 7935-> 7285 H:0->0 AP Cnt: 197
UF 3 1stGrayErr Hd:0
UF 3 1stGrayErr Hd:1
UF6 GE
UF 3 1stGrayErr Hd:3
UF 3 1stGrayErr Hd:0
UF 3 1stGrayErr Hd:1
UF6 GE
UF 3 1stGrayErr Hd:3
UF 3 1stGrayErr Hd:0
AP:2 C: 7935-> 87827 H:0->2 AP Cnt: 197
UD..OK : -1
PK_3 C: 87852 H:0
GT:443
SC(L):4077/-1
BE.N:27
LD..OK
SK C: 7684 H:1
SR:1
AP:1 C: 7684-> 7285 H:0->0 AP Cnt: 198
UF 3 1stGrayErr Hd:0
UF 3 1stGrayErr Hd:1
UF6 GE
UF 3 1stGrayErr Hd:3
UF 3 1stGrayErr Hd:0
UF 3 1stGrayErr Hd:1
UF6 GE
UF 3 1stGrayErr Hd:3
UF 3 1stGrayErr Hd:0
AP:2 C: 7684-> 74694 H:0->2 AP Cnt: 198
UD..OK : -1
PK_3 C: 73238 H:0
GT:443
SC(L):4075/-1
BE.N:23
LD..OK
UF6 GE
AP:2 C: 7684-> 7822 H:0->1 AP Cnt: 199
UD..OK : -1
PK_3 C: 16 H:1
GT:443
SC(L):4077/6
BE.N:24
LD..OK
SK C: 7534 H:2
SR:2
AP:1 C: 7534-> 7285 H:0->0 AP Cnt: 200
UF 3 1stGrayErr Hd:0
UF 3 1stGrayErr Hd:1
UF6 GE
UF 3 1stGrayErr Hd:3
UF 3 1stGrayErr Hd:0
UF 3 1stGrayErr Hd:1
UF6 GE
UF 3 1stGrayErr Hd:3
UF 3 1stGrayErr Hd:0
AP:2 C: 7534-> 85216 H:0->2 AP Cnt: 200
UD..OK : 6
PK_3 C: 82628 H:0
GT:443
SC(L):4076/6
BE.N:25
LD..OK
SK C: 8126 H:1
SR:3
AP:1 C: 8126-> 7285 H:0->0 AP Cnt: 201
UD..OK : 6
PK_1 C: 8126 H:0
GT:443
SC(L):4079/7
BE.N:21
LD..NoGray
UD..OK : 7
PK_3 C: 0 H:0
GT:443
SC(L):4078/8
BE.N:23
LD..OK
SK C: 3884 H:1
AP:1 C: 3884-> 7285 H:0->0 AP Cnt: 202
UF 3 1stGrayErr Hd:0
UF 3 1stGrayErr Hd:1
UF6 GE
UF 3 1stGrayErr Hd:3
UF 3 1stGrayErr Hd:0
UF 3 1stGrayErr Hd:1
UF6 GE
UF 3 1stGrayErr Hd:3
UF 3 1stGrayErr Hd:0
AP:2 C: 3884-> 76004 H:0->2 AP Cnt: 202
UD..OK : 8
PK_3 C: 74369 H:0
GT:442
SC(L):4076/50
BE.N:24
LD..OK
SK C: 8088 H:1

Thank you.
 

bernardo

New member
Hello everyone.
I have the samsung ST1000LM024 too and I have the same problem. I did the serial connection and got the same information or similar information than Bankole. I dont remember what head is wrong. At first I thought that my problem was the PCB but I read here that the issue is the head. Sometimes I disconect and connect the power SATA and my hard drive keep in calm. Right away I can see some information about the hard drive and then I press enter tab. With this steps I am able to see the next prompt: erg >
In other forums I read the existence of some commands like HE (HELP), RT (reset), etc but my hard drive doesnt respond with this commands. I had the idea that my problem was the SMART so in this case I wanted to do a SMART reset.

In this forum I also read that one guy had the same problem but he disabled the wrong head and he could read some information. In this case I want to know the set of commands for this hard drive in order to disable the wrong head and recover some personal information from my hard drive. :eek: :eek: or finally I need to know what can I do? What did Bankole do? Did you recover your information?

Thanks and I am sorry for my english. :D
 
Dear sir,
today i have received same hdd with 1st grey head err terminal.After initialized in ram head map 1 1 2 3 drive shows id .when i tried to open task in de i am not successed to open it .It stuck reading id and when i see terminal those err starts again.so again i tried 1121 than i am success and task ready . I disable 0 and 3 and start partition analyze with two heads but again drive clicking.So my question is is not possible to make image head by head in de if head 0 is bad ?Do i mistake to make task ?pls help me as data is too little ,only 50mb and lies on d-drive.I have pc3k-udma as tool


S_0AP:1 C: 8163-> 7477 H:0->0 AP Cnt: 44
UF 3 1stGrayErr Hd:0
SK C:177686 H:1

S_0SR:0
AP:1 C:177686-> 7477 H:0->0 AP Cnt: 44
UF 3 1stGrayErr Hd:0
SK C:176632 H:1
SR:1
AP:1 C:176632-> 7477 H:0->0 AP Cnt: 44
UF 3 1stGrayErr Hd:0
SK C:175668 H:1
SR:2
AP:1 C:175668-> 7477 H:0->0 AP Cnt: 44
UF 3 1stGrayErr Hd:0
SK C:175181 H:1
SR:3
AP:1 C:175181-> 7477 H:0->0 AP Cnt: 44
UD..OK : 11
PK_1 C:175181 H:0
GT:442
SC(L):4086/37
BE.N:27
LDUD..OK : 37
PK_3 C: 0 H:0
GT:443
SC(L):4089/6
BE.N:22
LD..OK
UF6 GE
UF 3 1stGrayErr Hd:2
UF6 GE
UF 3 1stGrayErr Hd:0
UF6 GE
UF 3 1stGrayErr Hd:2
UF6 GE
UF 3 1stGrayErr Hd:0
AP:2 C:175181-> 22255 H:0->3 AP Cnt: 45
UD..OK : 6
PK_3 C: 24061 H:0
GT:443
SC(L):4086/20
BE.N:26
LD..OK
SK C: 7719 H:1

S_0AP:1 C: 7720-> 7477 H:0->0 AP Cnt: 46
UF 3 1stGrayErr Hd:0
SK C:175653 H:1

S_0SR:0
AP:1 C:175653-> 7477 H:0->0 AP Cnt: 46
UF 3 1stGrayErr Hd:0
SK C:175559 H:1
SR:1
AP:1 C:175559-> 7477 H:0->0 AP Cnt: 46
UF 3 1stGrayErr Hd:0
SK C:175494 H:1
SR:2
AP:1 C:175494-> 7477 H:0->0 AP Cnt: 46
UF 3 1stGrayErr Hd:0
SK C:175654 H:1
SR:3
AP:1 C:175654-> 7477 H:0->0 AP Cnt: 46
UD..OK : 20
PK_1 C:175654 H:0
GT:443
SC(L):4086/1
BE.N:23
LDUD..OK : 1
PK_3 C: 0 H:0
GT:443
SC(L):4089/17
BE.N:23
LD..OK

thanking all.
 
Gray error not always meaning bad head. Sometimes SA problem , weak head , or collapsed defect list.
I have already recovered data some samsung drives that has long GRAY error logs , endless busy mode.
I get data 3 real cases. 2 of them % 100
3th case continue . I had 50% right now. rom doesn't recognised 2 head from 4. ( maybe rom compatibility problem maybe dead head . I will see when find donor)
waiting new donor.

According to my experience I could say that;
Some gray arrow occure when deformed defect list
some gray error occure when bad or wrong zone table.
Some gray error occure when bad head
Some gray error occure when lost some head
Some gray error occure when wrong head map.
Some gray error occure when bad or wrong rom

I have 1 drive. That has endless busy nonstop gray error log.
I need stop pending reallocate command on terminal. Anyone know? Because readonly mode working perfect if drive has error like that.
 
Top