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

All times are UTC - 5 hours [ DST ]




Post new topic Reply to topic  [ 7 posts ] 
Author Message
 Post subject: The next Seagate ST3000DM001 issue
PostPosted: September 15th, 2015, 18:55 
Offline

Joined: September 15th, 2015, 18:20
Posts: 2
Location: Germany
Hi guys,

I'm new here and want to share my experience with you.
So annoyed with the reliability of Seagate Hard Drives, I like to call the short life term of the Seagate Barracuda Series not watergate, not nipplegate, not bendgate..... I like to call this crap just "Seagate".

So let me explain you my experiences:

I used a Seagate Barracuda ST3000DM001 9YN166-500 with 3 TB in my Synology Diskstation DS112+ for two years.
I was very happy with it until I suddenly got an email from the disk station that the connection to the Diskstation has been lost. Hours later when I was home I diagnosed my Diskstation and found out that it showed an amber status LED blinking.

I decided to just restart my Diskstation and after the boot sequence it ended with a beep and again a amber coloured blinking status LED.

The Diskstation Windows Tool told me that the hard drive has no Diskstation operating system installed. A reinstall of the operating system would delete all my data of my hard drive. Abort!
So I opened the Diskstation and took out my Seagate Barracuda hard drive to diagnose it directly on my PC.
There was the second problem: My PC BIOS couldn't detect it.......

Hours and hours of googleing the issues with this HDD model I decided to log the HDDs status via a USB TTL Adapter through the Serial Port of the Hard Drive.

There are tutorials to do this. My hard drive doesn't like to get logged with the head connectors covered by a piece of paper. So I tried to get a F3 connection to my HDD the PCB attached as it is from stock. That was successful, I got a F3 connection and could log all the status reports into my Terminal Tool.

The log I got was looking okay until a loop of "ProcessRWError -Read- @ LBA.....". At the end I was able to get "F3 1>".
Here I deleted the Smart Table and checked the heads. They were okay.

After a further research I got this tutorial and performed it via a Knoppix Live DVD: http://blog.asiantuntijakaveri.fi/2013/09/updating-seagate-st3000dm001-9yn166-to.html.
Firmware before update (sticker on my HDD): CC4B - Firmware after update: CC4H

Now I get this log when powering on the HDD:
Quote:
Boot 0x40M
Spin Up[0x000065B4][0x00006A20][0x00006E8C]
Trans.

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

MCMainPOR: Start:
Check MCMT Version: Current
MCMainPOR: Non-Init Case
MC Seg Disc and Cache Nodes: 40125B20 40122EF8
Seg Write Preamble VBM start: 0000204A end: 00002091
Footer - start: 00002093 end: 000020DA
Seg Read Preamble VBM - start: 000020DC end: 00002123
Footer - start: 00002125 end: 0000216C
Reconstruction: MCMT Reconstruction Start
Max number of MC segments 0A61
Nonvolatile MCMT sequence number 000052BB
[RSRS] 0137
Reconstruction: Completed 1:
[MCMTWS]
MCMainPOR: MCTBufferPtr->Header.MCStateFlagsDisc = 00000041
MCMainPOR: MCTBufferPtr->Header.MCTStateFlags = 0000002A
MCMainPOR: MCStateFlags = 00000041

MCMainPOR: Feature Enabled...

Starting LBA of RW Request=0000000000087E66 Length=000001B0
ProcessRWError -Read- at LBA 0000000000087E66 Sense Code=43110081
Starting LBA of RW Request=0000000000087E66 Length=000001B0
ProcessRWError -Read- at LBA 0000000000087E67 Sense Code=43110081
Starting LBA of RW Request=0000000000087E66 Length=000001B0
ProcessRWError -Read- at LBA 0000000000087E68 Sense Code=43110081
Starting LBA of RW Request=0000000000087E66 Length=000001B0
ProcessRWError -Read- at LBA 0000000000087E69 Sense Code=43110081
MC Internal LPC Process
Starting LBA of RW Request=0000000000087E6A Length=000001AC
ProcessRWError -Read- at LBA 0000000000087E6A Sense Code=43110081
Starting LBA of RW Request=0000000000087E6E Length=000001A8
ProcessRWError -Read- at LBA 0000000000087E6E Sense Code=43110081
Starting LBA of RW Request=0000000000087E6E Length=000001A8
ProcessRWError -Read- at LBA 0000000000087E6F Sense Code=43110081
Starting LBA of RW Request=0000000000087E6E Length=000001A8
ProcessRWError -Read- at LBA 0000000000087E70 Sense Code=43110081
Starting LBA of RW Request=0000000000087E6E Length=000001A8

