Content Type
Profiles
Forums
Events
Posts posted by DerSnoezie
-
-
Number:9QM3****:ST3500320AS:9BX154-303:SD15:08411:KRATSG:2008/07/15:2009/01/16:OEM:Verdilith:UK:fail :Windows XP SP2:
DerSnoezie - I'm not sure that you've added my first fail (above), just the second one I posted - #106 on your list.
You're absolutely right, sorry about that! I've fixed it right away.
@ DerSnoezie : Hi!!!! I'm happy to announce that my disk is ALIVE AGAIN and all my data is OK and being backed up as I write this message. I've wrote more details about the procedure at the "7200.11 solution" post.Greets, ToKuRo.
That's great news! I'm glad you were able to recover your data
And @ dadou: Thanks for sharing your 7200.11 experience with us! I sure hope the procedure of the free data recovery service offered by seagate won't take ages B)
0 -
#104 9RY28***:ST3250410AS:9EU142-305:3.AAC:08306:TK:2007:2009-01-27:Flomon_2:Germany:Problems while Booting,then chkdsk with errors, next Booting not Detected in Bios:WIN Ultimate x64
Edit: Is it possible that it is the same Problem which evryone here has or is it another Problem?
I'm not sure.. The symptoms appear to be similar, but your model and firmware type tell me you have a 7200.10 drive.. If the disk is no longer recognised, regardless whether you check/exchange sata cables, try other sata ports on the mainboard and excluded the possibility of a faulty power supply or other external factors, then you should pretty much have pinnend it down to this type of issue. However, for now i can only say that the BSY bug seems to be restricted to the drive types mentioned at the seagate knowledge base:
http://seagate.custkb.com/seagate/crm/self...sp?DocId=207931
0 -
Now, let's estimate just 10% of 17,5 millions are unlucky and will have this problem so we have 1,75 millions HDDs, in other words, almost 2 millions worldwide I might said.
LOL, that's actually a pretty fat squirrel But i guess we'll never receive any feedback on the true numbers.
0 -
Glad to help. Here is the 500GB, also reasonably old:
110:5QM0****:ST3500320AS:9BX154-303:SD15:08241:2007-12-15:WUXISG:2008-01-27:N/A:OEM:NearlyGod:Netherlands:fine:Server2003:Chieftec450W
Great, they'll certainly be included in the next update of the figures, which will be after the next 50 or so entries. (or when interest for the issue completely dies, whatever happens first)
0 -
Hi, registered especially to help with this; I have a 500GB for which I'll have to power down some stuff, so that'll come later. This is a nice old 750GB:
109:3QK0****:ST3750330AS:9BX156-303:SD15:08222:2007-12-02:AMKSPR:2008-01-18:N/A:OEM:NearlyGod:Netherlands:fine:XPPro+VistaBiz:Antec500W
Ah mooi Op de main thread zag ik trouwens net een post met een verklaring van seagate die inzicht zou geven in de ware aard van het probleem, maar die moet nog worden geverifieerd.
http://www.msfn.org/board/index.php?showto...mp;#entry830686
0 -
Anything between 20,000 and 200,000 appears "reasonable".
Even taking the lowest of the "range", 20,000 is several times bigger than the initially assumed 800.
Is it one of those days where my understanding of English is failing AND my math skills lack any kind of precision?
jaclaz
The quite reasonable numbers you mentioned above certainly do not look like a "purple squirrel" to me. Thanks jaclaz!
0 -
9QM2****:ST3500320AS:9BX154-303:SD15:08394:2008-04-01:KRATSG:2008-05-20:2008-08-05:N/A:cooper2009:Germany:(no detect in bios):XPHome:230W
Pls, could someone update the sheet with the mfg/fail dates? I couldn't believe that this is all chance (most failures around xmas).
Thanks, I will be updating it today
9QJ0****:ST31000340AS:9BX158-303:SD15:08354:N/A:KRATSG:N/A:2009-01-16:OEM:ione:Finland::There was no mention of Finland on the list yet, so I decided to register and post the above data from a recently failed disk of mine. There has also been some reports of similar problems with Seagate disks in Finnish hardware forums, so I guess its safe to say that the problem probably is just as widespread here as it seems to be around the globe.
On my particular case with the 1TB Barracuda, the disk stopped responding to ata commands and was not detected on the next reboot or ever since. However, after several attempts I managed to get it detected on another computer with P965 chipset and its SATA-controller, but then again the disk didn't survive through Seatools long self-test. I'm probably going to try the SD1A firmware update next and see what happens.
NB. I was unable to decode manufacturing date from the actual date code, but my failed disk certainly was older than from December 2008. If anyone else can determine the exact manufacturing date from the date code above, please do.
Hi, I've added Finland to the map, thanks for your entry. As long as your drive is detected at Bios level you can perform the firmware update offered by seagate. BTW The actual manufacturing date of your disk is 4 march 2008.
0 -
Hi there, i'm from Norway and i don't see my country listed as affected. I do however get a new computer tomorrow with the Seagate 7200.11 500GB, and i got a question. Do i only update the firmware if i get any of these firmwares AD14, SD15, SD16, SD17, SD18, SD19? Or do i have to update no matter what version i got?
Our humble dataset is only a very small sample of the total amount of 7200.11 drives out there. Your country isn't listed because no one based in Norway has yet provided an entry. However, judging from the wide spread of the entries, this appears to be a large scale issue; even large enough for seagate to publically anounce a firmware update.. So chances are that you'll receive a faulty drive, depending on it's manufacturing date.
Check this link to the seagate knowledge base to find out if your drive will be needing a firmware update:
http://seagate.custkb.com/seagate/crm/self...sp?DocId=207931
0 -
Here's my details:
1:9QM1****:ST3500320AS:9BX154-303:SD15:08357:KRATSG:2008-xx-xx:2009-10-3:RETAIL:709394hk:HongKong:BSY:XP Pro:XXX
Thanks HongKong has been marked on the map.
0 -
99:9QM3****:ST3500320AS:9BX154-303:SD15:08406:2008-11-20:KRATSG:2009-01-22:RETAIL:ili:Israel:(no detect in bios):Vista64:620W
no my drive is not detected to!
Wow, the list is still growing! Israel will be added to the map.
0 -
DerSnoezie do you think, adding info about MB chipset could be a good Idea? I mean, there a lot of discussions on the internet about Nvidia Nforce4 chipset drivers making HDD's corrupt their MFT + when you run Zero Assumption Recovery 8.3 it tells you, that Nvidia IDE drivers are know to make problems in case of an intensive usage. I myself have a Gigabyte GA-8NSLI, it uses Nforce 4.
Hi GDR, the dataset is dedicated to specific problems (stated in my first post) with 7200.11 drives. However, if you would like to start a new topic based on this list concerning the particular issue you mentioned above, feel free to do so. Maybe you could PM members who provided an entry and ask if they will also add information about their chipset.
0 -
Thanks for the new entries! Kazakhstan has been added to the 7200.11 "plague" map.
Edit: Issues reported from Kazakhstan appear to be not directly related to our main problem, therefore Kazakhstan is removed from the map.
0 -
Now what am I gonna do with this brick?
- Save it. Maybe it'll make a good story for your grandchildren
- Trash it to get rid of your frustration with seagate
- Use it as guinea pig drive in other experiments
0 -
Not that I want to toot my own horn, but I spent many many many hours researching and spreading the word, especially in the original Seagate forum, spreading the news of this bug to PC review companies and review forums etc.
I am just glad we found the answer!!!!!!
BTW: PICHI messaged me, and the fix of the LBA=0 worked for him. We both put in a lot of collaborative time together and I am glad he was able to recover his data.
Thanks all!
G
Yes, credit where credit is due. Especially considering the tech stuff
0 -
Sure thing! B)
0 -
Great job Gradius!
And why did the guy above quote the entire fix?! Edit:LOL
BTW Maybe you should PM the moderator to ask if this topic could also be moved to the "sticky" section.
0 -
First of all: Thanks to all new members for sharing your 7200.11 data with us!
Second point: Please pay attention to the particular unfortunate experience below, which was reported by donnerzusel:
Long story short:-ST31000340AS with Firmware SD15 (working)
-Seagate support acknowledged that the drive is affected
-Seagate support suggests firmware upgrade to AD14
-upgraded firmware, drive bricked.
Thank you, Seagate.
We have repeatedly warned for the dangers of "upgrading" your firmware from SD15 to AD14, but now even some seagate support employees appear to be making this mistake.
0 -
I believe Seagate owes everyone involved a big apology, free data recovery, and new (hopefully better... ) drives.
Good work everyone.
And we greatly appreciate that the MSFN forum provided a solid & objective platform for our efforts!
0 -
Thats giid news...
But does anyone else have problems loging in on to the seagate support page?Everytime I try to create a new name, or log in with my old one, I get a message that my username/password combo may be incorrect, or my accesstime may be limited, or my region may be restricted...
They're most likely having problems processing the huge amount of visitors attracted by today's developments. Maybe you should try a little bit later or restart your browser..
0 -
Here is my data
9TE0****:ST31000333AS:9FZ136-100:LC15:09175:TK:Dez2008:08-01-09:RETAIL:aspro:Germany:no detect in bios:XP x64:Seasonic 380W
Well, this is a new 3 platter TB drive with a different firmware than SD15 so I dunno if it's related to the firmware problem of the 4 platter version but I hope so. Also my drive isn't acoustically working normal but is continuously attempting to spin up and then spinning down again.
Seagate has officially acknowledged the issue. Check out the links in the post above yours. And I'm pretty exhausted right now
0 -
Seems that today is a good day after all Thanks everyone for your tremendous efforts in building this thread and MSFN forum for being our host.
0 -
Sorry if I misunderstood...do you mean a main thread here or at the place I linked? Could you direct me to this fix/thread?
DRP
The main thread I linked above in post #72. Please scroll up.
0 -
Hey guys,
These folks have a fix for it, but they quickly took down the video for fear that people would find out their fix (they are data recovery professionals).
http://forum.hddguru.com/solution-for-7200...isk-t10714.html
Apparently it uses PC3000 data recovery tools.
DRP
Yeah, you should check the main thread for more info on that subject. BTW the PC3000 recovery kit costs several 1000's of dollars.
0 -
9QM62***:STM3500320AS:9BX154-303:SD15:09083:KRATSG:121108:160109:OEM:Schoolisoutfan:Germany:NO DETECT IN BIOS
Hi, thanks! Could you also add some info on your OS and power supply please?
0
Seagate 7200.11 fail & fine dataset
in Hard Drive and Removable Media
Posted
To all recent contributors: thanks for sharing your 7200.11 experience with our humble dataset
This side thread is mainly dedicated to collecting information and drawing attention to the BSY bug affecting seagate 7200.11 drives manufactured before January 2009.
Most current information and general rants can be found at the main thread (also located at the hardware hangout of MSFN forum):
http://www.msfn.org/board/index.php?showto...&start=1080
The issue has been reported online since October/November 2008 and seagate has indeed acknowledged it and released a firmware update to prevent your drive from being affected. However, this update can only be applied to drives which have not yet been affected. Presently seagate does offer a free data recovery service for drives disabled by this problem, but chances are that it will take them quite some time to process all requests.
Data recovery is also possible with various recovery kits (prices ranging from 500$ - several 1000$, for links see main thread), but for a low cost homemade solution see this thread (also located at the hardware hangout of MSFN forum):
http://www.msfn.org/board/index.php?showto...t=0&start=0