MultiDrive – free backup, clone & wipe disk utility from Atola Technology

Main » Forums home » Conventional hard drives

All times are UTC - 5 hours [ DST ]



Post new topic Reply to topic  Page 1 of 1
  [ 9 posts ] 
  Previous topic | Next topic 
Author Message
Seag3029
 Post subject: ST2000DM001 busy / inaccessible
PostPosted: February 14th, 2026, 11:05 
Offline

Joined: February 14th, 2026, 10:41
Posts: 3
Location: Earth
I have a ST2000DM001 that's no longer responsive.

Symptoms: disk was being written to, but progressively became slower. After replugging it a couple of times it's no longer detected at all (via usb). Once I was able to read a single sector, after which all I/O fails.

I have connected serial, boot:
Code:
Boot 0x40M
Spin Up
RECOV Servo Op=0100 Resp=0005
Trans.

Spin Up
SpinOK
(P) SATA Reset


Other info:

Code:
F3 1>N5
Att
Num  Flgs normlzd worst raw
1   000F   77     63   0000000D54B008
3   0003   5C     5B   00000000000000
4   0032   63     63   00000000000514
5   0033   64     34   0000000000E738
7   000F   35     35   0000080018B191
9   0032   63     63   00000000000662
A   0013   64     64   00000000000000
C   0032   63     63   0000000000050D
B7   0032   64     64   00000000000000
B8   0032   64     64   00000000000000
BB   0032   64     64   00000000000000
BC   0032   62     4F   00003300330033
BD   003A   64     64   00000000000000
BE   0022   38     2D   0000008080002C
BF   0032   64     64   00000000000000
C0   0032   64     64   0000000000020A
C1   0032   62     62   00000000001331
C2   0022   2C     37   00000D0000002C
C5   0012   64     64   00000000000000
C6   0010   64     64   00000000000000
C7   003E   C8     C8   00000000000000
F0   0000   64     FD   33711300000170
F1   0000   64     FD   0000009109A488
F2   0000   64     FD   0000004E013F68
0   0000    0      0   00000000000000
0   0000    0      0   00000000000000
0   0000    0      0   00000000000000
0   0000    0      0   00000000000000
0   0000    0      0   00000000000000
0   0000    0      0   00000000000000

F3 1>/T

F3 T>V4
Reassigned Sectors List Enabled
Entries: 4000, Alts: 3F9B, Removed: 0000,
Pending: 0000 Host Pending: 0000
Idx  LBA          PBA          LLLCHS of LBA Wdg PLPCHS of PBA SFI    Hours Msecs  Status           BBM Mask

0000 00000007AC59 00001D290C13 000000.0.0000 000 047569.2.00B4 09360B 0065B 35EEB3 0001001000000000 11111111
0001 00000007AC5A 00001D290C14 000000.0.0000 000 047569.2.00B5 094296 0065B 35F022 0001001000000000 11111111
0002 00000007AC5B 00001D290C15 000000.0.0000 000 047569.2.00B6 094F21 0065B 35F188 0001001000000000 11111111
0003 00000007AC5C 00001D290C16 000000.0.0000 000 047569.2.00B7 095BAC 0065B 35F2EE 0001001000000000 11111111
0004 00000007AC5D 00001D290C17 000000.0.0000 000 047569.2.00B8 096837 0065B 35F45D 0001001000000000 11111111
0005 00000007AC5E 00001D290C18 000000.0.0000 000 047569.2.00B9 0974C2 0065B 35F5C4 0001001000000000 11111111
0006 00000007AC5F 00001D290C19 000000.0.0000 000 047569.2.00BA 09814D 0065B 35F72A 0001001000000000 11111111
0007 00000007AC60 00001D290C1A 000000.0.0000 000 047569.2.00BB 098DD9 0065B 35F899 0001001000000000 11111111
0008 00000007AC61 00001D290C1B 000000.0.0000 000 047569.2.00BC 099A60 0065B 35F9FF 0001001000000000 11111111
0009 00000007AC62 00001D290C1C 000000.0.0000 000 047569.2.00BD 09A6A7 0065B 35FB66 0001001000000000 11111111
...


