Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 



Zenskas

Seagate Barracuda 7200.11 Troubles

Recommended Posts

MonStar    0

hi all,

I'm from germany and bought an external USB drive "Maxtor Basics Desktop 500 GB" two month ago

a few days ago i wanted to speed up the drive by removing it from the external case and using it as a normal internal hdd

after breaking it open the case revealed a ST3500320AS with firmware SD81 made in China

I attached it to my mainboard and voila, the bios didn't recognize the hdd

plugged back into the case it worked again.

Maybe the hdd is locked or something to work only inside the external case

or could it be possible, that it suffers from the busy problem, but the controller in the external case can read it anyway?

Someone here could try his hdd in an external case. the Maxtor Basics Desktop seems to be sold only in europe

I'll provide the exact data for the list next week, cause I'm not at my office over the weekend

Share this post


Link to post
Share on other sites

ToKuRo    0
hi all,

I'm from germany and bought an external USB drive "Maxtor Basics Desktop 500 GB" two month ago

a few days ago i wanted to speed up the drive by removing it from the external case and using it as a normal internal hdd

after breaking it open the case revealed a ST3500320AS with firmware SD81 made in China

I attached it to my mainboard and voila, the bios didn't recognize the hdd

plugged back into the case it worked again.

Maybe the hdd is locked or something to work only inside the external case

or could it be possible, that it suffers from the busy problem, but the controller in the external case can read it anyway?

Someone here could try his hdd in an external case. the Maxtor Basics Desktop seems to be sold only in europe

I'll provide the exact data for the list next week, cause I'm not at my office over the weekend

What!!?!?!?!! SD81 at last!!!! :blink: You're the first here that have the same firmware that I have!!! Mine is made in Thailand thou but... you say when it is in an enclosure it works but when it is connected directly to the sata port on the MB it does not??!?!?! **** I have not tried that!!!! On monday first thing is to buy a sata enclosure... Do I have to buy some special one or anything should work???

Saludos, ToKuRo.

Share this post


Link to post
Share on other sites
blichev    0

This article might be interesting: http://www.thefreelibrary.com/Find+Best+So.....-a01073926556

It shows the probable triggers for the problems.

The information in the article comes directly from Salvationdata and the links point to their website. I've found at least 3 other articles with similar info about 7200.11 disks posted on different article directories by salvationdata and linking to their website. This way they are getting more visitors to the webpage where they are selling their recovery software. Seems like they are making good money from the 7200.11 Problems.

Share this post


Link to post
Share on other sites
pichi    0

Interesting V lists: V1, V2, V4, V8, V10, V20, V40, V80, V100

If anybody can obtain V lists of goods hdds or differents V lists, please post the results.

To compare files I use "Total Commander": http://www.ghisler.com/download.htm

Common V lists of wrongs hdd (and similars):

------------------------------------------------------------

F3 T>V1 (identical)

User Slip Defect List

log log log phys phys

LBA span cumm cyl hd sctr zn cyl sctr SFI

0 0 0 0 0 0 0 0 0 6 (or 7)

Head 0: entries 1 slips 0

Head 1: entries 0 slips 0

Head 2: entries 0 slips 0

Head 3: entries 0 slips 0

Total Entries 1 Total Slips 0

------------------------------------------------------------

F3 T>V2 (similar, except *)

System Slip Defect List

log log log phys phys

LBA span cumm cyl hd sctr zn cyl sctr SFI

0 0 0 0 0 0 0 2**** 0 FFFFFFFF

***** 39C 39C 0 1 0 1 2**** 0 FFFFFFFF

***** 39C 738 0 2 0 2 2**** 0 FFFFFFFF

***** 39C AD4 0 3 0 3 2**** 0 FFFFFFFF

***** 39C E70 ** 0 0 4 2**** 0 FFFFFFFF

***** 39C 120C ** 1 0 5 2**** 0 FFFFFFFF

***** 39C 15A8 ** 2 0 6 2**** 0 FFFFFFFF

***** 39C 1944 ** 3 0 7 2**** 0 FFFFFFFF

Head 0: entries 2 slips 39C (why only the middle of 738?)

Head 1: entries 2 slips 738

Head 2: entries 2 slips 738

Head 3: entries 2 slips 738

Total Entries 8 Total Slips 1944

------------------------------------------------------------

F3 T>V4 (identical)

Reassigned Sectors List

Original New log log log phy phy

LBA PBA cyl hd sctr zn cyl sctr SFI hours msec

Alt Pending Total Alted Total

Entries Entries Entries Alts Alts

Head 0 0

Head 1 0

Head 2 0

Head 3 0

Total 0 0 0 0 0

Total Alt Removals: 0

