Jump to content

baws

Member
  • Posts

    5
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Sweden

Posts posted by baws

  1. Yep :), but the real problem (besides geographical distance) is that we know very little about a single (actually two) very specific issues originating from a same very specific firmware implementation on a different (though similar) drive, the 7200.11, and we know even less :w00t::ph34r: on these "LP Green" things, specifically we have a single "vague" report of success coming from a post on the Seagate board, quoted here:

    http://www.msfn.org/board/topic/150475-st2000dl003-seagate-barracuda-lp-green-2000gb-suddenly-ceases/?p=990707

    and (maybe) a single "even more vague" confirmation:

    http://www.msfn.org/board/topic/150475-st2000dl003-seagate-barracuda-lp-green-2000gb-suddenly-ceases/?p=1091946

     

    Please do note how the ONLY (as said "vague" and not properly confirmed) source runs only a "i" command that clears (possibly without any real need :unsure:) the g-list and then runs just a "N" command (clearing the S.M.A.R.T.) and EXPLICITLY tells you to NOT run any "m" commands:

     

    DONT GIVE m0,2,2,,,,,22 m,6,2,,,,,22 OR ANY SAME

    ALL THE TERMINAL LOG AS YOU CAN SEE REGARDING "No HOST FIS-ReadyStatusFlags 0002A1E1" THIS IN THIS POST ARE VICTIM OF THIS M-FORMAT COMMAND AS PER MY KNOWLEDGE EVEN I HAVE MADE SAME MISTAKE.

     

     

    and we have at least a confirmation that running the  "m0,2,2,,,,,22":

    http://www.msfn.org/board/topic/161029-seagate-barracuda-lp-green-is-not-recognized-in-bios-suddenly/

     

    actually further "bricks" the device into a "No HOST FIS-ReadyStatusFlags 0002A1E1" :(.

     

    jaclaz

     

    Ohh man.

     

    Not good at all, why can´t the technicians at seagate give an answer on this?

    Damnit!

×
×
  • Create New...