ST2000DM001 no ID, stuck in BSY

216 views
Skip to first unread message

Markus Bauer

unread,
Mar 11, 2022, 7:05:41 AM3/11/22
to DataRecoveryCertification
Hello,

I have a ST2000DM001 here and the drive sounds OK. It spins up, stay for 1-2sec. BSY and then reports DRD + DSC.

The log windows how only this:

Boot 0x40M
 Spin Up
 Trans.

 Spin Up
SpinOK
(P) SATA Reset


No error and no unusual sounds.

Automatic detection fails and the drive get stuck in BSY-state when I try to select the F3-utility manual then I have the same result. Stuck in BSY and no ID at all - no model, no size, nothing. 

I had the idea it's maybe related to the PCB as the PCB and the contacts where pretty bad looking. I cleaned the contacts and it did not help so I try to replace the PCB.

After programming a new PCB with the ROM of the old one I get the following output:

Identifying device...
Device identification error!

Getting detailed firmware version...
Failed to get firmware version!

Physical sector size : .............................Failed to get

physical sector size of service area : .............Failed to get

Number of physical heads : .........................Failed to get
Get System module information ...
     ID          length          Description
 =========================

Failed to get system module information!

THE POWER-CYCLE WAS HERE 

Getting DT information...

ROM:
   ID          Offset address          Length
============================

   00          40030200          40944          
   01          40030000          512          
   04          0001D400          7168          
               40002000          13288
                  total          20456
   05          0006C000          81920          
   08          80070000          968          
   0A          0025EA94          1024          
   0F          80014040          768          
   10          80015D00          448          
   12          800D40C0          72          
   13          401291C0          1440          
   14          40129760          120          
   15          00000000          524288          
   1D          40030220          424          
   1E          400305B8          4016          
   26          40126CF0          9424          
   27          40126AF8          504          

RAM:
 ID          offset address          length
 ============================

   00          40030200          40944          
   01          40030000          512          
   02          400303C8          496          
   04          0001D400          7168          
               40002000          13288
                  total          20456
   05          0006C000          81920          
   06          01915C40          81964          
   08          80070000          968          
   0A          0025EA94          1024          
   0F          80014040          768          
   10          80015D00          448          
   12          800D40C0          72          
   13          401291C0          1440          
   14          40129760          120          
   15          00000000          524288          
   16          40030200          32          
   17          400319A0          2016          
   1D          40030220          424          
   1E          400305B8          4016          
   1F          4032C8E8          4500          
   20          4032DA80          150          
   26          40126CF0          9424          
   27          40126AF8          504          

Finished to get DT information!

Getting service area size.......
Service area size : .................................0x315A0F

Getting list  of sys files.......
Getting list of sys files completed!
Reading autotuning buffer
Buff Root FAT searching  in RAM : ...................OK
Searching module table in RAM : .....................OK
Searching DT table(RAM, WR) in RAM : ................OK
Searching DT table(RAM, RD) in RAM : ................OK
Searching volume 0 file table in RAM : ..............OK
Searching volume 3 file table in RAM : ..............OK
Searching SMP RAM FID in RAM : ......................OK
Searching Non Resident G-List FID in RAM : ..........OK
Searching CFW OVL FID in RAM : ......................OK


MRT had also to power-cycle the drive to read some data.

I have now the F3-Modules list but I can't read some module.

But I can communicate via terminal:

F3 7>X

Head 00 Resistance 012F
Head 01 Resistance 013D
Head 02 Resistance 0128
Head 03 Resistance 0111


Maybe you guys have an idea what that could be?

jol qwerr

unread,
Mar 11, 2022, 8:08:17 AM3/11/22
to datarecovery...@googlegroups.com
take care on 93 using terminal

Fraser Corrance

unread,
Mar 11, 2022, 12:58:27 PM3/11/22
to DataRecoveryCertification

F"RWRecoveryFlags",00,22 (disables read sparing, write sparing, and enables correction)

F"BGMSFlags",00,22 (disables background media scan)

F"PerformanceFlags",043C,22 (disables offline sparing and deferred auto reallocation)

F"ReadRetries",00,22 (disables read retries)

t...@desertdatarecovery.com

unread,
Mar 11, 2022, 1:36:25 PM3/11/22
to datarecovery...@googlegroups.com

I have tried those a few times without much success.