Checksum = 0000

------------------------------------------------------------

F3 T>V8 (identical)

Servo Flaws List

Log head 0: entries 0

Log head 1: entries 0

Log head 2: entries 0

Log head 3: entries 0

Total Entries 0

------------------------------------------------------------

F3 T>V10 (differents, but there are two details)

P List

log log phy length

head cyl cyl in symb SFI flags

0 0 0 ** ***** 80 scr fill

1 *** *** 3 E1BA6 80 scr fill

1 *** *** 803 E17A6 80 scr fill

1 *** *** 3 E1BA6 80 scr fill

...

Detail 1: Is 803 an overflow?

Detail 2: When appear 80X the SFI value is 0x00400 lower than nearest neigbours.

------------------------------------------------------------

F3 T>V20 (differents)

Servo Flaws List

log log phy

head cyl cyl wedge status

0 0 0 **

1 **** **** **

...

------------------------------------------------------------

F3 T>V40 (identical)

Nonresident GList 0 entries returned

Total entries available: 0

PBA Len Flags Phy Cyl Hd PhySctr SFI

------------------------------------------------------------

F3 T>V80 (identical)

Resident GList 0 entries returned

Total entries available: 0

PBA Len Flags Phy Cyl Hd PhySctr SFI

------------------------------------------------------------

F3 T>V100 (similar, except *)

Primary DST List 0 entries returned

Total entries available: ***

PBA Len Flags Phy Cyl Hd PhySctr SFI

------------------------------------------------------------

Edited by pichi

Share this post


Link to post
Share on other sites
MonStar    0
What!!?!?!?!! SD81 at last!!!! :blink: You're the first here that have the same firmware that I have!!!

no, I think in the list is at least one with a SD81, too

Mine is made in Thailand thou but... you say when it is in an enclosure it works but when it is connected directly to the sata port on the MB it does not??!?!?! **** I have not tried that!!!! On monday first thing is to buy a sata enclosure... Do I have to buy some special one or anything should work???

the Maxtor enclosure could be especially "tuned" for the barracuda, because Maxtor belongs to Seagate so I don't know if it works with any other enclosure

to straighten that out: I don't know if my hdd is really "busy" or if it's locked somehow by Maxtor/Seagate to work in the enclosure only,

the only thing I know is it works in the enclosure, but not with my mainboard (Gigabyte GA-K8N51PVMT-9 with nForce 430)

if anyone has any USB external SATA enclosure, please test it with your "busy" barracuda and report back

Share this post


Link to post
Share on other sites
icefloe01    0
What!!?!?!?!! SD81 at last!!!! :blink: You're the first here that have the same firmware that I have!!!

no, I think in the list is at least one with a SD81, too

Tokuro himself was the other one with SD81...

Share this post


Link to post
Share on other sites
pichi    0

Questions:

Chronological firmwares:

SD04 and SD14 -> I don't know if it has timebomb virus

AD14 -> With timebomb virus

SD15 -> With timebomb virus

SD... -> With timebomb virus

Is there anybody with a version before AD14?

Is possible udate the firmware to SD04 or SD14?

Why Seagate help to update from SD04 or SD14 to AD14 and dont help to solve ours problems?

Are there anything important on SD04 or SD14?

Have SD04 or SD14 0GB problems?

(The smaller cache isn't a very important problem)

http://www.seagate.com/www/en-us/support/d...wnloads/cuda-fw

See "drives with previous version of firmware (SD14) report no such failures" at:

http://forums.ncix.com/forums/?mode=showth...roduct_id=26387

Edited by pichi

Share this post


Link to post
Share on other sites
artpav    0
What will be recommendations regarding new 1TB driver vendor. Well, I would say we need to replace all that 1TB ST31000340AS drives with something else.

1) Hitachi HDS721010KLA330 - didn't mess with this company since IBM similar "nice" story. Are they any good in this days? They could be ok.

2) WD - hmmh, I had some really bad experiences with WD in the past

3) Samsung HD103UJ - users also reported some dead drives

What you will buy as Seagate replacement or what you already bought?

Cheers

Yeah, there aren't many brands to choose from, I picked Samsung HD103UJ 1TB for internal and WD Mybook 2TB Mirror for external, just to spread my chances, without being loyal to one particular brand.

Reading reviews didn't help, because for every happy customer, there's always a 1 star rating saying it died on them, and a suggestion to buy another brand, you go to check on other brand and they say the exact same thing, so..

Current Seagate 7200.11 line is clearly defective (this has also been confirmed in private conversation with someone from Seagate), other brands drives may fail, but from natural causes and on rare occasion.

Share this post


Link to post
Share on other sites

