Falcon7

Well NO. HP fails to say explicitly that it is for Windows 7, which is a different thing from what you seem like fearing, i.e. that the HP26 is incompatible with Windows 7. I guess we are talking of this one: http://h10025.www1.hp.com/ewfrf/wc/softwareDownloadIndex?softwareitem=pv-68339-3&lc=en&dlc=en&cc=us〈=en&os=2100&product=3740339 Now, use some logic. IF it was that this firmware is incompatible with Windows 7, it would mean that you couldn't migrate from any of the previous OS to Windows 7 - a bit hard to believe . (judging from the way Windows 7 is "pushed", MS would sue HP immediately ) If you check the HP ftp site: ftp://ftp.hp.com/pub/softlib/software10/COL27451/pv-68339-1/ you will see that the firmware file has a date of: 06/05/2009 Now, having Windows 7 been released on 22nd July 2009, it should mean that the HP guys had not a crystal ball capable of forecasting the furture over a larger than two months span. http://en.wikipedia.org/wiki/Windows_7 http://windowsteamblog.com/windows/b/windows7/archive/2009/07/22/windows-7-has-been-released-to-manufacturing.aspx However rest assured, drive firmware is OS agnostic, and since the actual updating is done from a DOS based .iso there wouldn't be problems with compatibility during the update either. In case of problems with the self extracting exe: http://h30434.www3.hp.com/t5/Hardware/HP-firmware-update-for-Seagate-drive-fails-sp40966-exe-upgrades/m-p/55596 use 7-zip to extract the contents and burn the .iso manually. jaclaz Thanks jaclaz, it's now updated to HP26.

If it's an OEM drive with HP-firmware and HP26 is the latest: yes, just like Jaclaz said HP says firmware upgrade HP26 is not for Win7!

Very well said. NO. I'll try again to break down the structure in priorities for you: Facts: you have a bricked drive this drive is bricked presumably because a stoopid software in the drive has been made in such a way that every time you position 320 of the log (or multiple mod 256) is hit , the drive gets bricked when powered on you have valuable DATA on the drive, but not valuable enough to pay several hundred dollars to a recovery firm, or however you want to take your chances trusting a bunch of crazy people on an internet forum and follow the procedure suggested PRIMARY Objective: save your otherwise UNbacked up DATA by having a TEMPORARILY functional unbricked drive [*]SECONDARY objective (SUGGESTED): set things so that such a problem won't happen again (learn from experience=BACKUP!) [*]TERTIARY objective (OPTIONAL): attempt to have the once bricked drive fully functional or have a new working one THEN: Procedure to reach PRIMARY objective : unbrick the drive as per instructions image (or however copy/recover the DATA in it) to another, surely working, drive [*]Procedure to reach SECONDARY objective: make an additional copy (better, TWO of them) of the data on different media [*]Procedure to reach TERTIARY objective (IF first two succeeded): test thoroughfully the unbricked drive IF anything is not OK, and if under warranty RMA it IF RMA is not possible or the drive shows no errors, decide if you prefer: to throw into the dustbin the stoopid drive anyway OR to continue using it IF you chose to continue using it, decide IF: you prefer NOT to risk a firmware upgrade of the firmware and you will likely need to unbrick it again after no less 6 to 12 months of "normal" use, many more months if you don't powercycle it often OR you prefer to risk a firmware upgrade IF you decide to perform a firmware upgrade, choose the firmware file wisely In other words, updating the firmware is the LAST and LEAST of your problems, and you have at least 3 months of time (since a hopefully successful unbricking ) for safely deciding whether you really want to upgrade it and do researches to find out which is the "right" firmware. Now, the fact that it bricked last Friday, may be a problem, but only if it was full moon where you live. Apart from that, you should have no problems in reaching the important objective: GET YOUR DATA BACK by following the suggested procedures (EXACTLY AS DESCRIBED). jaclaz Thanks everyone, worked perfect (verbatim as described by you guys and Carter) and that was for my (Seagate ST3500620AS from a HP computer with HP24 Firmware) Now do I try to upgrade the HP24 firmware to HP26 (I have win7 on the computer)? Oh yea, seatools for windows would not work to test the drive, it would see the drive and firmware but when I tried to run a test it says "Test unavailable". It would run a generic "Short Test". I guess that is a HP thing.

So this will not work (AT LEAST NOT EXACTLY AS DESCRIBED) for my Seagate ST3500620AS from a HP computer with HP24 Firmware which bricked last Fri. Correct? If anyone can help it would be greatly appreciated.

Sure it is labeled Seagate , point is that if it is also labeled with the HP logo and a HP part number. Post a photo of it if you are not sure, but if it has an HP firmware it is an HP OEM drive (unless someone already fiddled with it). jaclaz No HP logo at all on drive. I got the computer new, unopened box in Feb. 2009. So it must be an HP OEM drive. Thanks again.

If the drive is "labeled" HP it's an OEM drive and you should use the HP one. If the drive is labeled Seagate (no matter where it was installed to) use the Seagate one. (I suspect that there are not many differences between the two at actual code level) The main thing is that you run BOTH the Short and Long DST tests BEFORE updating the firmware, and if anything is not OK, you try to RMA the drive. Check also against point #5 Usually if you are within the terms of warranty (and shout aloud enough ) you can manage to have a replacement drive, at least from Seagate. jaclaz Thanks for your response, the drive is labeled Seagate, but the firmware is HP24. So now what? Thanks, again.

My Seagate ST3500620AS (from a HP computer) bricked last Fri. I just ordered parts to attempt this fix. My question, if I succeed and after back-up should I use the HP firmware update (sp40966.exe) or the (ms-sd1a.exe) from Seagate? Sorry if this has already been answered. I've been reading this for hours, but I may have missed it. And thanks so much for this forum!