Samsung Spinpoint ST1000LM024 Stuck at BSY, no terminal

D

datahaze

Member
I have a Samsung Spinpoint ST1000M024 which is stuck at BSY. Soft and hard resets seem to do nothing. It fails to identify at all. The full specs are below. Using the utility Spinpoint USB and Spinpoint M8E 2.5 HN-M101BB I'm unable to even get terminal access (using UART bridge) or detect the baud rate. Does anybody have any suggestions? I am fairly new to using the PC-3000.

Model: ST1000LM024
HDD P/N: HN-M101MBB/AV2
Rev A F/W 2BA30003

It also has Seagate Momentus on the label, this is from an external Seagate 2.5" USB drive. I have removed the USB controller and connected it directly to SATA. Should I be using a Seagate utility instead? Which one?

Thank you in advance to anybody who is able to help on this, your advice is greatly appreciated. Thanks!
 
Jared

Jared

Administrator
Staff member
datahaze":1jixz82v said:
[post]11105[/post] Should I be using a Seagate utility instead?
Click to expand...

No, I'm pretty sure that one is Samsung Architecture. Are you sure you've got the terminal connected correctly and using the correct adapter? Also, how did you bypass the USB? Direct soldering or did you replace the PCB with a compatible SATA one? You should be seeing something in the terminal.
 
D

datahaze

Member
This model just uses a SATA -> USB adapter, so I just removed the adapter and used a direct SATA connection. The COM section is connected using the Samsung adapter which is connected to the PCB USB Terminal 2, which is then connected to the PC via a USB cable on a USB 2.0 port, and the UART bridge shows as an option for the COM port in the PC-3000. Unless the cable has a particular orientation it needs to be in, I think it's connected properly.
 
Jared

Jared

Administrator
Staff member
datahaze":1hvmis3j said:
This model just uses a SATA -> USB adapter, so I just removed the adapter and used a direct SATA connection. The COM section is connected using the Samsung adapter which is connected to the PCB USB Terminal 2, which is then connected to the PC via a USB cable on a USB 2.0 port, and the UART bridge shows as an option for the COM port in the PC-3000. Unless the cable has a particular orientation it needs to be in, I think it's connected properly.
Click to expand...

The cable does have a specific orientation always. Double check that the red stripe is on the right side as shown in the pictures in the PC-3000 manual. Then try it on another Samsung drive and see if your connection is working.
 
D

datahaze

Member
Aah thank you for your help on this Jared, I feel like such a dope! I've got terminal access now : ). Drive still showing as BSY. I figure there's some issue accessing the SA.

I tried going to HDD Initialization -> RAM Head Map editing and cycling through heads 0-3. Each time, I put "0,0,0,0" "1,1,1,1" etc it appears to work but when it gets to the end it times out because drive is still in BSY. I've tried doing soft resets afterwards to the same effect

[nfo]****************************************
Debug mode

ROM loading
From file............................... : <HDD Profile>\Data\ROM\rom.bin

Selected parameters
Heads map............................... : 1, 1, 1, 1
Disable record in service area.......... : No

Memory map building..................... : Ok
Search for free memory space............ : Ok
Search control point.................... : Ok
Search table of zone translation address : Ok

Creating a pointer to executable code... : Ok
Source code patching.................... : Ok
Head map setup.......................... : Ok
Heads map............................... : 1, 1, 1, 1
Normal mode[/nfo]

Here is the terminal output when the drive initializes:
[nfo]ActiveFW : 00
FWVer : 0001
SATA PLL cal done
DDR size detected = 16MB

DDR size detected = 16MB

