Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account


Photo

Seagate Barracuda 7200.11 Troubles

- - - - -

  • Please log in to reply
1247 replies to this topic

#1176
firescalp

firescalp
  • Member
  • 1 posts
Hi all,

I'm looking for a Seagate barracuda PCB:

barracuda 7200.11 1000 Gbytes
- S/N: 9QJ1TT42 - ST31000340AS
- P/N: 9BX158-335 - Firmware: SD15
- Date code 09074 - site code: KRATSG
- WWN: 5000C5000DAAD518

if someone know were is one just mail me!!

Thanks too all!


How to remove advertisement from MSFN

#1177
amit_talkin

amit_talkin

    Experienced

  • Member
  • PipPipPip
  • 397 posts
I didnt know about this problem until I read this thread! Seems they had fixed it in later firmware version. I have SD46 firmware revision on my ST3500320AS 500GB HDD. Havent faced any problem from the day I have purchased it :).
Primary - Q9450@3.6GHz | 8GB G.Skill 1000MHz | Gigabyte GA-X48-DS4 F3b mobo. | 1.5TB Storage | Sappgire HD4890 | HomeMade H2O Kit | Antec NeoPower Blue 650w
Secondary - E8400 3.00@ 4.05GHz | 4 GB Crucial Ballistix | ASUS P5B Deluxe mobo. | 250GB Storage | Sapphire Toxic HD4850 512MB | OCZ Vendetta2 CPU Cooler | Coolermaster 500w

#1178
hubb_99

hubb_99
  • Member
  • 3 posts
my seagate 7200.11 just stopped working. It's really odd though, it will recognize at first and I can scan with some recovery programs and then all of a sudden it will just disappear and nothing can see the drive anymore. I was using this as my backup drive....I had images....music....movies.....everything on it. I will never buy another seagate product again. I work as a network admin and you better believe I know a lot of people and will tell everyone I can the same thing. I guess seagate really doesn't care about us consumer based customers though. Ohhh and Seagate apparently says that according to my serial number I am not in need of the firmware update.

Edited by hubb_99, 05 December 2009 - 03:05 PM.


#1179
hubb_99

hubb_99
  • Member
  • 3 posts
I just did the procedure to recover data on my seagate and it actually worked (thank you very much to the author)

my question is:

has anyone continued to use the drives after this procedure?

I am pulling all my data off of it and putting it on my new western digital hard drive but am just curious if anyone has continued to use these with any success.

#1180
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,385 posts
  • OS:none specified
  • Country: Country Flag

I just did the procedure to recover data on my seagate and it actually worked (thank you very much to the author)

my question is:

has anyone continued to use the drives after this procedure?

I am pulling all my data off of it and putting it on my new western digital hard drive but am just curious if anyone has continued to use these with any success.

Yes.

The problem is seemingly in the actual firmware.

Some details are in the main thread, starting here:
http://www.msfn.org/...-page-1007.html
for roughly three pages.

The issue in itself is stoopid enough:
when you power on the drive and internal LOG was left to entry 320 or any value satisfying the expression 320+n*256 the drive bricks itself.

  • IF you have a working drive AND you upgrade it's firmware AND the firmware is NOT bugged, the drive will last on average like any other one.
    The fix is made in two steps:
  • unbrick a bricked drive making it working
  • loop to 1. above

Point is that due to the TOTAL and UTTERLESS lack of any form of brightness, courtesy, politeness and open-mindedness from the Seagate people, BOTH in the Technical and Support services AND on their Forum, there is NO way to know for sure:
  • IF any given new firmware is appropriate to the specific drive
  • IF any given new firmware release solves the problem (without introduceing OTHER bugs)

