lavan Posted January 18, 2009 Share Posted January 18, 2009 My drive is bricked, but their serial number check thinks it's not affected.My tooSeagate ST3500320AS, Firmware SD15, manufactured on March 22, 2008Checker says it's not affected, but it's dead now!!! Link to comment Share on other sites More sharing options...
stormbow Posted January 18, 2009 Share Posted January 18, 2009 When I registered the drive it came up as soProduct: INTERNAL KIT 7200.9 FAMILYModel: ST3500641AS-RKThe drive identifies itself asModel Family: Seagate Barracuda 7200.11Device Model: ST3500320ASSerial Number: 9QM3D441Firmware Version: SD15User Capacity: 500,107,862,016 bytesSeagate just says check your serial number online. The online checker "Your drive 9QM3D441 is NOT affected"Doesn't give me a whole lot of confidence. I would like to know why the drive is okay if it says it has the affected firmware and why the serial number identifies as a 7200.9 series drive.It is currently running fine but I have zero confidence in it. Link to comment Share on other sites More sharing options...
Leigh.Wanstead Posted January 18, 2009 Share Posted January 18, 2009 (edited) 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.My hard drive S/N:9QJONXXX not effected. What to do? I got firmware:SD15. I purchased around 6 months ago. It was running fine now. I disconnected the drive around two days ago.So I can not get the firmware from seagate??? Edited January 18, 2009 by Leigh.Wanstead Link to comment Share on other sites More sharing options...
Madcoder Posted January 18, 2009 Share Posted January 18, 2009 I just checked from the web page and I have a large server FULL of the faulty drives. The Seagate tool says they ARE affected by the problem. However, my drives are ES.2 (NS) drives on a SAS controller, so they were already flashed to AN05 a long time ago. I am now wondering if they are still impacted or if they are impacted only if I had the original SN05 loaded that they came with. Anyway, I will let everyone know what support says in this particular scenario. Link to comment Share on other sites More sharing options...
PrOdiGy1 Posted January 18, 2009 Share Posted January 18, 2009 guys try using capital letters when entering the serial # on seagates checker site.this person is right!mine was affected when i entered my number in so i was wondering why so many others were having problems. i just put it in again in lower case and it tells me my drive is not affected. make sure you enter the letters in caps on the seagate checker!See this post if your serial number is coming up as not affected. also make sure there are no spaces when you enter into the field (this can happen if you are copying and pasting the number from somewhere) as that also messes up the search. pretty pants coding i have to admit! Link to comment Share on other sites More sharing options...
Madcoder Posted January 18, 2009 Share Posted January 18, 2009 One other thing to keep in mind is that they are obviously updating the situation as they learn more. For example, the KB article says it is only drives which were manufactured in December, but their serial number checker tool says my drives ARE affected, and they were manufactured long before December. Link to comment Share on other sites More sharing options...
Gradius2 Posted January 18, 2009 Share Posted January 18, 2009 (edited) One other thing to keep in mind is that they are obviously updating the situation as they learn more. For example, the KB article says it is only drives which were manufactured in December, but their serial number checker tool says my drives ARE affected, and they were manufactured long before December.No this is FALSE !Wasn't in December only, they really should meant UNTIL december are affected.I have two drives from August and they died.Btw the direct link is:https://apps1.seagate.com/rms_af_srl_chk/Gradius Edited January 18, 2009 by Gradius2 Link to comment Share on other sites More sharing options...
fatlip Posted January 18, 2009 Share Posted January 18, 2009 Hey all,The fix was released on a website for those of you with the RS-232 connection. See Gradius' post. From reading it, this should work. I have taken the PCB board off my drive possible 50-60 times without incident, but be extremely careful when unscrewing and screwing it back on with the power connected!!!!Thanks,G Link to comment Share on other sites More sharing options...
Shuky Posted January 18, 2009 Share Posted January 18, 2009 Fixing 0 LBA error:To correct 0 LBA error, you'll need to do a quick format in order to regenerate the partition, just with m0,2,2 and the rest can be left blank by putting only commas or filling out with zeros. At the end you need to use a "ValidKey" code, or 22. So we'll have to enter:F3 T>m0,2,2,0,0,0,0,22 (enter)Gradius,a question: Will the quick format wipe out / erase the existing data?Thanks, ArndNo, just use Partition recovery or "A-FF Find and Mount"and copy your data safely..i just yesterday do some translation recalculate , on my 0 LBA ST3320613AS. Link to comment Share on other sites More sharing options...
Leigh.Wanstead Posted January 18, 2009 Share Posted January 18, 2009 May I ask if seagate checker says the hard disk not effected and if I follow the conclusion to continue using the hard disk and do have the hard drive broken later. Will any compenstation for this legal ground? Link to comment Share on other sites More sharing options...
Gradius2 Posted January 18, 2009 Share Posted January 18, 2009 I created a new topic about the solution here:http://www.msfn.org/board/index.php?showtopic=128807Please, no offtopic there.Thanks,Gradius Link to comment Share on other sites More sharing options...
Shuky Posted January 18, 2009 Share Posted January 18, 2009 May I ask if seagate checker says the hard disk not effected and if I follow the conclusion to continue using the hard disk and do have the hard drive broken later. Will any compenstation for this legal ground?My ST3320613AS is also not affected, but 0 LBA is show ,and now repaired;) Link to comment Share on other sites More sharing options...
ViniciusFerrao Posted January 18, 2009 Share Posted January 18, 2009 Gladius2 method works? O.OAmagod! \o/ Link to comment Share on other sites More sharing options...
fatlip Posted January 18, 2009 Share Posted January 18, 2009 I have a drive on the way here now to see 100% if this works. It should be here within the hour.GGladius2 method works? O.OAmagod! \o/ Link to comment Share on other sites More sharing options...
tuning1 Posted January 18, 2009 Share Posted January 18, 2009 I have a drive on the way here now to see 100% if this works. It should be here within the hour.GGladius2 method works? O.OAmagod! \o/Data lost or okay Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now