DerSnoezie

Hi Richard, unfortunately we have not yet found a complete solution for recovering your data, but at: - page 2, post #30, you can find detailed pictures of the required hardware setup by fatlip - page 4, post #79, you can find pichi's instructions for removing the BSY flag after that still some additional steps are required to get the drive up and running.. My best advice is to PM pichi to find out about the details. *BTW if you add some further information we could also include your drive in the fail & fine dataset.

Thanks for the data meow! Have you currently shelved these drives, waiting for a segate firmware fix/recall? Or are you still using them for low importance tasks?

Hi Jackie78, we need some extra info to awnser your question, which can be found at the sticker on top of your drive: - Firmware version: SD.. - Datecode: (5 digits, start with a 0) - SiteCode: KRATSG, WUXISG or other.

Yeah and right now the news is spreading like a wildfire!

Lithuania! We will add your country to the map. Thanks for your info! Edit: Lithuania has been marked on the "plague" map.

For now you hold the unlucky record of having the oldest drive to brick out in the dataset.. Have you really hold on to the failed drive since June last year?!? wow..

The picture at the gizmodo link is pretty hilarious And look at the evergrowing number of reactions!

I am sorry for your loss.. Thanks for sharing your data though BTW It's time to get some sleep. See you all in about 9 hours or so.

A nice formal e-mail, including the "plague" worldmap (with a slightly altered title ofcourse) and the 7200.11 drive life trajectory figure based on the fail & fine list B)

Thanks, I get it now

looks like a little slip of the tongue to me BTW today I got this message when I tried to log in for some PM action: We're sorry, but you have been banned from using this site. * You have been banned for the following reason: Continuous violation of the Seagate Community rules and regulations. Edit: Oh and the Inquirer article has started to spread: http://www.electronista.com/articles/09/01...acuda.failures/ http://pchardwareblips.dailyradar.com/arti...drives_failing/

What is the full chain? PC ----USB----console-----serial cable------? special adapter ? ----- harddrive?

This case is a bit different, since these are both maxtor drives (according to the model entry), with one displaying exactly the same problem as we are reporting in seagate 7200.11 drives. But when comparing the firmware versions with that of seagate models the only difference apears to be a 2 character prefix, with your MX15 corresponding to the SD15 failures and MX1A being a later firmware update, which was officially launched by seagate to fix yet another problem (so called "freezing"). Up till now I haven't come across any cases of seagate drives with SD1A firmware failing due to the "no detect in bios/0GB disc size problem" so my best guess is that your second drive will be spared from those particular issues. BTW According to the date code calulator your second drive was manufactured quite recently; on 31-12-2008, to be precise and the defective drive on 06-09-08.

Visualization of the seagate 7200.11 fail & fine dataset at present: Look at the tightly clustered occurence of the failures.. What could be causing this?

Visualization of the seagate 7200.11 fail & fine dataset:

Thanks for your input I will add Turkey to the map later this evening! Edit: Reports of failing 7200.11 drives in Turkey have been marked on the 7200.11 "plague" map.

Thanks! Unfortunately seagate moderators do a darn good job preventing people from finding this thread. They blocked out all possibilties on their forum to link to this thread and alter or even delete our posts! We do have some small scale promotion going on at several forums, but for as yet we haven't got the resources to reach the bulk of neglected seagate customers.

Thanks! Unfortunately seagate moderators do a darn good job preventing people from finding this thread. They blocked out all possibilties on their forum to link to this thread and alter or even delete our posts! We do have some small scale promotion going on at several forums, but for as yet we haven't got the resources to reach the bulk of neglected seagate customers.

That's great news! I hope more articles will follow soon. BTW I could't resist leaving a link to our little thread Heh, I was about post asking about the link, refreshed the page instead and you had already fixed it. LOL Very interesting article. Now if only it were worthy of 20/20 picking up on it and blasting Seagate publically WORLDWIDE.

Countries currently reported to have been affected by the seagate 7200.11 "plague" marked in red (including a few countries of forum members which did report the problem, but haven't contributed their data to the fail & fine dataset):

Countries currently reported to have been affected by the seagate 7200.11 "plague" marked in red (including a few countries of forum members which did report the problem, but haven't contributed their data to the fail & fine dataset yet): Credits for providing the basic vector map go out to Lee Brimelow: http://theflashblog.com/?p=144

Check out the following post on the seagate forums! ***Turribeach Visitor Posts: 4 Registered: 01-11-2009 Turribeach Message 17 of 18 Viewed 9 times OK BradC, let's stay in topic. What does Seagate has to stay about this drive (the other hundreds) that are not recognized by our BIOS? What should we do as users to solve the problem? What firmware should be apply or where do we get our money back for a clearly faulty product? When are you guys going to start addressing these issues honestly, responsibly and seriously? Anyone with enough time to setup a website so that we can avoid "breaking" the Forum rules and discuss these issues between all the affected customers? Anyone with contacts in mainstream media so that we can get them to do an article on this?*** It seems that seagate moderators are doing a good job in preventing people to find their way over here.. So I send that guy a PM giving him google search instructions, since the link to this forum is also blocked in PM!!! Edit: and I typed "****" in the PM which was automatically changed to "darn" Edit: okay, I get the point now XD It's a shame I haven't got time to PM them all..

Can anyone give a confirmation on the validity of these commands? Pichi perhaps?

That is their standard awnser. Call centre employees have most likely been trained to give that reply to all customers who called in with this problem. When seagate employees publically admit there is a problem they're legally f*****. So that's why. Also check out the official seagate forum for complaints of more people who called seagate support and got the same awnser as you did..

Is this guy also from Canada? If so, this could be very convenient for some forum members. edit.. Nevermind.. I need some sleep. Toronto it is.