I've got a seagate freeagent 250gb external USB enclosure with a drive currently in it. I will research how to disassemble this and do it here in a few hours hopefully, then plug the brick drive up and report on my results. Wish me luck.

Share this post


Link to post
Share on other sites

Failure. It was a Freeagent Desktop 7200.10 250gb but the drive I'm trying to resurrect is a 7200.11 500gb, so I'm sure that is why I didn't get any response in windows no matter what variables I tried with cables and connections. Taking apart the drive was easy if you're not too squeamish about destroying a stout plastic housing or two with a sharp knife and using a tiny screwdriver on the vital bits. Took me about 20 minutes. Also tried plugging up the drive back on normal sata afterward hoping that the sata-usb controller might have reset the drive somehow but nah, nothing. Still bricked, but I tried.

Share this post


Link to post
Share on other sites
rainshower    0

@ DerSnoezie: thank you for your impressive chart!

Yes, my drive is also OEM although I bought it directly from a big store (mediamarkt) in Berlin. I'll attach a foto of my drive, because I don't know why the model number above (ST3500820AS) differs from the model number below the "mic"-logo, which is STX-ST3500320AS . Maybe anybody can tell me?

BTW, my firmware-number is SD25, as shown on the picture, so I don't quite know why my item in the list was changed. Please see my original post #216. I'm number 12 in the list, and I bought my drive in July 2008 (so the date-code 26/Ago/2008 must somehow be wrong)

Thank you for help, and I'm glad I found this forum. It's a good feeling not to be alone with all these problems.

post-226515-1231644504_thumb.jpg

Share this post


Link to post
Share on other sites
seahateHDD    0

Finally got my comp set up right again with all software back an and configured in vista (in out the box as a prebuild) mostly anyway, still got to sort linux install and that's a pain since I will compile/build most from source and use a self compiled vanilla kernel too so it's time consuming. I have new comp (same model etc) as my warranty meant had to return whole rig as opposed to just the hdd.

It's not a virus since I mainly use linux (slack based) and have avira (in vista too) and I do regualr housekeeping and scans. That was main net active OS at the time of my failure (dec failure, bought in nov), drive is thai on fw HP24. Behind hw/sw firewalls and due to set up and nature of my primary OS there is no way a virus got on without me letting it through and I don't open holes in security nor have I downloaded anything that could potentially contain malicious code so it rules that one out I think.

Share this post


Link to post
Share on other sites
barakaspeed    0

