Seagate Barracuda ST2000Dl003 doesn't work properly anymore

[daniel.krause777]

Good day!
Since I shutted down my QNAP after a long time and wanted to turn on again some weeks later, the hard drive is not recognized by QNAP anymore. I then plugged it into a USB adapter to my Laptop and it spins normally and Windows is recognizing it as a RAW partition device which I should format (maybe because it's a ext formatting). Testdisk won't start bc it freezes when tries to discover the drives.
I then downloaded EASEUS data recovery and it can search and find some files. Everytime at exactly the same moment the programm eventually freezes. But when I turn the HDD off and on again the programm continues to search for recoverable data. Then there is another "barrier moment" when I need to turn off and on again and it starts searching for data again, then without freezing again (actually I let it run for 1hr only).
Windows partitioning tool freezes after some time when I try to access the data. Gparted also freezes when it tries to discover the drives.
I tried the Seagate repair tool and it freezes after 10% of bad sector recovery.
What is most likely the cause of this behaviour and what would you say is the best way to fix it. I don't want to spend 70$ for data recovery programm 🙁

 

[seagate_surfer]

Hello daniel.krause777. Sorry to see you are having this situation. When you say you ran the Seagate repair tool did you mean Seatools? If not, go ahead and run Seatools as it will tell you the health of the drive.

 

[daniel.krause777]

Thanks for the quick answer. Yes, I used Seatools. I could run the quick self test and drive successfully passed. I couldn't find a SMART summary, just general information but nothing related to health.

 

[seagate_surfer]

Thanks for the quick answer. Yes, I used Seatools. I could run the quick self test and drive successfully passed. I couldn't find a SMART summary, just general information but nothing related to health.

If Seatools did not give you a warning or error after the scan most likely the drive is OK. Suggestion would be try it in another computer and see if the same symptoms appear. Maybe another user may chime in with another idea.

 

[daniel.krause777]

Thanks for the quick answer. Yes, I used Seatools. I could run the quick self test and drive successfully passed. I couldn't find a SMART summary, just general information but nothing related to health.

If Seatools did not give you a warning or error after the scan most likely the drive is OK. Suggestion would be try it in another computer and see if the same symptoms appear. Maybe another user may chime in with another idea.

Hey!
I plugged it into an free SATA slot on a Windows2012 server. After booting up the HDD was not recognized, I started Seatools and turned the HDD off and on again by pulling the power supply. and it was recognized then. I also could start SMART Test which was passed successfully. After starting the quick repair [strike]it stucked again at 10%. Drive becomes inaccessible.[/strike] it failes test after some time. Drive is still accessible.

I booted then an Ubuntu 18.04 and started Testdisk. The drive first was not found by fdisk but then I turned it off and on and Testdisk and fdsik both discoverd it successfully. Testdisk then failed to analyze and search for lost partition tables with error: "read error at <all> lba". Other analyzing options also failed.
Problem seems to be that the drive is not accessable after a few time running [strike](getting warm?)[/strike] or when some bad sector is entered.

 

[seagate_surfer]

Thanks for the quick answer. Yes, I used Seatools. I could run the quick self test and drive successfully passed. I couldn't find a SMART summary, just general information but nothing related to health.

If Seatools did not give you a warning or error after the scan most likely the drive is OK. Suggestion would be try it in another computer and see if the same symptoms appear. Maybe another user may chime in with another idea.

Hey!
I plugged it into an free SATA slot on a Windows2012 server. After booting up the HDD was not recognized, I started Seatools and turned the HDD off and on again by pulling the power supply. and it was recognized then. I also could start SMART Test which was passed successfully. After starting the quick repair [strike]it stucked again at 10%. Drive becomes inaccessible.[/strike] it failes test after some time. Drive is still accessible.

I booted then an Ubuntu 18.04 and started Testdisk. The drive first was not found by fdisk but then I turned it off and on and Testdisk and fdsik both discoverd it successfully. Testdisk then failed to analyze and search for lost partition tables with error: "read error at <all> lba". Other analyzing options also failed.
Problem seems to be that the drive is not accessable after a few time running [strike](getting warm?)[/strike] or when some bad sector is entered.

Hi daniel.krause777, looking further into this it very well could be the PCB board on the drive by the description you gave. That is why it worked sometimes and others not. Could very well be an electrical problem. Suggestion would be back up the information if you have not done so yet as this drive may fail. Here is the warranty link in case you need it. Sorry to be the bearer of bad news on this.

 

[Louise Porkolt]

hi there,

if it's the motherboard of the HDD then you might considder as last resort:
1. place the HDD in a cooled area (freezer) to work in a lower temperature environment. If this does work longer than before but not enough to recover all data you might consider the next step:


2.remove the PCB-board and let it warm up in the oven for about 10 mins at 190°C.

Usually I heat up only the faulthy part but we don't know which one that is, so melting the tin keeping the components on the board could repair the faulthy crack in the tin.

(However this worked for me (85%) and some people on Tomshardware.com, do this on your own risk, I'm not responsible for destruction from your own actions.)

Let us know how you managed,

Kind regards, Louise.

 

[mdd1963]

Once drives start 'heading south', there is often little than can be done....; if this was some RAID 5-equivalent array in the QNAP, insert a new drive so the rebuild can begin, and, pray you do not lose another during the rebuild process...