Gradius2

The Solution for Seagate 7200.11 HDDs

4,868 posts in this topic

It would appear that your drive has entered a “locked” mode and therefore inaccessible, clicking continuously.

The locking is usually caused by media issues (bad sectors) and the firmware then “locks” to prevent further damage, it could also be down to corrupt smart or defect list(s).

This is not the same thing as the publicised “firmware bug” which affected drives of FW version SD15, DE12 and MX15 (yours is SD33), where the drive spins up and sounds normal (yours clicks).

The price for recovery of this drive would be £249 + VAT which would include a USB hard drive with your data on, and shipping of the data drive.

Of course, if we are unsuccessful there would be no charge.

so what do you guys think, ask for it back without this recovery....and carry out the BSY error fix...or is it really sounding like thier advice is the only way out?

That *might* be true (or they might be looking to make a quick buck), but in my experience if a Seagate 7200.11 with firmware prior to SD1A is suddenly not being seen in Bios (and was not dropped just prior to this occurrence), it is mostly (yes, there are exceptions) the BSY bug and not bad sectors. By trying the fix, you might save yourself £247 (or lose £1.99 if it is not BSY). As you have already bought the cable, it will cost you only 20 minutes of your time trying it (the £1.99 already spent).

Since the fix is just some sort of general reset, you shouldn't damage your drive trying it, even if it is not the case (unless the drive is making funny noises as if the internals are breaking, in which case it is not recommended, but from your description, this is NOT the case).

Anyway, your choice. Choices, choices... (but, as jaclaz always says, choose wisely) ;)

Edited by BlouBul
0

Share this post


Link to post
Share on other sites

It would appear that your drive has entered a “locked” mode and therefore inaccessible, clicking continuously.

The locking is usually caused by media issues (bad sectors) and the firmware then “locks” to prevent further damage, it could also be down to corrupt smart or defect list(s).

This is not the same thing as the publicised “firmware bug” which affected drives of FW version SD15, DE12 and MX15 (yours is SD33), where the drive spins up and sounds normal (yours clicks).

The price for recovery of this drive would be £249 + VAT which would include a USB hard drive with your data on, and shipping of the data drive.

Of course, if we are unsuccessful there would be no charge.

so what do you guys think, ask for it back without this recovery....and carry out the BSY error fix...or is it really sounding like thier advice is the only way out?

That *might* be true (or they might be looking to make a quick buck), but in my experience if a Seagate 7200.11 with firmware prior to SD1A is suddenly not being seen in Bios (and was not dropped just prior to this occurrence), it is mostly (yes, there are exceptions) the BSY bug and not bad sectors. By trying the fix, you might save yourself £247 (or lose £1.99 if it is not BSY). As you have already bought the cable, it will cost you only 20 minutes of your time trying it (the £1.99 already spent).

Since the fix is just some sort of general reset, you shouldn't damage your drive trying it, even if it is not the case (unless the drive is making funny noises as if the internals are breaking, in which case it is not recommended, but from your description, this is NOT the case).

Anyway, your choice. Choices, choices... (but, as jaclaz always says, choose wisely) ;)

thanks for this, its the way ive been thinking too...would just need the drive returned to me, then to carry out the fix.

as you said, its a general reset so it might just prove to be the way out, saving afew bucks...easy for a data recovery company to go high on a qoute especailly if they think the consumer has either 1) no experience whatsover 2)done no reseacrh whatsoever

thankfully for me, with the aid of guys like Bloubul and jaclaz to name but only a few, ive got some good brains helping me out!

0

Share this post


Link to post
Share on other sites

OK my drive died quite a long time ago and wrote it off but after a while decided to see if it worked after a few system updates and still broken. I searched the net for a bit then came across this site and decided to do the fix(mine was stuck in the BSY state). All my parts arrived today built the rig and followed the guide and it now works. Thank you guys for your hard work and very easy to follow guides by all the people.

Many thanks again jamie

Glad you managed to fix it :thumbup

Firmware was also upgraded without a problem my previous was LC15 (didnt see this as listed as a problem version)

Yes and No. Although not explicitly mentioned, the FGA DO say:

...In fact, as this issue is related to the firmware and not the drive, ALL 7200.11 drives with firmware prior to SD1A are susceptible to this bug and is a time bomb waiting to happen...

Which DO include that firmware version ;)

Edited by BlouBul
0

Share this post


Link to post
Share on other sites

The price for recovery of this drive would be £249 + VAT which would include a USB hard drive with your data on, and shipping of the data drive.

I have my personal idea on this.

An actual recovery in a protected environment is something that goes in the several hundreds pounds range, maybe 1 thousand or more (PLUS the cost of the media).