Maybe I am not using them correctly.

This is what I use now.

 

SMP Flags Fix Via Terminal

 

Show add. diag. msg in Terminal [NO] :

T>F”SerialDebugLevel”,0

 

Offline defect sparing [NO] :

T>F”OFFLINE_SPARING_ENABLED”,0

 

Deferred defect hiding [NO] :

T>F”DAR_ENABLED”,0

 

Auto Reallocation (writing) [NO] :

T>F”WRITE_SPARING_ENABLED”,0

 

Auto Reallocation (reading) [NO] :

T>F”READ_SPARING_ENABLED”,0

 

Disable IDLE activities [YES] :

T>F”DISABLE_IDLE_ACTIVITY”,

 

Tim Homer - Lead Engineer

Desert Data Recovery

t...@desertdatarecovery.com

www.desertdatarecovery.com

--
Data Recovery Certification Group / for issue with google group please email sc...@myharddrivedied.com
---
You received this message because you are subscribed to the Google Groups "DataRecoveryCertification" group.
To unsubscribe from this group and stop receiving emails from it, send an email to datarecoverycertif...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/datarecoverycertification/85da3d59-2c6b-460a-9717-f147e0d1c10fn%40googlegroups.com.

Fraser Corrance

unread,
Mar 11, 2022, 2:06:36 PM3/11/22
to DataRecoveryCertification
I have found that entering the commands through terminal usually works when altering them through the utility does not. If I recall correctly, Marcus uses the MRT which I am not familiar with which is why I suggested the terminal commands. Dose MRT have something similar to the PC3K 'Edit HDD ID' utility?

Fraser Corrance

unread,
Mar 11, 2022, 2:17:49 PM3/11/22
to DataRecoveryCertification
And, by the way, thanks for sharing, Tim. I will add these to my big book of Seagate tricks. ;-)

pbzcbf...@gmail.com

unread,
Mar 11, 2022, 2:29:59 PM3/11/22
to DataRecoveryCertification
http://www.hddoracle.com/viewtopic.php?f=22&t=2271

SA module 34 contains documentation for the Congen parameters.


Markus Bauer

unread,
Mar 12, 2022, 9:37:22 AM3/12/22
to DataRecoveryCertification
Sorry for the late answer - I was getting totally chought up in the belkasoft CTF challenge and needed till 4am to solve all the brainf**k challenges they setup this time.

@jol
Thanks - that would have pointed me in the right direction.

@fraser
Yes sure - MRT hat Edit HDD ID and Edit HDD ID in RAM. I tryed that before but it did not work in that one. 
I just had no clue that's cased by background activities or I would have used the F-commands.

Gernadas seem to be famous for that - I had 2 in the past where Edit HDD ID solved the case and one where I searched the F-commands together.

But I had never seen a Seagate just locking up without any error or terminal output - just getting stuck.

@fraser and Tim
Thanks for pointing out the commands that have saved me digging trough the Output of T> F


Wish you all a nice weekend. 

Fraser

unread,
Mar 13, 2022, 1:11:42 AM3/13/22
to datarecovery...@googlegroups.com


The challenge looks pretty interesting. So, how did you do? 
 
Any luck with that drive?

On Mar 12, 2022, at 6:37 AM, Markus Bauer <m.bau...@gmail.com> wrote:


--
Data Recovery Certification Group / for issue with google group please email sc...@myharddrivedied.com
---
You received this message because you are subscribed to a topic in the Google Groups "DataRecoveryCertification" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/datarecoverycertification/VCtmpmXRoLM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to datarecoverycertif...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/datarecoverycertification/632e995b-611d-4c85-8fd5-9ecf7a7aa415n%40googlegroups.com.

Markus Bauer

unread,
Mar 13, 2022, 3:00:55 AM3/13/22
to DataRecoveryCertification
Hi. 
Challange was fun as always - Belkasoft do great CTFs. There where a few screwups which create some rabbitholes which cost me a lot of time. But after a sleepless night I got all solved but I needed a few hints. For example I would never come up with the idea to analyze a WAV-file in a spectrum analyzer... I learn at least a lot!

The drive is imaging - I have a lot of gaps which could not be read till now but roughly 70% of the data is cloned till now. Actually run the 3rd pass and fill in the gaps.

Reply all
Reply to author
Forward
0 new messages