ProcessRWError -Read- at LBA 0000000000087E71 Sense Code=43110081
Starting LBA of RW Request=0000000000087E6E Length=000001A8
ProcessRWError -Read- at LBA 0000000000087E72 Sense Code=43110081
Starting LBA of RW Request=0000000000087E6E Length=000001A8
ProcessRWError -Read- at LBA 0000000000087E73 Sense Code=43110081
Starting LBA of RW Request=0000000000087E6E Length=000001A8
ProcessRWError -Read- at LBA 0000000000087E74 Sense Code=43110081
Starting LBA of RW Request=0000000000087E6E Length=000001A8
ProcessRWError -Read- at LBA 0000000000087E75 Sense Code=43110081
Starting LBA of RW Request=0000000000087E6E Length=000001A8
ProcessRWError -Read- at LBA 0000000000087E76 Sense Code=43110081
Starting LBA of RW Request=0000000000087E6E Length=000001A8
ProcessRWError -Read- at LBA 0000000000087E77 Sense Code=43110081
Starting LBA of RW Request=0000000000087E6E Length=000001A8

ProcessRWError -Read- at LBA 0000000000087E78 Sense Code=43110081
Starting LBA of RW Request=0000000000087E6E Length=000001A8
ProcessRWError -Read- at LBA 0000000000087E79 Sense Code=43110081
Starting LBA of RW Request=0000000000087E6E Length=000001A8
ProcessRWError -Read- at LBA 0000000000087E7A Sense Code=43110081
Starting LBA of RW Request=0000000000087E7E Length=00000198
ProcessRWError -Read- at LBA 0000000000087E7E Sense Code=43110081
Starting LBA of RW Request=0000000000087E7E Length=00000198
ProcessRWError -Read- at LBA 0000000000087E7F Sense Code=43110081
Starting LBA of RW Request=0000000000087E82 Length=00000194
ProcessRWError -Read- at LBA 0000000000087E83 Sense Code=43110081
Starting LBA of RW Request=0000000000087E82 Length=00000194
ProcessRWError -Read- at LBA 0000000000087E85 Sense Code=43110081
Starting LBA of RW Request=0000000000087E86 Length=00000190
ProcessRWError -Read- at LBA 0000000000087E86 Sense Code=43110081
Starting LBA of RW Request=0000000000087E8A Length=0000018C
ProcessRWError -Read- at LBA 0000000000087E8A Sense Code=43110081
Starting LBA of RW Request=0000000000087E8A Length=0000018C
ProcessRWError -Read- at LBA 0000000000087E8B Sense Code=43110081
Starting LBA of RW Request=0000000000087E8A Length=0000018C
ProcessRWError -Read- at LBA 0000000000087E8C Sense Code=43110081
Starting LBA of RW Request=0000000000087E8A Length=0000018C
ProcessRWError -Read- at LBA 0000000000087E8D Sense Code=43110081
Starting LBA of RW Request=0000000000087E8A Length=0000018C
ProcessRWError -Read- at LBA 0000000000087E8E Sense Code=43110081
Starting LBA of RW Request=0000000000087E8A Length=0000018C
ProcessRWError -Read- at LBA 0000000000087E8F Sense Code=43110081
Starting LBA of RW Request=0000000000087E8A Length=0000018C
ProcessRWError -Read- at LBA 0000000000087E90 Sense Code=43110081
Starting LBA of RW Request=0000000000087E8A Length=0000018C
ProcessRWError -Read- at LBA 0000000000087E91 Sense Code=43110081
Starting LBA of RW Request=0000000000087E8A Length=0000018C
ProcessRWError -Read- at LBA 0000000000087E92 Sense Code=43110081