Count me in for this too!! :( Unfortunately I haven't made a good back up in a while and lost 6 months of pics of my 18 month old son. :( So I'm pretty desperate for a solution. Here's an update:

ME--> 36:9QM2****:ST3500320AS:9BX154-303:SD15:08381:KRATSG:JUL2008:05JAN2009:OEM:BARAKASPEED:THIALAND

01:9QM7VZBP:ST3500320AS:9BX154-303:SD15:09146 (09/Oct/2008):KRATSG:Oct2008:24Dec2008:poolcarpet:Malaysia

02:9QM6X90B:ST3500320AS:9BX154-303:SD15:09115 (17/Sep/2008):KRATSG:Oct2008:28Dec2008:DaftMule:United Kingdom

03:9QM6W2JE:ST3500320AS: - :SD15: - : - :5Dec2008:19Dec2008:DerSnoezie:Netherlands (no detect in bios)

04:9QM4G4PK:ST3500320AS:9BX154-303:SD15:08503 (16/Jun/2008):KRATSG:Aug2008:Nov2008:dskbrk

05:9QM3RWHJ:ST3500320AS:9BX154-568:SD81:08464 (20/May/2008):KRATSG:Aug2008:23Dec2008:ToKuRo:Chile (no detect in bios)

06:9QM7KSQJ:ST3500320AS:9BX154-501:SD15:09134 (30/Sep/2008):KRATSG:28Oct2008:07Jan2009:jeroen__online:Netherlands

07:9QM2MFS6:ST3500320AS:9BX154-303:SD15:08406 (10/Apr/2008):KRATSG:12Apr2008:23Dec2008:quattro150:Malaysia

08:9QJ0XJ01:ST31000340AS:9BX158-303:SD15:08496 (12/Jun/2008):KRATSG:Aug/Sep2008:8Jan2009:Nichev

09:9QM717SF:ST3500320AS:9BX154-303:SD15:09114 (16/Sep/2008):KRATSG:13Oct2008:14Dec2008:PrOdiGy1:UK

10:9QJ1LESR:ST31000340AS:9BX158-303:SD15:09063 (11/Ago/2008):KRATSG:Nov2008:27Dec2008:AVINNC:USA

11:9QJ1AGEV:ST31000340AS:9BX158-303:SD15:08515 (2/Jul/2008):KRATSG:Aug2008:4Jan2009:Ruddrage:UK

12:9QM6354J:ST3500820AS:9BX134-505:SD15:09084 (26/Ago/2008):KRATSG:July2008:20Dec2008:rainshower:Germany

13:9QM33FL8:STM3500320AS:9GT154-325:MX15:08396 (03/Abr/2008):KRTASG:Sep2008:30Dec2008:fabio.cillo:Italy

14:9QM*****:ST3500320AS:9BX154-303:SD15:08367 (14/Mar/2008):KRATSG:Dec2007:Dec2008:Death_Angel:Malaysia

15:9QK*****:ST3750630AS:9BX146-621:HP24:08511 (21/Jun/2008):TK:Oct2008:7Jan2009:Taiketo

16:5QJ*****:ST1000340AS:9BX158-303:SD15:09121 (20/Sep/2008):WUXISG:October2008:28Dec2008:Styleman

17:9QM8DRHL:ST3500320AS:9BX154-303:SD15: - (13/Oct/2008):KRATSG:06Dec2008:24Dec2008:roadstarter:Philippines

18:9QM6****:ST3500320AS:9BX154-303:SD15:09076 (21Aug2008):KRATSG:15Oct2008:29Dec2008:labraticmp3:USA

19:9QM6****:ST3500320AS: - : SD15 - : - : Oct2008:2Jan2008:eli2k

20:9QM5****:ST3500320AS:9BX154-303:SD15:09063 (11/Ago/2008):KRATSG:6Nov2008:27Nov2008:poim76

21:9QM2CHR4:ST3500320AS:9BX154-303:SD15:08382 (23/Mar/2008):KRATSG:August-08:Nov-Dec-08:caba212:Spain

22:9QJ15ZBN:ST31000340AS:9BX158-303:SD15:08496 (05/Jun/2008):KRATSG:July2008:26Dec2008:GrayGhost:USA

23:9QM27S5F:ST3500320AS:9BX154-303:SD15:08381:DEC 08:JAN 09: timha

24:9QJ0****:ST31000340AS:9BX158-303:SD15:08495:KRATSG:Oct2008:02Jan2009:viniciusferrao:Brazil

25:9QM60864:ST3500320AS:9BX154-303:SD15:09076:KRATSG:31 October 2008:Dec 2008:RiderZen:Australia (BSY)

26:9QJ0W41R:ST31000340AS:9BX158-335:SD15:08457 (16/May/2008):KRATSG:Jul2008:20Dec2008:Macprk:USA

27:9QM5V5HQ:ST3500320AS:9BX154-303:SD15:09071:KRATSG:(04/Nov/08):(09/Jan/09):BigSilverHotdog:USA

28:9QM2C4LT:ST3500320AS:9BX154-303:SD15:08382(??):KRATSG:Aug2008:1Jan2009:Keddar:USA

29:5QM1EYCG:ST3500320AS:9BX154-303:SD15:08383:WUXISG:jUL2008:02Jan2009:waly2k1:Argentina (no detect in bios).

30:9QM5RCNT:ST3500320AS:9BX154-303:SD15:09063:KRATSG:JUL2008:25DEC2008:criverock:Italy (no detect in bios).

31:9QM*****:ST3500320AS:9BX154-303:SD15:09076 (21Aug2008):KRATSG:Oct2008:20Dec2008:sarahcoco:France

32:9QJ*****:ST31000340AS:9BX158-303:SD15:09104 (10/Oct/2008):KRATSG:3Jan2009:artpav:Canada

33:9QM*****:ST3500320AS:9BX154-303:SD15:08371 (15/Mar/2008):KRATSG:7May2008:29Dec2008:KillerB :Korea (no detect in bios)

34:5QJ0****:ST31000340AS:9BX158-303:SD15:09045:WUXISG:CHINA:August2008:Dec24th08:Fuzzy_3D:Canada

35:9QJ0GLEX:ST31000340AS:9BX158-303:SD15:08356 (06/March/2008):KRATSG:March2008:Jun2008:TheName:Croatia

36:9QM2****:ST3500320AS:9BX154-303:SD15:08381:KRATSG:JUL2008:05JAN2009:OEM:BARAKASPEED:THIALAND

I did some general hdd failure searching and found various (not relating to this seagate issue) where people replace the pcb with an exact drive to recover the drive. Any thoughts on this? I admit I'm not entirely sure what this entails, but seems interesting. I would surely but another ~$60 drive and swap the pcb boards for data recovery. Actually I'll probably have to break down in a couple months and pay for professional recovery if nothing turns up with this issuee...

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.

×