Jump to content

Seagate Barracuda 7200.11 Troubles


Recommended Posts

So guys is it anyone that have sent their affected drive to Seagate for free data recovery on a replacement drive yet?

I called to them, they confirmed free data recovery, but they asked to call back on Tuesday.

Link to comment
Share on other sites


one think you could try to get your data off the faulty drive is to buy the exact same model again if you can get it and take (from the new drive) the controller board and fit it onto the older drive and if the BIOS on the old drives controller card is what's at fault you should be able to get your data off

sorry if someone's posted this info earlier in the thread already ;)

Link to comment
Share on other sites

one think you could try to get your data off the faulty drive is to buy the exact same model again if you can get it and take (from the new drive) the controller board and fit it onto the older drive and if the BIOS on the old drives controller card is what's at fault you should be able to get your data off

sorry if someone's posted this info earlier in the thread already ;)

It doesn't work at all!!!

Edited by lavan
Link to comment
Share on other sites

it finally seems that seagate is s*****g in their pants, good for them :thumbup

my issue is that using their online serial number checker it says that my drive is not affected :blink: how can that be? a

anybody else got the same response?

Link to comment
Share on other sites

I have an ST31500341AS, Firmware CC1H, is it affected or not?

seagate support says not yet affected, whatever that means

Thanks alot, so we will wait and see what ahppens, has anybody got an answer to their support email yet?

Btw, what's the difference between CC1H and SD1A? As far as I know, they are not interchangeable, so what's the difference between the hardware?

Since there is an online serial checking tool available from Seagate, I have started a new thread in order to compare which drives may be affected:

http://www.msfn.org/board/index.php?showtopic=128793

Edited by Jackie78
Link to comment
Share on other sites

Covered in Computerworld now: http://www.computerworld.com/action/articl...ticleId=9126280

And link to the online serial tool checker:

http://support.seagate.com/sncheck.html

Mine are Model: ST31500341AS P/N: 9JU138 - 300 Firmware: SD17 and it says they are not affected. I think this refers to the 0GB / gone from the BIOS bug, not the freezeing on RAID configurations which I guess is fixed by the previous firmware update (SD1A).

Link to comment
Share on other sites

Is it me, or is that serial checking tool crap? Or are the users telling crap? If I look at this thread:

http://www.msfn.org/board/index.php?showto...mp

And enter some of the fully readable serial numbers of people whose drives have already failed to the seagate online checking tool, it keeps telling me that these drives are NOT affected.

What now? :(

Edited by Jackie78
Link to comment
Share on other sites

I think it's pretty clear that Seagate doesn't know the full extend of the problem or don't want to go public with it. The KB page says that the defective drives were manufactured in Dec 2008 but clearly there are lots of people who had their ST31500341AS failing as early as Oct 2008.

Link to comment
Share on other sites

:thumbup :thumbup :thumbupSeagate offers fix, free data recovery for bricked Barracudas :thumbup :thumbup :thumbup

http://techreport.com/discussions.x/16246

Am I missing something?

1) "Seagate has isolated this issue to a firmware bug affecting drives from these families manufactured in December 2008" (from http://seagate.custkb.com/seagate/crm/self...sp?DocId=207931 )

2) The original forum at seagate.com was created in November 2008, and for many bricked drives the purchase time is November or earlier (see http://forums.seagate.com/stx/board/messag...ding&page=1 and http://www.msfn.org/board/index.php?showtopic=128514 ).

My guess is that they meant "before December 2008" or "before January 2009". Can people with bricked drives confirm that their serial numbers test positive at http://support.seagate.com/sncheck.html ?

Thanks

Link to comment
Share on other sites

*sigh* it sez mine is not affected... bull crap...

i punched in a few others on the list, and I noticed that most of the drives before aug/sept show up as not affected, and the later one are affected... just a coincidence? or are they trying to minimize the damage by only limiting this to a few ranges of S/N?

Link to comment
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.
×
×
  • Create New...