You EITHER found a recovery company that offers VERY reasonable prices :thumbupOR (choose one) :w00t: :

  1. It is a "trivial" problem that can be solved by yourself as a "reset" would be enough :)
  2. it is a "trivial" problem that you cannot however solve this way as you need some other technique/commands/hardware :(
  3. they are complete morons and they don't know what they are saying :ph34r:

If you take off the 249 pounds shipping and the price of a cheap 500Gb USB drive, let's say 40 Pounds, they get more or less 200 pounds for the work, so the problem must be trivial.

jaclaz

0

Share this post


Link to post
Share on other sites

I have no idea whether this is now known here, but it seems that during february and march, many ST2000DL003 (Seagate Barracuda LP Green 2000GB) drives have failed for users all over the world. Mine died a few days ago (2 days after purchase), so I tried connecting to its monitor to see what happens (and maybe try the N1/m0,2,2... fix), so here's what I've found out:

The dead drive is:

ST2000DL003

P/N: 9VT166-301

F/W: CC32

DATE: 11311

SITE: SU

I managed to connect to the disk's serial interface, and this is the diagnostic output it gives upon power-up. Hopefully someone qualified can now step up and tell us what it actually is that the ST2000DL003s are choking on.

(P) SATA Reset

SIM Error 1009

RW Error 00000080

User Data Base 00990DE8

MCMainPOR: Start:

Check MCMT Version: Current

MCMainPOR: Non-Init Case

MC Seg Disc and Cache Nodes: 4011982C 4011793C

Seg Write Preamble VBM start: 000010A7 end: 000010CE

Footer - start: 000010D0 end: 000010F7

Seg Read Preamble VBM - start: 000010F9 end: 00001120

Footer - start: 00001122 end: 00001149

Reconstruction: MCMT Reconstruction Start

Max number of MC segments 22E0

Nonvolatile MCMT sequence number 000070B0

[RSRS] 0EBA

Reconstruction: EXCEPTION: Segment Overall Sequence Number Mismatch

00004221 00000000 A

Recon Last Chance Header ID FFFFFFFF SeqNum FFFFFFFF Current

Segment, Head

Rst 0x40M

MC Internal LPC Process

LED:000000BD FAddr:00005652

Apparently the firmware is running into an assertion based on something it reads from the platters when starting up.

The bad news is there's no way to fix this using the "seagate fix" described all over the various Internet boards (that is, issuing commands N1 to reset the SMART log and m0,2,2,0,0,0,0,22 to re-format the user partition), because one never gets to the monitors prompt (ctrl-z won't work after the firmware has stumbled upon the exception). Insulating the contacts to either the motor or the heads (or both) doesn't help in this regard, because Seagate, as it seems, has crippled the electronics on these new drives by making the monitor (and presumably everything else) dependent on something that first has to be read from the platters. In other words, while older disks would communicate on the serial monitor even with the PCB totally disconnected from the motor and the heads, these new drives don't even start to log anything into the monitor until after they've spinned up and read a couple sectors from the platters. I tried taking the electronics off from several drives I have lying around (7200.9, 7200.10, 7200.11 and also one 2.5-inch drive), and this new drive is the only one that needs to read something from the platters before starting the serial monitor. I can't resist commenting on this observation... It simply seems that Seagate has made a pretty bad [cost cutting?] decision here.

Also, if you want to try to connect to your dead disk's monitor, too, note that:

- this new drive needs 5V to send/receive on the TX/RX lines (as opposed to 3.3V with all the older drives),

- while some older drives would communicate at 9600 bps, the ST2000DL003 communicates at 38400 bps,

- using a PCB from another, completely healthy disk doesn't help, because although the PCB will be able to spin up the drive, it won't then be able to read the initial couple of sectors (perhaps because of some platters-specific calibration data stored in the 512K Winbond flash?) and thus start the monitor.

Hope this helps someone eventually.

Edited by viinikala
0

Share this post


Link to post
Share on other sites

Hope this helps someone eventually.

It may. :)

Can you please re-post to a NEW thread aptly titled?

Something like:

Seagate Barracuda LP Green 2000GB Bricking

