• Announcements

    • xper

      MSFN Sponsorship and AdBlockers!   07/10/2016

      Dear members, MSFN is made available via subscriptions, donations and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, become a site sponsor and ads will be disabled automatically and by subscribing you get other sponsor benefits.
Zenskas

Seagate Barracuda 7200.11 Troubles

1,248 posts in this topic

We look forward to your continued dissatisfaction with Seagate products.

Thank you for worshipping Seagate.

Hahah, very good one! :thumbup

First laugh I have from this bad case. :wacko:

Gradius

0

Share this post


Link to post
Share on other sites

the alleged seagrapes knowlegdged base snapshot, perhaps its a hoax? dont get ur hopes to high

0

Share this post


Link to post
Share on other sites
Has anyone noticed the user - Seagate_AlanM :hello:?? Maybe Seagate can join in on the discussion and help us fix this issue... Might help out a bit in the PR arena!!

i think it is more likely he is trying to get this thread removed than him posting anything here!

in terms of this rumoured new firmware, it is likely that it will not "fix" the people whose drives have already locked up, but is intended for people who have not yet experienced any failure to prevent it from happening.

seems to me like this is probably the cheapest option for them to deal with this crisis they are facing. this caters for the folks who do not want to RMA the drive because we will just get another back that is going to do the exact same thing. but they really need to come up with a proper solution for us customers that have locked up drives other than RMAing it, because the cost of data recovery for an obvious fault on the part of seagate is the cause of the problem. they say in their warranty they do not cover data recovery costs, well that is fine, but come up with a PROPER solution for everybody then! if data recovery companies have found a way around this, surely seagate know how to fix it?!

0

Share this post


Link to post
Share on other sites
Hi all,

I have two ST31000340AS with firmware SD15 made in Thailand. The first drive was purchased in August and the second in October. Both drives are still working (knock on wood) and I'm a little puzzled as to why that is. Since the BSY flag problem is a firmware defect, I would expect the drives to fail at some point, but they haven't yet. Are there any theories as to why that is? Is there a motherboard/chipset combination which triggers the defect in the firmware?

Another interesting thing is that both drives are showing 0kB cache (BuffSize=0kB). I'm wondering if that has somehow "protected" them from the BSY flag problem?

