All times are UTC - 5 hours [ DST ]




Post new topic Reply to topic  [ 4 posts ] 
Author Message
 Post subject: Has my Seagate ST2000DM001 finally died ?
PostPosted: July 26th, 2021, 9:46 
Offline

Joined: July 26th, 2021, 7:10
Posts: 2
Location: Paris
Hi gurus,

I'm just a regular IT enthusiast and I'd like some insight on to whether my drive has permanently failed.
The drive is an 11y/o Seagate ST2000DM001 with around 20kH power-on hours.
It's been used to store some personal (important) data as well as a scratch space for program installs, games and such.
I will mention now that I was able to partially get my data back already (file copy), but not a full image of the disk. I had also made (not-so)-up-to-date backups of the important bits (way) before it started failing, so please don't be pulling your hair out reading me.
I'm afraid this post is going to be fairly long as I'm going to be detailing how I tortured the drive so far.

To fill you in, it started showing signs of failure last year with i/o errors and the reallocated sector count shooting up in the smart data. Since then, I started using another drive for scratch data and it's been siting in my desktop computer, plugged yet idle at most times. Then, starting 3 or 4 months ago, the drive wouldn't always be detected by the bios on startup and I had to cycle power-ons multiple times before seeing it detected. Until someday when it was no longer being detected, no matter how many power cycles I did.

At this point, I grabbed a usb-serial adapter and this is the output I got :
Code:
Boot 0x40M
Spin Up
TCC-001C[0x000042F9][0x00026F7C][0x000273E8][0x00027854]
Trans.

Rst 0x40M
MC Internal LPC Process
Spin Up
TCC-001C
(P) SATA Reset

MCMainPOR: Start:
Check MCMT Version: Current
MCMainPOR: Non-Init Case
MCMainPOR: EXCEPTION: MCMT PRI copy corrupt
MCMainPOR:  MCMT SEC copy valid
Reconstruction: MCMT Reconstruction Start
  Max number of MC segments 0A61
Nonvolatile MCMT sequence number 0012CF8E
[RSRS] 0228
Starting LBA of RW Request=000000000001BE58  Length=00000747
ProcessRWError -Read-   at LBA 000000000001BE58  Sense Code=43110081!

Starting LBA of RW Request=000000000001BE58  Length=00000747
ProcessRWError -Read-   at LBA 000000000001BE59  Sense Code=43110081!

ProcessRWError -Read-   at LBA 000000000001BF22  Sense Code=40000087
ProcessRWError -Read-   at LBA 000000000001BF2D  Sense Code=40000087
ProcessRWError -Read-   at LBA 000000000001BF2F  Sense Code=40000087
InitiateMarkPendingReallocateRequest for disc_lba: 000000000001BF2F!

Reconstruction: Completed 1:
[MCMTWS]
Rst 0x40M
MC Internal LPC Process
Spin Up
TCC-001C
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
...

I also noticed the '43110081!' codes where not consistently produced. I had boot-up outputs with none of them, or at different places. The '40000087' codes were in comparison always for the exact same locations. Not sure if that matters though.

After looking up these logs here and there, I came to the conclusion I had to short the read channel to get it detected by the bios again. Did so and it worked. I've attached the serial output (hdd_fix.txt) if you'd like to check what it did when I shorted the 2 pins.

At this point, I plugged in another 4TB drive with enough free space and booted a SysRescueCD - to prevent my system from automatically trying to mount the filesystem. The 2 disks were showing up the OS. Feeling lucky, I then tried to mount the filesystem and it worked as well. My guess was that going for a file-copy would be the fastest and a reliable way to backup only the important data first, since I had made very little writes and overall accesses to these parts of the file tree over the past years. It took time, a lot of time, bandwidth was at best a few MB/s, hundreds of Kb/s at worst. Eventually, I got the files backed up on the other drive.

From then, I thought I would try to recover the remaining data by imaging the drive with drescue, but together with the previous backup, I had no more space available on the 4TB drive for a full 2TB image. I shut everything down waiting another day for a fresh drive to arrive.

New drive arrived, I did everything as before, had to short again for the seagate drive to be detected. I ran ddrescue with only '-n' as I read (not in this forum) it was recommended for a first pass. I kept the '-r' for a later run. It ran for 10min straight, went over 30-40GB and claimed to have recovered as much (no errors yet). After 10 mins the throughput dropped to 0 and only the error count kept incrementing (yikes).
The full run ended up in approx 20 mins, with no data recovered past the 10min mark.

Without any proper thinking (late night time), I have rebooted the system to try again, but shorting the read channel no longer works - I can't get my seagate drive detected anymore.

Here's the output from serial for a normal power cycle :
Quote:
Boot 0x40M
Spin Up
TCC-0019[0x00026F7C][0x000273E8][0x00027854]
Trans.

Rst 0x40M
MC Internal LPC Process
Spin Up
TCC-0019
(P) SATA Reset

