Jump to content

psm321

Member
  • Posts

    7
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

About psm321

Profile Information

  • OS
    none specified

psm321's Achievements

0

Reputation

  1. Thanks jaclaz. I had read the "read me first" and understand the point about getting the data off before attempting to flash the firmware, and about firmware updates being risky. What I was wondering was if I do decide to update the firmware after grabbing the data, what goes on it. That is indeed answered in the discussion you linked me to, and I apologize for not searching for it ahead of time and wasting thread space/your time.
  2. My brother's friend has a 7200.11 that's exhibiting all the same symptoms of the BSY problem. It's from an HP computer and has HP24 firmware. I'm probably going to take a crack at it since I already have the right cable setup. If successful, what needs to be flashed afterward? Is there a newer firmware from HP? Or do I need to put SD1A on it? And if SD1A, will it just flash, or do I need to force it? (I can probably find forcing instructions myself because I know I've seen them, but if somebody has a link handy it would be appreciated) Thanks!
  3. Oops, I've been using Ctrl+z all along (but still uppercase on non-Ctrl commands)... could this be my problem? Seems unlikely because I got the prompt, but wanted to double-check.
  4. ...*could* explain why these commands are not recognized Hi all, I got approval from Seagate to send my drive in to i365 for a free attempt at fixing the firmware. I'll probably be sending it in either tomorrow or the next day. If there's anything else folks want me to try (for identification / attempts to categorize this particular problem) before I send it in, please let me know soon! After I get the drive back, I'll post a summary of my experience and the results (or would that be off-topic in this thread?)
  5. I sure hope not. I did find some posts on the Seagate forums with people having success sending it in. I think I'll give it a try today given my results below. Interesting... I had assumed it loaded the diag commands off the platter because if I do a Z/U cycle with the contacts still disconnected, and it fails to spin up because of that, then attempting to run the N1 command gives me "Unable to load Diag Overlay". Package Version: MS011B.SDD1.AD090G., Package P/N: 100518333, Package Builder ID : 3K, Package Build Date: 05/27/2008, Package Build Time: 12:39:16, Package CFW Versio n: MS01.SDD1.00075442.3K00, Package SFW1 Version: B100, Package SFW2 Version: C0FE, Package SFW3 Version: -- --, Package SFW4 Version: ---- Controller FW Rev: 05271239, CustomerRel: SX15, Changelist: 00075442, ProdType: MS01.SDD1, Date: 05/27/2008, Time: 123916, UserId: 00000761 Servo FW Rev: B100 RAP Format Rev: 0092, Contents Rev: 15 05 10 08 TetonST 2.0 SATA Moose Gen 3.0 (RAP fmt 10 ) w/sdff (RV ) Product FamilyId: 27, MemberId: 02 HDA SN: 9Q******, RPM: 7206, Wedges: 108, Heads: 8, Lbas: 74706DB0, PreampType: 47 08 PCBA SN: 0000C8380EPK, Controller: TETONST_2(639D)(3-0E-3-5), Channel: AGERE_COP PERHEAD_LITE, PowerAsic: MCKINLEY Rev 51, BufferBytes: 2000000 Package Version: MS011B.SDD1.AD090G., Package P/N: 100518333, Package Builder ID : 3K, Package Build Date: 05/27/2008, Package Build Time: 12:39:16, Packag n: MS01.SDD1.00075442.3K00, Package SFW1 Version: B100, Package SFW2 Version: C0FE, Package SFW3 Version: -- --, Package SFW4 Version: ---- Controller FW Rev: 05271239, CustomerRel: SX15, Changelist: 00075442, ProdType: MS01.SDD1, Date: 05/27/2008, Time: 123916, UserId: 00000761 Servo FW Rev: B100 RAP Format Rev: 0092, Contents Rev: 15 05 10 08 Features: - Quadradic Equation AFH enabled - VBAR with adjustable zone boundaries enabled - Volume Based Sparing enabled - IOEDC enabled - IOECC enabled - DERP Read Retries (I blocked out the serial number so Seagate doesn't know I tried to do this myself) Seeing the SX15 here brings back recollections that the other drives in my set were in fact also SX15 even though the labels say SD15. This matches this guy: http://www.dslreports.com/forum/r22209346- http://www.dslreports.com/forum/r22237565- who also has a drive labeled SD15 but with SX15, the BSY problem, and the same "Unknown Diag Cmd Failure 12CC4" error message. Thanks!
  6. Hi, Yes, it's a 7200.11, model ST31000340AS. The label on the drive says firmware SD15 and I'm pretty sure I never updated it. Once it "died" [spins up fine, no bad sounds, but doesn't seem to exist to the computer] I did go and update the other drives in the set and those were all at SD15 before update. Yes, I'm issuing the N1 command at the "F3 1>" prompt I get after saying "/1" Thanks! Edit: Interesting side-note: probably not relevant to the problem, but I bought these drives as retail kits from the Fry's website, and still have the original retail kit boxes, yet all 4 of the drives say "This drive is manufactured by Seagate for OEM distribution. For product information or technical support, please contact your system OEM." Interestingly, the boxes have 2 layers of model/serial number stickers on them... makes me wonder if Fry's was doing something shady. I foresee a fight with Seagate if I end up having to send the drive in to them for their free recovery.
  7. Hi all, I am trying to recover my 1TB 7200.11 from BSY lock. After I enter the "N1" command, I get "Unknown Diag Cmd Failure 12CC4". Like the other 2 posters I found on here with this problem, I got my drive (online) from Fry's, but in every respect it looks like a normal Seagate drive. I did not power down the drive at any point during the process, and have double-checked to make sure I followed it correctly. I can spin down and spin-up the drive and it sounds normal. The last time someone posted with this problem, they were requested to do "/C" and then "Q" to get a list of available commands, but they never responded. I tried that, and get the same "Unknown Diag Cmd Failure 12CC4" when I try to run "Q". Any ideas would be appreciated. I have looked through the search results within this thread for "unknown diag cmd failure" already [edit: to remove search link that was session-based and include search terms instead] Thanks!
×
×
  • Create New...