SMART shows 59240 reallocated sectors - I guess it might explain why it's busy? I've found various commands here to alter firmware behavior and perhaps make it accessible again, but I don't know which are safe/reversible.

Can anyone suggest some steps forward? I can provide output of other diagnostic commands if needed.
Top
 Profile  
 
SWM
 Post subject: Re: ST2000DM001 busy / inaccessible
PostPosted: February 14th, 2026, 13:30 
Offline

Joined: February 22nd, 2023, 13:49
Posts: 327
Location: Eastern Europe
If you want to copy the data, then:
https://forum.hddguru.com/viewtopic.php?f=1&t=45830
And make a sector-by-sector copy from the beginning to the first failure, and then from the end to the first failure. Do not mount the drive in the OS (use a bootable flash drive, etc.). If you only need a couple of files, mount them in the OS and try copying.
If you want to repair it, you don't have the necessary tools and knowledge.
https://forum.hddguru.com/viewtopic.php ... of#p317997
Top
 Profile  
 
SWM
 Post subject: Re: ST2000DM001 busy / inaccessible
PostPosted: February 14th, 2026, 13:50 
Offline

Joined: February 22nd, 2023, 13:49
Posts: 327
Location: Eastern Europe
If the data is IMPORTANT, it's best to contact a DR specialist immediately! And don't turn on HDD anymore.
Top
 Profile  
 
Seag3029
 Post subject: Re: ST2000DM001 busy / inaccessible
PostPosted: February 14th, 2026, 17:54 
Offline

Joined: February 14th, 2026, 10:41
Posts: 3
Location: Earth
SWM wrote:
If you want to copy the data, then:
https://forum.hddguru.com/viewtopic.php?f=1&t=45830


So, do you mean toggling these flags? DAR_ENABLED=0 / OFFLINE_SPARING_ENABLED=0 / DISABLE_IDLE_ACTIVITY=1 ?

Current flags:

Code:
F3 T>F"PerformanceFlags"
Byte:0464:       PerformanceFlags = 04 23
Byte:0464:           Bit:0, REDUCED_RAW_TRANSITION_FLUSH = 0
Byte:0464:           Bit:1, REDUCED_AV_RETRIES = 0
Byte:0464:           Bit:2, ID_READ_PARAMETERS_FROM_CAP = 1
Byte:0464:           Bit:4, VJIT_DISABLED = 0
Byte:0464:           Bit:5, ZERO_LATENCY_RD_ENABLED = 0
Byte:0465:           Bit:0, DAR_ENABLED = 1
Byte:0465:           Bit:1, OFFLINE_SPARING_ENABLED = 1
Byte:0465:           Bit:2, JIT3 = 0
Byte:0465:           Bit:3, JIT2 = 0
Byte:0465:           Bit:4, JIT1 = 0
Byte:0465:           Bit:5, JIT0 = 1
Byte:0465:           Bit:6, DISABLE_IDLE_ACTIVITY = 0
Byte:0465:           Bit:7, ENABLE_SELF_SEEK = 0


Quote:
And make a sector-by-sector copy from the beginning to the first failure, and then from the end to the first failure. Do not mount the drive in the OS (use a bootable flash drive, etc.). If you only need a couple of files, mount them in the OS and try copying.


Sure.

Quote:
If you want to repair it, you don't have the necessary tools and knowledge.
https://forum.hddguru.com/viewtopic.php ... of#p317997


Just to clarify, data on the disk isn't critical (likely already backed up elsewhere) so definitely not worth commercial DR. Nor do I want to repair it - just trying to image it once and then trash it.
Top
 Profile  
 
Seag3029
 Post subject: Re: ST2000DM001 busy / inaccessible
PostPosted: February 14th, 2026, 17:58 
Offline

Joined: February 14th, 2026, 10:41
Posts: 3
Location: Earth
:?:
SWM wrote:
If you want to copy the data, then:


So, do you mean toggling these flags? DAR_ENABLED=0 / OFFLINE_SPARING_ENABLED=0 / DISABLE_IDLE_ACTIVITY=1 ?

Current flags:

Code:
F3 T>F"PerformanceFlags"
Byte:0464:       PerformanceFlags = 04 23
Byte:0464:           Bit:0, REDUCED_RAW_TRANSITION_FLUSH = 0
Byte:0464:           Bit:1, REDUCED_AV_RETRIES = 0
Byte:0464:           Bit:2, ID_READ_PARAMETERS_FROM_CAP = 1
Byte:0464:           Bit:4, VJIT_DISABLED = 0
Byte:0464:           Bit:5, ZERO_LATENCY_RD_ENABLED = 0
Byte:0465:           Bit:0, DAR_ENABLED = 1
Byte:0465:           Bit:1, OFFLINE_SPARING_ENABLED = 1
Byte:0465:           Bit:2, JIT3 = 0
Byte:0465:           Bit:3, JIT2 = 0
Byte:0465:           Bit:4, JIT1 = 0
Byte:0465:           Bit:5, JIT0 = 1
Byte:0465:           Bit:6, DISABLE_IDLE_ACTIVITY = 0
Byte:0465:           Bit:7, ENABLE_SELF_SEEK = 0


Quote:
And make a sector-by-sector copy from the beginning to the first failure, and then from the end to the first failure. Do not mount the drive in the OS (use a bootable flash drive, etc.). If you only need a couple of files, mount them in the OS and try copying.


Sure.

Quote:
If you want to repair it, you don't have the necessary tools and knowledge.


Just to clarify, data on the disk isn't critical (likely already backed up elsewhere) so definitely not worth commercial DR. Nor do I want to repair it - just trying to image it once and then trash it.
Top
 Profile  
 
Hardcore Games
 Post subject: Re: ST2000DM001 busy / inaccessible
PostPosted: February 14th, 2026, 17:59 
Offline

Joined: March 8th, 2025, 18:07
Posts: 111
Location: Canada
That disk is probably 20 years old, I recall having one back then before migrating to 4TB and larger disks

_________________
Orico DS500C3-US-BK 5-disk 3.5" SATA, iTGZ 4x M.2 2280 Thunderbolt enclosure NVMe/SATA, etc. etc.
Top
 Profile  
 
SWM
 Post subject: Re: ST2000DM001 busy / inaccessible
PostPosted: February 15th, 2026, 3:10 
Offline

Joined: February 22nd, 2023, 13:49
Posts: 327
Location: Eastern Europe
Quote:
So, do you mean toggling these flags? DAR_ENABLED=0 / OFFLINE_SPARING_ENABLED=0 / DISABLE_IDLE_ACTIVITY=1 ?

Yes. And Ctrl R to turn on SATA interface.
Top
 Profile  
 
SWM
 Post subject: Re: ST2000DM001 busy / inaccessible
PostPosted: February 15th, 2026, 3:18 
Offline

Joined: February 22nd, 2023, 13:49
Posts: 327
Location: Eastern Europe
Quote:
I recall having one back then before migrating to 4TB and larger disks

Maybe it's easier to put a mirror in front of you and admire yourself...
Top
 Profile  
 
Hardcore Games
 Post subject: Re: ST2000DM001 busy / inaccessible
PostPosted: February 15th, 2026, 21:56 
Offline

Joined: March 8th, 2025, 18:07
Posts: 111
Location: Canada
SWM wrote:
Quote:
I recall having one back then before migrating to 4TB and larger disks

Maybe it's easier to put a mirror in front of you and admire yourself...


I buy new hard disks frequently as I like to have backups of backups

_________________
Orico DS500C3-US-BK 5-disk 3.5" SATA, iTGZ 4x M.2 2280 Thunderbolt enclosure NVMe/SATA, etc. etc.
Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  Page 1 of 1
  [ 9 posts ] 

Main » Forums home » Conventional hard drives

All times are UTC - 5 hours [ DST ]

Who is online

Users browsing this forum: No registered users and 34 guests

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Switch to mobile style
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group