This way it will have better visibility and will NOT be "buried" in this unrelated thread (where most people won't be able to find this info and where there will be NO discussion about this OTHER drive model, see read-me-first).

jaclaz

0

Share this post


Link to post
Share on other sites
Can you please re-post to a NEW thread aptly titled?

Sure. Here goes:

Edited by viinikala
0

Share this post


Link to post
Share on other sites

Is there any possibility to get my data back? with the instructions from gradius, aviko or all the other?

MInd you the following is my PERSONAL opinion.

There are reports of the i365 guys to be either extremely correct and honest :thumbup or completely nuts and false :ph34r: (up and beyond the border of "robbery")

I suspect that this may depend on several factors including:

  • the actual "channel" through which your drive was sent to them
  • the actual "operator" that actually puts his/her hands on your drive

Point is whether your drive was originally affected by either LBA0 or BSY problem, what we commonly define as "bricked" as in:

discbrick.jpg

For what we know:

  1. it is NOT possible to upgrade the firmware UNLESS the drive is "unbricked" first.
  2. once the drive is unbricked (and WITHOUT ANY firmware upgrade) it won't re-brick itself spontaneously for at least three months of daily use (six to twelve month being proven to be the most likely cases)
  3. logically NO data recovery service would (though it is possible) re-brick the drive after the firmware upgrade :w00t:
  4. actually upgrading the firmware has NO (immediate) consequence to the actual "brick status" of the drive

If I were you (and mind you - AGAIN - this is just my PERSONAL take on the matter), if you are sure enough of the symptoms your drive had when it failed, i.e. you are confident enough that it was in a LBA0 or BSY state, I would call the bluff :angel and get the drive back.

Mind you also that there is a line that is quite "elastic" between "recovering a drive" and "recovering the filesystem", and even another elastic line between "recovering the filesystem" and "recovery of MOST contents of it".

PLEASE go to "Search" and search for "i365" make sure you select "Show results As posts" and take some time reading the results (you'll get two pages of results):

http://www.msfn.org/board/index.php?app=core&module=search&search_in=forums

Come back when you have read ALL those posts and have a better idea of the past experiences of the other members, as said quite contrasting.

jaclaz

Hello jaclaz or other people,

i tried myself to fix the LBA0 Problem. The Cable connections are OK, the Loopbacktest also, but when i try to start

F3 T>m0,2,2,0,0,0,0,22

Then i get after a few seconds the answer :

DIAG Error 0000500E Process Effect List Error

R/W Sense 00000002 R/W Error 841C0087, List Offset 00000000, File Error 00000001

And after I tried

F3 T>v4

I got everey few seconds

LED:000000CC FAddr:00243FCF

Is there any possibility to solve this problem ??

Edited by Jamesblond
0

Share this post


Link to post
Share on other sites

That should mean that you did not manage to spin down. :blink:

See here:

http://vermeulen.ca/computer-harddrives.html

Try if this changes anything.

WHICH guide/method are you following?

I don't recall any "v4" command in the guides used :unsure:

jaclaz

0

Share this post


Link to post
Share on other sites

[*]once the drive is unbricked (and WITHOUT ANY firmware upgrade) it won't re-brick itself spontaneously for at least three months of daily use (six to twelve month being proven to be the most likely cases)

I can not agree with this. Just unbricked my drive last week for the 4th time. I undbricked it the last time two months ago.

However, since I did not solve the Fujitsu Siemens firmware issue (and to be honest I'm not interrested to look further in this topic anymore), I have a replacement drive at home since Tuesday, that just waits until I figured out how to solve the 4kByte sector alignement issue, before I send my seagate drive into rent.

And, ofcourse, the replacement drive is no seagate drive.

Regards

Chilli

0

Share this post


Link to post
Share on other sites

[*]once the drive is unbricked (and WITHOUT ANY firmware upgrade) it won't re-brick itself spontaneously for at least three months of daily use (six to twelve month being proven to be the most likely cases)

I can not agree with this. Just unbricked my drive last week for the 4th time. I undbricked it the last time two months ago.

Well, maybe not strictly "at least" three months, but if your hdd bricked three more times in the 14 months since you fixed it the first time in Jan'10, it is 14/3=4.66 months. Thus on average it bricked every 4 months and twenty days which IS longer than the three months jaclaz said. It also depends on how many times you power cycle the drive and can't be exactly quantfied.

However, since I did not solve the Fujitsu Siemens firmware issue (and to be honest I'm not interrested to look further in this topic anymore),

Did you look here? http://support.seagate.com/firmware/fts_drive_check_en.html

0

Share this post


Link to post
Share on other sites

Well, maybe not strictly "at least" three months, but if your hdd bricked three more times in the 14 months since you fixed it the first time in Jan'10, it is 14/3=4.66 months. Thus on average it bricked every 4 months and twenty days which IS longer than the three months jaclaz said. It also depends on how many times you power cycle the drive and can't be exactly quantfied.

Sure, three months is something intended as "NOT IMMEDIATELY" and "NOT TOMORROW" it may also depend on the number of (other) problems the drive may have AND by the actual number of entries written to the log.

Just as an example if a "good drive" writes just one entry in the log at each boot, if some other events writes at each boot other three events, and you boot once daily, you will reach a multiple of 256 earlier, like 256/4=64 days, that do sound a lot like two months.

Some hypothesis explaining the three months (or 106 reboots) possibilities:

jaclaz

0

Share this post


Link to post
Share on other sites

That should mean that you did not manage to spin down. :blink:

See here:

http://vermeulen.ca/computer-harddrives.html

Try if this changes anything.

WHICH guide/method are you following?

I don't recall any "v4" command in the guides used :unsure:

jaclaz

Hello Jaclaz,

now i tried this from your link "http://vermeulen.ca/computer-harddrives.html"

After ...

F3 T>/8

F3 8>Z

Spin Down Complete

Elapsed Time 0.161 msecs

F3 8>

F3 8>U

Spin Up Complete

Elapsed Time 9.250 secs

F3 8>/1

F3 1>N1

I got allways the same words:

LED:000000CC FAddr:00243FCF

In my case : Is there any hope to solve the problem, or get it into the garbage ?

I google for the words :

DIAG Error 0000500E Process Effect List Error

R/W Sense 00000002 R/W Error 841C0087, List Offset 00000000, File Error 00000001

And i found on "http://forum.hddguru.com/seagate-issue-repair-and-breaks-again-t13900.html" the v4.....

0

Share this post


Link to post
Share on other sites

Barracuda 7200.11... do I have this same problem??

I have a internal Barracuda 7200.11...Firmware SD33 .... Manufac: 11/2008.....and for some reason it refuses to start up when connected via SATA at bootup..

I can hear the drive actually spinning to start with, then it seems to reset itself and try over again, on an endless unsuccessful cycle. it does not want to initiate...however im guessing i would not hear these sounds if it was not spinning up at all?...

this text seems to match my problem:

Reason for the Seagate 7200.11 Failure

This problem is caused by a firmware issue that sets the drive's "event log" pointer to an invalid location. This is detected by the drive during power-up initialisation, and the drive switches to fail-safe mode to prevent further corruption and loss of user data. Once the failure has occurred user data becomes inaccessible.

During power up, if the Event Log count is at 320, or any multiple of (320 + Nx256), and if a particular fill pattern is present in the factory reserved area of the drive, the firmware will incorrectly allow the Event Log pointer to increment past the end of the Event Log data structure.

This error is detected during initialisation and returns an "Assert Failure", which causes the drive to enter it's fail-safe mode. When the drive enters this mode further updates to the event log counter are impossible as the same results occur at each power-cycle.

The problem can only occur if a power cycle initialization occurs when the Event Log is at 320 or a multiple of 256 thereafter. Once a drive is in this state, the user will not be able to resolve/recover existing failed drives.

...but i am not sure...plus i dont know how to get a diagnosis?!?

The drive resides in a clean host system as a back-up drive for data, and has not been dropped or had any form of stress....it just stopped working and disappeared form my computer.

I have contacted Seagate but its an OEM so they will not help me any further....The OEM would not help as i beleive its out of waaranty and even if it was still under, then they would only offer a replacement...which of course, i do not want.....i need the data only - this drive has important stuff and for the record the £600GBP i have been qouted from data recovery is too much...

any help/advice is very much appreciated!!

Thanks in advance,

Corky :P

ok guys ive performed the fix as per listed here and now the drive is spinning more normally than before...

it loaded the drivers and said it was installed and the device was working properly

still no in My COmputer though...

however although its telling me in disk management that it is 'unknown' and 'Not initialized' this is strange as its obviously not a new disk...it ghas my data on it. is it ok to go ahead and initialize? it says something of partioning which worries me that it might overwrite my data or am i being a jack a** worrying there?!

Corky

0

Share this post


Link to post
Share on other sites

ok guys ive performed the fix as per listed here and now the drive is spinning more normally than before...

it loaded the drivers and said it was installed and the device was working properly

still no in My COmputer though...

however although its telling me in disk management that it is 'unknown' and 'Not initialized' this is strange as its obviously not a new disk...it ghas my data on it. is it ok to go ahead and initialize? it says something of partioning which worries me that it might overwrite my data or am i being a jack a** worrying there?!

Normally after the fix, it is exactly as it was before it bricked with all the data and partitions like before . Did you get something like this:

Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 14, Max Certify Rewrite Retries = 00C8

User Partition Format 10% complete, Zone 00, Pass 00, LBA 00004339, ErrCode 00000080, Elapsed Time 0 mins 05 secs

User Partition Format Successful - Elapsed Time 0 mins 05 secs

Is it seen in BIOS now. and if it is, as what size?

How are you connecting to your computer now - still as an internal hdd via SATA or as an external USB? :unsure:

And NO, do not partition or overwrite anything now you are right to worry about that, let's first try to find out what is wrong.

Edited by BlouBul
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.