Starting LBA of RW Request=0000000000087E8A Length=0000018C
ProcessRWError -Read- at LBA 0000000000087E93 Sense Code=43110081
Starting LBA of RW Request=0000000000087E8A Length=0000018C
ProcessRWError -Read- at LBA 0000000000087E94 Sense Code=43110081
Starting LBA of RW Request=0000000000087E8A Length=0000018C
ProcessRWError -Read- at LBA 0000000000087E95 Sense Code=43110081
Starting LBA of RW Request=0000000000087E8A Length=0000018C
ProcessRWError -Read- at LBA 0000000000087E96 Sense Code=43110081
Starting LBA of RW Request=0000000000087E8A Length=0000018C
ProcessRWError -Read- at LBA 0000000000087E97 Sense Code=43110081
Starting LBA of RW Request=0000000000087E8A Length=0000018C
ProcessRWError -Read- at LBA 0000000000087E98 Sense Code=43110081
Starting LBA of RW Request=0000000000087E8A Length=0000018C
ProcessRWError -Read- at LBA 0000000000087E9B Sense Code=43110081
Starting LBA of RW Request=0000000000087E8A Length=0000018C
ProcessRWError -Read- at LBA 0000000000087E9C Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000087EA1 Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000087EAF Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000087EB0 Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000087EDB Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000087EE1 Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000087EE5 Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000087EE6 Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000087EE7 Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000087EF9 Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000087EFA Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000087EFB Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000087F71 Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000087F84 Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000087F8D Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000087F8E Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000087F9E Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000087FA0 Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000087FA1 Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000087FA2 Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000087FAB Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000087FAC Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000087FAF Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000087FB2 Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000087FB3 Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000087FB5 Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000087FBB Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000087FC1 Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000087FC2 Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000087FC9 Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000087FD2 Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000087FD3 Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000087FD5 Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000087FD6 Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000087FDD Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000087FE2 Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000087FE5 Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000087FE6 Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000087FE7 Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000087FFC Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000087FFE Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000087FFF Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000088000 Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000088001 Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000088002 Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000088003 Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000088004 Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000088005 Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000088006 Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000088007 Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000088008 Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000088009 Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 000000000008800A Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 000000000008800B Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 000000000008800C Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 000000000008800E Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000088010 Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000088011 Sense Code=43110081
Starting LBA of RW Request=0000000000087E9E Length=00000178
ProcessRWError -Read- at LBA 0000000000088012 Sense Code=43110081
Internal SavePersistentInfo Triggered
(ConfigChange) SATA Reset

ASCII Diag mode


F3 T>


This is my head test:
Quote:
F3 1>/7


F3 7>X

Head 00 Resistance 0147
Head 01 Resistance 014F
Head 02 Resistance 0121
Head 03 Resistance 0169
Head 04 Resistance 0191
Head 05 Resistance 0175


F3 7>