What they tell people with a bricked drive is more or less:
  • you are NOT affected by the problem (which means in plain English: you are a liar, your drive is not bricked)
  • if you send the drive in we will replace it, should we find it to be defective
  • under the Warranty Terms, recovery of your data is not provided, you should have backed it up
  • if the drive gets lost on the way to us or on the way back it's your problem
  • we may send you back at our exclusive discretion (and we won't tell you in advance whether you will get back):
    • your drive revived with all data intact (not because we will recover the data, but only if the data happens to be there, and we won't even tell you if this is likely to happen or not)
    • a refurbished drive
    • a new drive
  • Since we won't admit that there is a problem, it is obvious that we cannot tell you that firmware xxxx will fix that problem (that only exists in your mind)

As I see it the product is not worse or better than that of the competitors, every firm has had (or will have) a "badly born" model or series, but definitely the Support sucks.

Reality (and as proven by the number of reported successes) is:
  • an average technician can fix the issue in no more than 15 minutes and NO data will be lost
  • a complete n00b can fix it in a few attempts/several hours and NO data will be lost
  • it is utterly stoopid to send drives back and forth if not actually needed (have you ever seen the delicacy with which UPS or FedEx - or any other courier for that matter - manage parcels?) as you have the concrete risk of damage or loss during this stage

In my opinion if they had
  • printed DON'T PANIC in large, friendly letters on their Web Site
  • told people not to worry, that their data and drive could be recovered allright
  • admitted the hiccup
  • apologized for the inconveniences
  • provided documental evidence of the reason of the problem and of the way they fixed it in later releases
  • outsourced the recovery to local (say) TV repairers or Computer Shops for (say) US $10 apiece, asking Customers to bring personally the drive in the shop, and collect it after a couple of days, they would have :yes::
  • saved lots of money
  • saved lots of fuel and packing/shipping costs (a small contribution to the fight against entropy)
  • had a plethora of admired Customers that would have LOVED :wub: them for the rest of their life (no matter if their drive is good or not)

The way they chose they have had ALL their sentient customers really, really mad at them :realmad: (again no matter if their drive is good or not).

jaclaz

#1181
hubb_99

hubb_99
  • Member
  • 3 posts
What really makes me angry is that I know I have the firmware version SD15 that is having the problems but Seagate won't give me the firmware update. I had to search the net for an update from Dell that contains the update ISO. Buncha basterds. I can officially say that I am anti-Seagate. Another classic example of a company pushing products on the market when they had obviously not done any quality control on it. Also if you look at the soldering on the chips.....not very good either.....even if I do get the firmware updated I would not trust this drive.

#1182
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,385 posts
  • OS:none specified
  • Country: Country Flag

What really makes me angry is that I know I have the firmware version SD15 that is having the problems but Seagate won't give me the firmware update.


Sure, to them you are a liar :ph34r: as your drive is NOT affected by the problem (What problem? :w00t:) ;)

http://www.imdb.com/...t0072431/quotes

Dr. Frederick Frankenstein: You know, I'm a rather brilliant surgeon. Perhaps I can help you with that hump.
Igor: What hump?


:P

jaclaz

#1183
Laz

Laz

    Newbie

  • Member
  • 29 posts
Hi Hub 99; I am happy to hear you solved your problem; I have about 8 7200.11s maybe; I had to apply the rs232 fix on one and the rest of the affected versions I upgraded the firmware. I have not had any further issues with my seagates.

#1184
illuminate

illuminate
  • Member
  • 1 posts
Seagate 7200.11 S/N 5qkomphm, st3750630as, p/n 9bx146-621, hp24, date code 09124, site code wu, wwn:5000c5000e8c733d. wgbu: 460315-002, ct:2ahzh0183wk3gv. Same symptoms as described- slower startups, started freezing all within 3 days of final bricking. Talked to hp support and said it was an obvious hard drive failure and that I needed a new one. No mention of seagate problems. Found this site and many others all describing exactly what happened to me. What a sham! HP said I needed to replace with identical same hard drive from seagate-seems stupid to do so. Can I substitute?

#1185
Laz

Laz

    Newbie

  • Member
  • 29 posts
of course you should be able to substitute; HP wants you to stay with the standard configuration; but screw'em, it's your computer.

#1186
Zenskas

Zenskas

    Advanced Member

  • Member
  • PipPipPip
  • 484 posts
  • OS:Windows 8.1 x64
  • Country: Country Flag

Seagate 7200.11 S/N 5qkomphm, st3750630as, p/n 9bx146-621, hp24, date code 09124, site code wu, wwn:5000c5000e8c733d. wgbu: 460315-002, ct:2ahzh0183wk3gv. Same symptoms as described- slower startups, started freezing all within 3 days of final bricking. Talked to hp support and said it was an obvious hard drive failure and that I needed a new one. No mention of seagate problems. Found this site and many others all describing exactly what happened to me. What a sham! HP said I needed to replace with identical same hard drive from seagate-seems stupid to do so. Can I substitute?

Yes and I recommend a Western Digital or Samsung HDD, I have one of both and they are flawless. Quiet, and have no well known problems (at least with any of the drives you can buy today from them).

[Passive Gamer] Silverstone TJ08-EW | Intel Core i7 3770S | Silverstone Heligon HE02 | ASUS Maximus IV Gene-Z/Gen3 | 8GB Kingston HyperX Fury 1866MHz | Samsung 840 EVO 250GB | ASUS GTX 750 Ti Strix OC 2GB | Antec Neo HE 550W |


#1187
Kai-Pirinha

Kai-Pirinha
  • Member
  • 4 posts
first of all: I'm not sure if my case is related to this problem. I'm posting this be course I need to know and I don't trust Seagate support anymore.
I own a Maxtor one touch 4 1TB (external USB Hard drive) which failed 3 Days ago. Seagate Support tells me I can ship it over to them and they will replace it but all my Data will be lost. So I carefully removed the actual hard drive from its external housing, hoping the drive itself is not damaged.
The harddrive turned out to be a Seagate Barracuda 7200.11 1000GB and its not working internal as well meaning power is ok, motor is started but BIOS is not detecting it.
The Model is ST31000340AS. The Firmware is SD81. The S/N is 9QJ0SE0L. The P/N is 9BX158-568. The Date Code is 08454. The Site Code is KRATSG. Product of Thailand. (all information according to the label on the actual hard drive, not the external housing)

Model and Sitecode match plus seagate is offering the same Firmware update for my drive they offer for the SD15Firmware. So I expected it to be the Firmware problem and called Seagate support again.
They asked me for the S/N only and told me my drive (and all drives manufactured for external use) don't have the Firmware problem.
So I asked him why my drive died without any warning and the same symptoms. The answer I got is they often receive drives with the same symptoms that don't have the firmware problem but a malfunctioning circuit board instead. Even though the board has this Problem they say it's not Seagate's fault but in the normal 1% failure rate for hard drives and could have been solved within the normal warranty I don't have any more be course I opened the external housing. (if i shipped it to Seagate for warranty unopened all my data would have been lost and I wouldn't even know I had a barracuda 7200.11)

according to Seagate I can get my data back in one of two ways:
1. let a professional Data rescue service handle it for 300EUR-1000EUR
2. buy another hard drive with the same S/N and use its control board

i think it's unacceptable to spend money for another unreliable 7200.11 espacially be course i don't know if this will bring back my data. There are a few reports on the web about drives with SD81 Firmware that could be restored with a firmware update.

Can anyone tell me what I should do?
Can anyone say if my Hard drive COULD have the firmware problem?
Is there anyone from Hamburg or north Germany who already fixed a "busy" barracuda 7200.11? I don't know where to buy the components and I'm afraid to lose my Data if I try it myself.

sorry if i double posted something, i read a lot of those 60 pages but not all of them

Edited by Kai-Pirinha, 21 January 2010 - 08:51 AM.


#1188
Laz

Laz

    Newbie

  • Member
  • 29 posts
Re-awakening the 7200.11 is not as hard as it might seem without trying. Yes, there is some risk, risk that you fail to follow the instructions in this thread and screw up; but otherwise I will say it is up to you to mitigate that risk. Send the drive to seagate and lose your data; send it somewhere else, lose some money and maybe get/lose your data,or, keep your money and your drive and see what you can do by yourself. The wise choice should be clear. Good luck.

#1189
Kai-Pirinha

Kai-Pirinha
  • Member
  • 4 posts

first of all: I'm not sure if my case is related to this problem. I'm posting this be course I need to know and I don't trust Seagate support anymore.
I own a Maxtor one touch 4 1TB (external USB Hard drive) which failed 3 Days ago. Seagate Support tells me I can ship it over to them and they will replace it but all my Data will be lost. So I carefully removed the actual hard drive from its external housing, hoping the drive itself is not damaged.
The harddrive turned out to be a Seagate Barracuda 7200.11 1000GB and its not working internal as well meaning power is ok, motor is started but BIOS is not detecting it.
The Model is ST31000340AS. The Firmware is SD81. The S/N is 9QJ0SE0L. The P/N is 9BX158-568. The Date Code is 08454. The Site Code is KRATSG. Product of Thailand. (all information according to the label on the actual hard drive, not the external housing)

Can anyone say if my Hard drive COULD have the firmware problem?
Is there anyone from Hamburg or north Germany who already fixed a "busy" barracuda 7200.11? I don't know where to buy the components and I'm afraid to lose my Data if I try it myself.


Hey guys thank you very much the the answers in both threads.
I'm currently trying to get the components to unbrick my drive. when i do a Forum search for SD81 i can find a couple of reports from who successfully unbricked their drives with SD81 (NOT SD 18) Firmware so they obviously had the firmware problem.
When i call seagate support they tell be only one factory had the Firmware problem (even though they are all using the same firmware) and they can tell from my serial number my drive doesn't have that Problem, so it must be the control board.
I have no idea if I should believe them.
first they deny the whole firmware Problem. Next step: they say "7200.11 barracuda drives a the Problem but yours with SD81 Firmware doesn't".
Now they say "SD81 drives can have the Problem too but yours still can't so we don't have to help you"
The guy told me to use the following link (https://apps1.seagat...check_index.jsp) and enter my serialnumber: according to the website i don't need to update my firmware. The support guy said that's how they check it and i can't have the firmware Problem.
I can see the following situation coming: I get everything to unbrick my drive, it doesn't work and i have now way of knowing if i got a broken CA-42 cable, did something wrong or if i really don't have the Firmware problem.
So here is what would be a great help for me and certainly other people with SD81 firmware drives: If you have a barracuda 7200.11 with SD81 Firmware and successfully unbricked it please use the link i mentioned above and enter your serial number. If it tells you not to update we know seagate is giving us bull**** again!
I would be very very thankful for everyone who takes the time to do that.
Kai

Edit: ok i spent another evening on reading many many pages to prepare for fixing my drive and also found several reports about SD81 firmware drives being successfully recovered from busy state even so the seagate serial-number-tool said they couldn't have been affected. one exaple is the report from ToKuRo (http://www.msfn.org/...tml#entry831015) however those postings are very old and they may have updated their tool in the meantime. If i can fix my drive and therefore proof they are still covering things up or don't know better (i don't know witch is worse) i'm looking foreward to call seagate support again and give em hell!!!

Edited by Kai-Pirinha, 25 January 2010 - 06:26 PM.


#1190
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,385 posts
  • OS:none specified
  • Country: Country Flag

I can see the following situation coming: I get everything to unbrick my drive, it doesn't work and i have now way of knowing if i got a broken CA-42 cable, did something wrong or if i really don't have the Firmware problem.


Optimism is your not strong point, I presume.

You should separate the problem in two parts:
1) unbricking the drive
2) updating the firmware

The worst thing that can happen with #1 is that the procedure doesn't work (and then there is no reason to worry about #2), but it is unlikely given the number of people that reported success.
Of course it is well possible that the problem of your drive is NOT related to the issue that the procedures try to fix (0LBA oer BSY due to the 320th log entry.

On the other hand, if you succeed with #1 the ONLY thing that you should do in your right mind is FORGET about the firmware, get all the data you can off the stoopid seagate and put it on another disk, then the seagate will have NO value whatsoever, and you can do all the experiments and tests you want with it, again, even if the Firmware update is successful, DO NOT trust that drive.

However, and since you asked:

Can anyone tell me what I should do?
Can anyone say if my Hard drive COULD have the firmware problem?

judging also from your other post here:
http://www.msfn.org/...e...63.html&hl=

You are approaching it the "wrong" way.:(

You are a bit pessimist/overcautious BUT:
  • you are going to use a non-supported OS (Windows 7 instead of XP/2003)
  • you are going to use a known to be a possible failure hardware (the CA-42):
  • you don't trust yourself but are willing to trust a stranger that says he is able to do recover for you and give him your drive


The suggested approach is:
  • use the OS that has been reported to be working for sure (XP/2003)
  • use one of the TTL adapters that have been reported to be working for sure
  • trust ONLY yourself and/or a friend of yours technically oriented or a professional

The "main" thread is full of people who reported success with one or the other method and practically noone reporting an "absolute" failure, i.e NO hints that performing the procedure has damaged a drive even when it failed to unbrick it.

:hello:

jaclaz

#1191
stickle

stickle
  • Member
  • 1 posts
Hey troops,

My problem may be different than the firmware issue...does this sound familiar to anyone?

my barracuda 7200.11 only buzzes/pulses about once every four seconds. I don't think it is spinning! Can't see the drive. Nothing at all!!!

Contacted Seagate, they told me to try the firewire connector (I was using the USB). Nothing different.

Is this the firmware issue?

Got an suggestions on a fix?

Help Help Help Please!!!

Thanks

#1192
robintay

robintay

    Newbie

  • Member
  • 17 posts
my 7200.11 drive is still broken since aug 09. i have bought a tonne of stuffs specified in this forum to try to fix it with no luck. if anyone that is based in london is willing to fix it i am willing to bring the drive over along with the stuffs bought and pay for your time to fix. please let me know. desperate to get the family pics off it.

#1193
MadOCer

MadOCer

    Newbie

  • Member
  • 37 posts

my 7200.11 drive is still broken since aug 09. i have bought a tonne of stuffs specified in this forum to try to fix it with no luck. if anyone that is based in london is willing to fix it i am willing to bring the drive over along with the stuffs bought and pay for your time to fix. please let me know. desperate to get the family pics off it.


Does the drive sound "normal", when it is powered on, or does it exhibit any scratching or clicking noise or something like that? I mean does it spin up, like it used to when it was still working OK?

#1194
robintay

robintay

    Newbie

  • Member
  • 17 posts

my 7200.11 drive is still broken since aug 09. i have bought a tonne of stuffs specified in this forum to try to fix it with no luck. if anyone that is based in london is willing to fix it i am willing to bring the drive over along with the stuffs bought and pay for your time to fix. please let me know. desperate to get the family pics off it.


Does the drive sound "normal", when it is powered on, or does it exhibit any scratching or clicking noise or something like that? I mean does it spin up, like it used to when it was still working OK?


yes it definately spins up. no strange noises or anything. just cant access the drive. appreciate if you're around london and able to fix it.

#1195
MadOCer

MadOCer

    Newbie

  • Member
  • 37 posts

my 7200.11 drive is still broken since aug 09. i have bought a tonne of stuffs specified in this forum to try to fix it with no luck. if anyone that is based in london is willing to fix it i am willing to bring the drive over along with the stuffs bought and pay for your time to fix. please let me know. desperate to get the family pics off it.


Does the drive sound "normal", when it is powered on, or does it exhibit any scratching or clicking noise or something like that? I mean does it spin up, like it used to when it was still working OK?


yes it definately spins up. no strange noises or anything. just cant access the drive. appreciate if you're around london and able to fix it.


I'm sorry, but I'd have quite a long way to London, from Bavaria, Germany :D.

BUT, and that's the good news, your drive should be recoverable once the connection works. And that should definitely be possible to accomplish.

Good luck! Just offer the poeple some money. Something like 10-20 pounds and I'm sure there will be someone to assist you with this. ;)

#1196
robintay

robintay

    Newbie

  • Member
  • 17 posts

my 7200.11 drive is still broken since aug 09. i have bought a tonne of stuffs specified in this forum to try to fix it with no luck. if anyone that is based in london is willing to fix it i am willing to bring the drive over along with the stuffs bought and pay for your time to fix. please let me know. desperate to get the family pics off it.


Does the drive sound "normal", when it is powered on, or does it exhibit any scratching or clicking noise or something like that? I mean does it spin up, like it used to when it was still working OK?


yes it definately spins up. no strange noises or anything. just cant access the drive. appreciate if you're around london and able to fix it.


I'm sorry, but I'd have quite a long way to London, from Bavaria, Germany :D.

BUT, and that's the good news, your drive should be recoverable once the connection works. And that should definitely be possible to accomplish.

Good luck! Just offer the poeple some money. Something like 10-20 pounds and I'm sure there will be someone to assist you with this. ;)


Yeah definately dont mind that. thanks anyway

#1197
blinkdt

blinkdt

    Somewhat Knowledgeable

  • Member
  • PipPipPipPip
  • 582 posts
  • OS:Windows 8 x64
  • Country: Country Flag
OK, I just ran into my second Seagate drive suffering this issue. In the first instance, the owner contacted a "seller" on eBay who unbricked the drive for a mere $80. Uh-huh. Little did we know . . . .

In this case, I went to Seagate's site, wrote down the toll free support number (1-800-732-4283) and gave them a call. I spoke briefly with customer service and they sent me to tech support where 'Karen' explained the issue to me (they sent out a batch of drives with test firmware) before offering to have me ship the drive to them at their expense. They would perform a force firmware update that would unbrick the drive and make the data accessible, or replace the drive outright. I told them I did not need the data and opted for choice three, the advance replacement at $20. I should receive my new drive in three days and will return the old drive using a pre-paid shipper. I could have done the whole thing for free, but life is short and then you die.

Bottom line: sounds to me like Seagate has their act together at this point and could not have been more accommodating, at least in my case. Give them a call.

Edit: by the way, Karen and her colleagues are based in Oklahoma and sound real purdy :rolleyes: .

Edited by blinkdt, 02 May 2010 - 02:02 PM.

no peace for the wicked, no rest for the good

#1198
BetKing

BetKing

    Emergency Technician

  • Member
  • 21 posts
  • OS:none specified
  • Country: Country Flag
I just saw this for sale, at an online auction site, is this an OEM that has been repaired? Or what is it?

Posted Image

#1199
VideoRipper

VideoRipper

    CSI Eastwood City

  • Member
  • PipPipPip
  • 330 posts
  • OS:none specified
  • Country: Country Flag
Yes, it looks like a repaired drive from an HP computer (it has HP firmware). :yes:

Original Seagate firmware starts with "SD". :hello:
This is the drive I received when I got it swapped under warranty:
Posted Image

Greetz,

Peter.
To C the BASIC things in life, use Delphi

#1200
HTC_guy

HTC_guy
  • Member
  • 8 posts
guys can you please help me with my post in the other thread?

SOrry for the duplicate post, i started a new topic by mistake when I meant to start one here... soz!

hi all

ive been fixing these 7200.11 BSY drives for a long time now using the original fix posted from Gradius (kudos to you mate!)

so a client dropped off a drive (Seagate ST31000340AS 1TB) and I ran through the normal process, and still nothing... drive doesnt pick up at BIOS. So I was like OK... and did the optional extra step in his guide (which I have never done before)... still no luck!

So I followed the post from Aviko (on this forum)

ok lets start from scratch, try this:

put some isolation under connector to heads (paper plastic etc.) motor have to be connected. power up drive. enter terminal, press ctrl+z.

and this i am not sure, i havent any 7200.11 here to check, you have to try

first try:

wait until motor stops itself. then enter /2 and Z

if you got message spin down completed remove isolation from pcb and mha connector (mha - magnetic heads assembly)

screw on pcb to hdd. if you still dont get CC or CE its really good.

now wake up drive with command U

motor should be started and you should not get any error messages, otherwise you have to start again from begin.

when drive spins up, go to level T (just enter /)

now type F,,22

should appear message about restoring to defaults.

then

F3 t>/1

then

F3 1>N1

if drive goes back to prompt ask for further instructions
Now the drive is showing in the BIOS, but when I get into Windows it picks up the drive under device manager as a 2TB drive, but doesnt show under my computer.

Can you advise me as to what I might do to get around this?

Many thanks,
Richard from South Africa




1 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users


    Baidu (1)


How to remove advertisement from MSFN