*PA_TI5565*PA VID=0012 PN=0055 Rev=0000- PA_TI5565 Found
*PA_TI5565*PA VID=0012 PN=0055 Rev=0000- PA_TI5565 FoundU
S_0SO_1
SPU@31'C,5058mV
IS=2
CLA ..Stuck..0/30
HO..TO
SO_2 C=1,A=0,S=1,RPM=0
SPU@31'C,5055mV
IS=2
CLA ..Stuck..1/44
HO..TO
SO_2 C=2,A=0,S=2,RPM=0
SPU@31'C,5054mV
IS=2
CLA ..Stuck..1/31
HO..TO
SO_2 C=3,A=0,S=3,RPM=0
SPU@31'C,5051mV
IS=2
CLA ..Stuck..1/31
HO..TO
SO_2 C=4,A=0,S=4,RPM=0
SPU@31'C,5056mV
IS=2
CLA ..Stuck..1/44
HO..TO
SO_2 C=5,A=0,S=5,RPM=0
SPU@31'C,5053mV
IS=2
CLA ..Stuck..1/31
HO..TO
SO_2 C=6,A=0,S=6,RPM=0
SPU@31'C,5052mV
IS=2
CLA ..Stuck..1/44
HO..TO
SO_2 C=7,A=0,S=7,RPM=0
SPU@31'C,5059mV
IS=2
CLA ..Stuck..1/44
HO..TO
SO_2 C=8,A=0,S=8,RPM=0
SPU@31'C,5051mV
IS=2
CLA ..Stuck..1/44
HO..TO
SO_2 C=9,A=0,S=9,RPM=0
SPU@31'C,5056mV
IS=2
CLA ..Stuck..1/31
HO..TO
SO_2 C=10,A=0,S=10,RPM=0
SPU@31'C,5054mV
IS=2
CLA ..Stuck..1/44
HO..TO
SO_2 C=11,A=0,S=11,RPM=0
SPU@31'C,5054mV
IS=2
CLA ..Stuck..1/31
HO..TO
SO_2 C=12,A=0,S=12,RPM=0
SPU@31'C,5057mV
IS=2
CLA ..Stuck..1/31
HO..TO
SO_2 C=13,A=0,S=13,RPM=0
SPU@31'C,5059mV
IS=2
CLA ..Stuck..1/31
HO..TO
SO_2 C=14,A=0,S=14,RPM=0
SPU@31'C,5055mV
IS=2
CLA ..Stuck..1/31
HO..TO
SO_2 C=15,A=0,S=15,RPM=0
SPU@31'C,5059mV
IS=2
CLA ..Stuck..1/44
HO..TO
SO_2 C=16,A=0,S=16,RPM=0
SPU@31'C,5053mV
IS=2
CLA ..Stuck..1/31
HO..TO
SO_2 C=17,A=0,S=17,RPM=0
SPU@31'C,5055mV
IS=2
CLA ..Stuck..1/44
HO..TO
SO_2 C=18,A=0,S=18,RPM=0
SPU@31'C,5058mV
IS=2
CLA ..Stuck..1/31
HO..TO
SO_2 C=19,A=0,S=19,RPM=0
SPU@31'C,5053mV
IS=2
CLA ..Stuck..1/31
HO..TO
SO_2 C=20,A=0,S=20,RPM=0
SPU@31'C,5051mV
IS=2
CLA ..Stuck..1/31
HO..TO
SO_2 C=21,A=0,S=21,RPM=0
SPU@31'C,5054mV
IS=2
CLA ..Stuck..1/44
HO..TO
SO_2 C=22,A=0,S=22,RPM=0
SPU@31'C,5052mV
IS=2
CLA ..Stuck..7/53
HO..TO
SO_2 C=23,A=0,S=23,RPM=0
SPU@31'C,5059mV
IS=2
CLA ..Stuck..1/31
HO..TO
SO_2 C=24,A=0,S=24,RPM=0
SPU@31'C,5052mV
IS=2
CLA ..Stuck..1/31
HO..TO
SO_2 C=25,A=0,S=25,RPM=0
SO_3 R Sp Err
EPOK
UDed
PK_4 C: 0 H:0
LED 1703
LED 1703[/nfo]

Also, maybe this is important, this drive is spitting out LED1703 errors in the terminal, I've applied the fix the utility provides on each Head Map editing cycle, which stops the errors in terminal but otherwise does nothing else.

Any pointers about where to go next? Thanks for all of your help on this! I hope at some point I can become a contributor and knowledge-sharer here as well : )
 
D

datahaze

Member
Yep. There's some clicking, sounds like seeking to me but it's hard to tell, then the clicking/attempts stop. My guess is the head is stuck to the platter based on the terminal output. Its too quiet to hear if it's spinning specifically
 
You must log in or register to reply here.
Top