MCMainPOR: Start:
Check MCMT Version: Current
MCMainPOR: Non-Init Case
MCMainPOR: EXCEPTION: MCMT PRI copy corrupt
MCMainPOR: MCMT SEC copy valid
Reconstruction: MCMT Reconstruction Start
Max number of MC segments 0A61
Nonvolatile MCMT sequence number 0012CFA2
[RSRS] 0233
ProcessRWError -Read- at LBA 000000000001C748 Sense Code=40000087[RAA]!

ProcessRWError -Read- at LBA 000000000001C81D Sense Code=40000087
ProcessRWError -Read- at LBA 000000000001C822 Sense Code=40000087
InitiateMarkPendingReallocateRequest for disc_lba: 000000000001C822!

Reconstruction: Completed 1:
[MCMTWS]
Rst 0x40M
MC Internal LPC Process
Spin Up
TCC-0019
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
...


and here's one when I short :

Quote:
Boot 0x40M
Spin Up
TCC-001A[0x000042F9][0x00026F7C][0x000273E8][0x00027854]
Trans.

Rst 0x40M
MC Internal LPC Process
Spin Up
TCC-001A
(P) SATA Reset

MCMainPOR: Start:
Check MCMT Version: Current
MCMainPOR: Non-Init Case
MCMainPOR: EXCEPTION: MCMT PRI copy corrupt
MCMainPOR: MCMT SEC copy valid
Reconstruction: MCMT Reconstruction Start
Max number of MC segments 0A61
Nonvolatile MCMT sequence number 0012CFA2
[RSRS] 0233
ProcessRWError -Read- at LBA 000000000001C748 Sense Code=40000087
InitiateMarkPendingReallocateRequest for disc_lba: 000000000001C748!

Reconstruction: EXCEPTION: Seg Read Fail: Status = 0000
Continuing after error
Reconstruction: Completed 1:
[MCMTWS]
Rst 0x40M
MC Internal LPC Process
Spin Up
TCC-001A
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
...

Am I just clumsy and not shorting properly the 2 pins ?

The 2 outputs look different, but I can't find any info on whether I can get it detected again.
Would you, gurus, have some insight on this ?
Is there any evidence at this point the drive is toast ?
Is there still a way for me to image that drive ? Should I give up on the unrecovered and unimportant data ? Was I already extremely lucky to go this far with such unprofessional methods and guesswork ?

Also, do you think this drive may be fixed and repurposed as a scratch disk solely ?
My idea was, that if the drive is not complete junk and good for electronic waste, I could perhaps find some use of it. I have applications where I do not care about recovering data at all if it were to fail again.

Thank you very much for reading this whole. The post is probably too long for what's inside, and may not be useful to other readers, so big thanks again.
I'd understand if you're not willing to answer or spend time on this thread - as one could view the issue as already fixed in some way.
Finally, my HDD issue brought me to this forum where I found very valuable informations - to all contributors, I could recover some data (and finish toasting my drive?) thanks to you ; I'm so grateful.

Have a nice day you all, cheers.


Attachments:
hdd_fix.txt [3.48 KiB]
Downloaded 293 times
Top
 Profile  
 
 Post subject: Re: Has my Seagate ST2000DM001 finally died ?
PostPosted: July 27th, 2021, 2:49 
Offline

Joined: November 7th, 2020, 5:31
Posts: 1084
Location: The_UK
I think you already know you should have dealt with the drive back when it first showed signs of failure, I wont labour the point.

If there's no value to the data on the drive bin it, a drive once failed in my opinion is not worth using for anything. You can try shorting the read channels again a few times but this reads like it needs tweaking and a little work to encourage it to give up it's data, and that's really a pro job - assuming you haven't already killed the heads.

Someone might talk you through some terminal commands but without backing up the rom you may just end up with e-waste.

_________________
Data Recovery Services in the UK.
https://www.usbrecovery.co.uk/


Top
 Profile  
 
 Post subject: Re: Has my Seagate ST2000DM001 finally died ?
PostPosted: July 27th, 2021, 3:43 
Offline

Joined: July 26th, 2021, 7:10
Posts: 2
Location: Paris
I tried shorting the read channel for a fair bit of time already with no success so far.
Even if I was able to get it detected again, is there anything I can do to help the ddrescue go through this time ?
I did not mention it, but I've made a backup of the drive's rom with a spi flasher. Before getting a look at the serial output, I tried a pcb swap (was almost free).


Top
 Profile  
 
 Post subject: Re: Has my Seagate ST2000DM001 finally died ?
PostPosted: July 27th, 2021, 8:20 
Offline

Joined: November 7th, 2020, 5:31
Posts: 1084
Location: The_UK
The most recent error is pointing towards media cache issues.

Code:
MC Internal LPC Process
Spin Up
TCC-001C
LED:00000047 FAddr:FFFFFFFE


Have a look for f3romexplorer that might help as might "seagate regenerate media cache", but be warned blindly following instructions online might brick your drive.

_________________
Data Recovery Services in the UK.
https://www.usbrecovery.co.uk/


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 4 posts ] 

All times are UTC - 5 hours [ DST ]


Who is online

Users browsing this forum: Google [Bot], juanato and 57 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:  
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group