toptenandrew
Content Type
Profiles
Forums
Events
Posts posted by toptenandrew
-
-
Ok so slightly different topic here....I have used this method to fix numerous drives for myself and others....now I have a Seagate SAS drive that is having issues. I tried using my connector that I used for the SATA drives but when I pull up PuTTY, I am not getting any response in the terminal. I know the connector I have still functions because I am able to use it with SATA drives still just fine. Does anyone know if the Pin-Out for Tx-Rx is different for the Barracuda SAS drives, or is there a different set of variables in PuTTY that I need to use? Or is there some other solution altogether? Or is it just not possible?
I have looked online everywhere, and no one seems to have a straight answer for this. The drive is out of warranty and I just want to know if getting it back online is even possible or if this is going to be a straight data recovery center issue. If the good folks here can tell me if this can even be done for this type of drive or not, I would greatly appreciate it. Thanks.
0
Issue with Failed Seagate Cheetah SAS Drive
in Hard Drive and Removable Media
Posted
Hey guys, just trying to find a completely solid yes or no on this question, not just guesses/maybes. I know that getting into the terminal of a Barracuda drive is possible and actually relatively easy, as I have done it. However, is it possible to also get into the terminal using the same methods for a Cheetah SAS drive (ST3450856SS)? I have tried using the same adapter that I used for my SATA drive, but I get no response when I open putty, not even a command prompt, just black screen. Have done a loopback test so I know the adapter is working fine. Is the TX-RX pinout different on the rear of an SAS drive than on a SATA drive? Different baud rates? Or something else altogether? I have also seen posts about having to jump pins on the PCB in order to get terminal to work. Could this have something to do with it?