The problem is caused by a firmware bug, it writes bad data on sector 0 where some important information about your HD lies there. When it writes bad data there, it leads the drive to CC, BSY or 0GB state. This problem can be manifested between 2 weeks until 5 months (so far it's random thing). It could be a hardware problem too, but that only Seagate will know (?) and I hardly believe they will tell us all the true, because it would lead to panic, and everyone around the world would return those crappy HDs at same time, and of course, I believe they don't want that because of the costs involved on a mass recall and bad publicity, but good companies does mass recalls, and I do find that a good thing.

Gradius

0

Share this post


Link to post
Share on other sites
WD Caviar Black? I'd rather spend some money now and have a machine that I can use over waiting for seagate to issue a fix. This is for a home PC, spends most of its time editing images and running itunes...no heavy server use, etc.

Thanks to everyone who is keeping up the pressure and getting the word out. If I can represent the "casual user" for a moment, you guys are heroes! If I ran PR/support like seagate apparently is, I'd be out of business quickly!

Yes, I do recommend WD Caviar Black, in fact I'll replace all my 750GB to 1TBs WD C.B.

My fear are on 1TB ST31000333AS I have now. :unsure:

Gradius

0

Share this post


Link to post
Share on other sites
Hi all,

I have two ST31000340AS with firmware SD15 made in Thailand. The first drive was purchased in August and the second in October. Both drives are still working (knock on wood) and I'm a little puzzled as to why that is. Since the BSY flag problem is a firmware defect, I would expect the drives to fail at some point, but they haven't yet. Are there any theories as to why that is? Is there a motherboard/chipset combination which triggers the defect in the firmware?

Another interesting thing is that both drives are showing 0kB cache (BuffSize=0kB). I'm wondering if that has somehow "protected" them from the BSY flag problem?

snip

but good companies does mass recalls, and I do find that a good thing.

Gradius

exactly. good companies would sort this out. if seagate turned around and offered to fix all these drives for us, so rare is decent customer service these days that i would probably only ever buy seagate hard drives from that point forward. however, they wont.

0

Share this post


Link to post
Share on other sites
in terms of this rumoured new firmware, it is likely that it will not "fix" the people whose drives have already locked up, but is intended for people who have not yet experienced any failure to prevent it from happening.

Unfortunately, you cannot "fix" something already in locked state (aka BSY, or not begin recognized by BIOS), because the flasher needs that.

I tried myself and found out the hard way. :ph34r:

Gradius

0

Share this post


Link to post
Share on other sites
EDIT: Sorry, I meant all drives till December.

Ouch, now I'm scared! :blink:

Gradius

0

Share this post


Link to post
Share on other sites
Have you guys seen this? I can insert it into the first post, just PM me if you'd like to see it there. :)

http://www.kbklawfirm.com/seagate/Seagate-...-hard-drive.php

These fools are just jackals. They sue everyone they can. Look at the title of that Seagate page "Are you a Verizon customer?". Click on their name at the top of the Seagate page, and its a lawsuit against Brother printers also.

They must lie in wait for a product to fail a few times, and then try to bring a lawsuit against companies for easy money.

Scoundrel lawyers. They are probably too busy chasing ambulances to actually code webpages properly. Too bad, people may take them a bit more serious if they did.

0

Share this post


Link to post
Share on other sites
Press Ctrl+Z to get: T> command prompt.

Then type this:

T>/2 (Enter)

2>S006b (Enter)

2>R21,01 (Enter)

2>C0,570 (Enter)

2>W20,01 (Enter)

Gradius

I doubt this will fix 7200.11 drive, it seems to be a fix for old ST310014ACE (to unlock passworded drive I guess) look here

Regards

0

Share this post


Link to post
Share on other sites
I have built an EEPROM programmer.

The EEPROM memory is of 512K (4MBit).

I will do a backup of EEPROM memory of the PCB. Then I can do all test over PCB without any problem. Half of the firmware is here.

The problem can be a defective EEPROM, can you say your EEPROM number? (8 leads integrated circuit of the family 25XXX).

Ehhhrr, what exactly do you want us to do?

I have tested my programmer with the M25P40 memory that I had.

Unscrew torx 6 screws and see integrated circuit number.

I want make a list of EEPROM memory compatibility.

If all EEPROMs are from the same manufacturer can be an EEPROM problem.

The problem may be a writting error in the EEPROM at power off.

Sometimes there may be errors in the writing of the EEPROM. If the firmware does not detects these errors the hdd can be blocked as a security mechanism.

The other half of the firmware is in the service area SA (2113 fields, approx. 1MB), but it is innaccesible.

512K + 1MB = 1.5MB

All ".lod" or ".bin" of the updates are multiples of 512 bytes. Curiosity.

PLEASE: Help to make the EEPROM list.

0

Share this post


Link to post
Share on other sites

Sup guys,

I contacted several mag companies, just to spread the word and i have gotten one reply thus far. This was also posted on the seagate forum, but obviously it got removed. Go Figure!

Hi, Jose.

I’ve tried to contact Seagate’s PR rep about this (and a related article I found on The Inquirer), but I haven’t heard back yet. I’ll let you know if I do.

Sounds like the issue is too huge for Seagate to ignore, for what it’s worth. I would be surprised if they don’t make an official statement soon, if they haven’t already.

Let’s cross our fingers that they have a plan to help their customers. Hang in there...

Best regards,

Edited by jpal20002001
0

Share this post


Link to post
Share on other sites
PLEASE: Help to make the EEPROM list.

How & where can we check the EEPROM information you are asking for? Please be a little more descriptive.

0

Share this post


Link to post
Share on other sites
PLEASE: Help to make the EEPROM list.

I don't know how to get the EEPROM, maybe you could post a guide.

Anyway, I uploaded a pic of the PCBs that I have, I hope it helps.

PCB-Comparison-s.jpg

0

Share this post


Link to post
Share on other sites
PLEASE: Help to make the EEPROM list.

How & where can we check the EEPROM information you are asking for? Please be a little more descriptive.

I believe you have to pull the board off the drive and look at the chips on the other side...

0

Share this post


Link to post
Share on other sites

From OLD: MT46V16M16 (cache)

This isn't the eeprom, is just the DRAM (DDR) from Micron (cache), so the EEPROM in this case lies inside on CPU.

---

From NEW: Hynix HY5DU561622ETP-D43 (cache)

Bad news, this is DDR (Hynix) too! So is also inside the CPU.

They changed the CPU.

OLD: ST

NEW: LSI

So there is NO way to re-programming with right tools. I have the SF446, it will be necessary to disassembly and hack it to accept bad firmwares cases (like programming SD15 with AD14). Also, a new tool will be necessary to look for hard drive even if they aren't detected by BIOS. But probably isn't possible until you remove the drive from CC,BSY,0KB state, and until now this is only possible by RS232 or other hardware solution.

Gradius

Edited by Gradius2
0

Share this post


Link to post
Share on other sites

Hi,

has anybody ever seen their 1.5TB drive fail (ST31500341AS)? At least there is none in the data-thread, isn't it strange that this model is obviously not affected?

0

Share this post


Link to post
Share on other sites

Hi guys, I noticed there are a lot of mainstream sites like Gizmodo and Engadget that have posted new stories about this problem. I'm so thankful for their support. Otherwise we'd be getting the shaft from Seagate.

0

Share this post


Link to post
Share on other sites
I have built an EEPROM programmer.

The EEPROM memory is of 512K (4MBit).

I will do a backup of EEPROM memory of the PCB. Then I can do all test over PCB without any problem. Half of the firmware is here.

The problem can be a defective EEPROM, can you say your EEPROM number? (8 leads integrated circuit of the family 25XXX).

Ehhhrr, what exactly do you want us to do?

I have tested my programmer with the M25P40 memory that I had.

Unscrew torx 6 screws and see integrated circuit number.

I want make a list of EEPROM memory compatibility.

If all EEPROMs are from the same manufacturer can be an EEPROM problem.

The problem may be a writting error in the EEPROM at power off.

Sometimes there may be errors in the writing of the EEPROM. If the firmware does not detects these errors the hdd can be blocked as a security mechanism.

The other half of the firmware is in the service area SA (2113 fields, approx. 1MB), but it is innaccesible.

512K + 1MB = 1.5MB

All ".lod" or ".bin" of the updates are multiples of 512 bytes. Curiosity.

PLEASE: Help to make the EEPROM list.

the EEPROM on my board is a 25fw406a.

Other chip details (might be useful) Samsung DRAM, LSI main chip.

Has anyone tried sorting the pinout of the test port at the back? (been having problems hooking up the serial port to reset the BSY state, looking at that as a possible connection point to save soldering to the board - can't seem to find useful 'bucket' connectors for the pins)

0

Share this post


Link to post
Share on other sites

Access Time speed is an issue too.

750GB fw SD15 (I know a bad one, but with good access time):

ST3750330AS.png

1TB fw CC1F (low access time):

ST31000333AS_1.png

Gradius

0

Share this post


Link to post
Share on other sites

The memory label has this form: X25X40 for memories of 512K (or X25XXX for others sizes).

Integrated circuit of 8 leads.

This image is for ST31000340AS, ST3500320AS has similar placement.

post-225812-1232135803_thumb.jpg

Edited by pichi
0

Share this post


Link to post
Share on other sites

Anybody has troubles with 7200.11 under the linux? In failures statistics i can't find peoples with this OS. I'v seen messages related with AHCI,NCQ.

Edited by ivanich
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.