I still cannot access to my data :(
Is there a possibility to get my files back? I unfortunately have no backups of these files. I know, that's a big fault but I learned from it.

They say that every drive has his unique BIOS IC which contains the drive specific parameters. So I need to swap the BIOS IC when I buy a donor PCB.
I updated the firmware like described above. Has it flashed the BIOS IC or updated the firmware on the HDD partition? If BIOS IC: Could the drive specific parameters have been overwritten with wrong values due to a incompatible BIOS version? The bootable Seagate CC4H Update CD said to me that model matches but firmware version is mismatched. I force updated it via the Knoppix DVD. The reason is, that in many forums they say that in case of the symptoms that my HDD shows maybe the firmware is corrupted. So I wanted to clean up the firmware with a reflash. I would like to get my old version back and am hoping that I did not destroy the specific drive parameters inside the BIOS

Earlier when I clicked on "Disk Info" within the Seagate Tools program, I got some informations about my drive. Now after the update it shows:
Quote:
Receive T Series Data Incorrect



I hope you can help me with my problem to find a solution.

Thanks for reading and your interest.

Best regards,
Tolga

Here is a pic of my hdd:

Image


Top
 Profile  
 
 Post subject: Re: The next Seagate ST3000DM001 issue
PostPosted: September 15th, 2015, 21:58 
Offline
User avatar

Joined: April 3rd, 2011, 0:19
Posts: 2003
Location: Providence, RI
I'm not exactly sure based on that terminal output, but it might be an issue with the auto reallocation. I'd probably first try disabling everything in module 93, though I'm not sure how you'd accomplish that with just a terminal adapter.

Maybe try one or more of the following:

T>F"RWRecoveryFlags",00,22
T>F"BGMSFlags",00,22
T>F"PerformanceFlags",043C,22
T>F,,22 (resets it to default after if it doesn't help)

_________________
Data Medics - Hard Drive, SSD, and RAID Data Recovery Service Company


Top
 Profile  
 
 Post subject: Re: The next Seagate ST3000DM001 issue
PostPosted: September 16th, 2015, 4:26 
Offline

Joined: September 3rd, 2015, 21:04
Posts: 32
Location: The Internet
Try waiting not pressing any keys (like ctrl+z) at all until the reallocation has ended and you get the Sata reset, then see if the drive detects. If not get T prompt and try going straight back into ATA mode with Ctrl+r and see if it detects now. If not at terminal prompt try clearing glist with "i4,1,22", also edit the congen settings as described above then change back again (Ctrl+r) without repowering.

If you get the drive working copy all the data off as quickly as possible while you still can!


Top
 Profile  
 
 Post subject: Re: The next Seagate ST3000DM001 issue
PostPosted: September 16th, 2015, 7:30 
Offline
User avatar

Joined: December 8th, 2013, 4:48
Posts: 838
Location: Pakistan
since it is DM series, i would strongly suggest you to send disk to a reputed DR company and get the price estimate first later you can decide whether or not proceed with DIY.

_________________
Data Recovery Pakistan


Top
 Profile  
 
 Post subject: Re: The next Seagate ST3000DM001 issue
PostPosted: September 16th, 2015, 8:23 
Offline
User avatar

Joined: May 13th, 2010, 11:17
Posts: 2821
Location: Kuwait
MindMergepk wrote:
since it is DM series, i would strongly suggest you to send disk to a reputed DR company and get the price estimate first later you can decide whether or not proceed with DIY.



what is it with DM Series?

anything special here we are not aware of?

_________________
Kuwait Data Recovery - UNIX GTC
The only reason for time is so that everything doesn't happen at once. By: Albert Einstein


Top
 Profile  
 
 Post subject: Re: The next Seagate ST3000DM001 issue
PostPosted: September 16th, 2015, 9:36 
Offline

Joined: September 15th, 2015, 18:20
Posts: 2
Location: Germany
I think I had a little bit of success today.
I followed the tips which are described above.

After putting in the commands into the Terminal, I plugged in the SATA Cable into the hard drive, the typical sound, which appears when you plug in a USB device into the USB Port, was hearable.
Windows showed 2 popups that I have to format the hard drive to use it. I think it is because the 2 partitions on the HDD are Unix partitions and Windows can't read them without special drivers. Synology Diskstations create 2 partitions on hard drives. The first one is for the Diskstation OS and the second one for all my data.

So far so good. Before I could open a data recovery tool, again the sound (like plugging out a USB device) appeared and the disk was away again :(

I am at work now and will try out the same procedure with a LINUX Live DVD, when I am at home.


Top
 Profile  
 
 Post subject: Re: The next Seagate ST3000DM001 issue
PostPosted: September 16th, 2015, 11:40 
Offline

Joined: August 18th, 2010, 17:35
Posts: 3669
Location: Massachusetts, USA
The drive has at least one suspect degraded surface, which naturally causes the firmware to attempt dealing with it through reallocation. It is very possible that the read-write component on that surface may not work all that well. Careful here in how much buggering around takes place. That drive is bound to fail permanently soon. So, get your data asap, though a clone is a much better option.

_________________
Hard Disk Drive (HDD), Solid State Drive (SSD, SATA, NVMe, etc), USB Flash Drive and RAID Data Recovery Specialist in Massachusetts


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

All times are UTC - 5 hours [ DST ]


Who is online

Users browsing this forum: No registered users and 77 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