Hello,

I successfully established a connection to the diag console of my Seagate Barracuda 7200.11 and I am trying to use the 'd' command. Tried to use the 'R' to load the service information into RAM. But here it starts getting complicated. The command.


or



Issuing command d also fails.


I am using the wrom Diag command set? I found some using google...

Oh why I am doing this, I am currently writing my master thesis evaluating ata security. Thanks in advance for your help, thank you.

u cannot just press few buttons and expect things to work
most of the time it makes it even worst

_________________
Kuwait Data Recovery - UNIX GTC
The only reason for time is so that everything doesn't happen at once. By: Albert Einstein

... you were just a keystroke away from making the drive FUBAR

And I don't see any connection between ATA security and console commands...

yes I see why 'd' was the wrong command. 'Download' works the other way around. But why not telling me in the first place? Okay, other way around, may be this time I'll receive some constructive critics. It should be possible to access the information stored in the service platters, and also the security information. The documentation I have is not very complete. If I destroy the drive, than I'll take a new one. My goal is not to repair the drive, but to extract as many information through the diag mode as possible.


This is my task to evaluate, but as I wrote above and I understood the ATA specification right it is stored somewhere, accessable by diag mode.

@jaypikay:
I don't expect that you will like these comments, but I'll write them anyway, to try to guide your expectations...

Can you understand why discussing this specific subject, in an open forum, is not what everyone will want to help with?


With respect, I'm not sure that you did. What you are doing is not defined in the ATA specification. That specification does not describe using the terminal port on a Seagate drive, since that port is not part of the spec.


The ATA specification does not define exactly where security information is stored on the drive (that varies by drive manufacturer), nor does the spec describe how that information may be accessible, using proprietary methods.

@Vulcan:
Thank you for your answer. I can live with that answers and I see your point with the open forum, totally understandable.