seagate vsc for send ctrl data like sct cmd: 0x0000 0x0001 0x00BE 0x2459 0x0000 0xa0 0x3F

seagate vsc for Read data like sct cmd: 0x0000 0x0001 0x00BF 0x2459 0x0000 0xa0 0x2F

I know the vsc 3f and 2f ,but i can not get the ctrl data. anyone help?
get the ctrl code ,you can read or write rom ram and sa with sata interface directly, It wont use com port.

_________________
Data and Disk security laboratory：http://www.dadslab.net
Skype: peter.zyo

Here is how it was done in the early days:

Reverse Engineering HDD Software using IDE Port Sniffer:
http://www.hddoracle.com/viewtopic.php?f=59&t=611&p=1613

_________________
A backup a day keeps DR away.

The free version has been limited, just sniffer some seconds. and the author dont reply the email , i dont know why.

_________________
Data and Disk security laboratory：http://www.dadslab.net
Skype: peter.zyo

You would still need a firmware tool to use on the drive, like for example SeDiv or PC-3000 and then you would "sniff" whatever the tool is doing ...

No point of using a "sniffer" if you don't have a tool that is actually sending commands that you want to "sniff"....

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

The Smart Command Transport (SCT) protocol was introduced just to avoid the VSC sniffing!

But if you have some sort of IDE/SATA hardware port "sniffer" you can still see the "packages" inside the SCT.

Also i'm almost certain that they didn't invent the SCT to "hide" VSC. SCT was created for it's own objective, to transport S.M.A.R.T. data.

If they wanted to "encapsulate" VSC intro "something" they could have used old style Quantum and Maxtor system. You send a special key (not SCT related) and that will request for buffer data. Then you send the VSC as buffer data, the same as you would do with SCT but with different commands ...

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

To transport S.M.A.R.T. data between what?

Well,
I hope The HDD and Computer What Else .Do you think or know some other transport also

_________________
Regards
Amarbir S Dhillon , Chandigarh Data Recovery Labs
Logical,Semi Physical And Physical Data Recovery
Website-> http://www.chandigarhdatarecovery.com

Hard drive and host computer ?

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

SCT means Smart Command Transport and not S.M.A.R.T. Command Transport. Do you get it? S.M.A.R.T. data can be transported so easy in a normal way. No need for Action code, Function Code, etc.

http://encyc.org/wiki/SMART_Command_Transport

SMART Command Transport or SCT is a computer storage media protocol which is used for diagnostic and reliability testing of computer storage devices, both traditional Hard Disk Drives (HDD) and Solid-State Drives (SSD). It is an extension of the previously established Self-Monitoring, Analysis, and Reporting Technology (SMART) protocol. This protocol is part of the ATA specification, which itself is a communications protocol for disk drives.

SCT is implemented as a mechanism for sending a series of commands via the SMART protocol. These commands can return various pages of data including thermal profiles, drive access statistics, SATA bus link errors, etc. The protocol uses SMART log pages to communicate back and forth.

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

The SCT Command Transport feature set provides a method for a host to send commands and data to a device and for a device to send data and status to a host using log pages. Log page E0h is used to issue commands and return status. Log page E1h is used to transport data.

SCT commands piggy-back on the standard ATA commands: SMART READ LOG and SMART WRITE LOG, or READ LOG EXT and WRITE LOG EXT. As viewed through an ATA protocol analyzer, an SCT command is seen as data being transferred by these commands

@BGman, I confess I was confused in regard to the meaning of SCT. Thanks for the clarification.

Table A.2 in the ATA standard distinguishes between SMART and SCT feature sets. AIUI, Seagate and WD use the SMART feature set to transport commands and data via vendor specific logs BEh and BFh. The SCT feature set uses standard E0h and E1h logs, although these can themselves transport vendor specific Action Codes.

_________________
A backup a day keeps DR away.

and





It works like this you send the ATA command to write the log page to the drive and the drive reports DRQ and requests for you to send data to the buffer of the drive. From there you send a sector of data with a "key" or VSC on that data. The drive will react to the VSC as "data" instead of sending it as normal ATA command.

Same for retrieve data from the drive. You issue the correct VSC as data on the log page and you retrieve the log page that the drive places on it's buffer with the SCT command to read from the drive.

More or less like that ...

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

The confusion in my case is due to the fact that, while WD uses the SMART feature set, WD's vendor specific command format in log BEh is identical to that used in SCT command/status log E0h (ie Action Code + Function Code + parameter list).

Just to add to the confusion, various documents from t13.org refer to the "SCT Command Transport feature set" and "SMART Command Transport (SCT)". The first is not strictly logical.

_________________
A backup a day keeps DR away.

Well .... At the end of the day it makes no big difference as the way one would use those commands to send data to the drive is more or less the same ...

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

Exactly. It's really just a "semantic" difference.

_________________
A backup a day keeps DR away.

On disks with the WDC mPU (eg Egle), 2 (!) Command systems worked through the 0BEh log

Why do you want to see VSC everywhere? WD is using SCT for more than 10 years. It started with the new generation ROYL drives, Seagate started with F3> dtives, Samsung started with Trinity drives, Hitachi with ARM drives, Toshiba with xx46GSX, etc. VSC generations of drives were replaced by the SCT generation.
Try to "sniff" VDMarvel for example. You'll get nothing because all VSC's are encapsulated in a small piece of data transfered between the host and the drive...

I think you are making a big confusion.

VSC = Vendor Specific Command(s) and those are the commands that are specific to the maker and not standard ATA.

SCT is a "standard". Just because some vendors are using SCT to transmit and recieve Vendor Specific Commands and data it doen't mean that SCT is vendor specific.

Native Quantum and native Maxtor were using encapsulated commands way back .... WD used encapsulated commands even on older WDC based MCU, prior to Marvell. Marvell MCU uses encapsulated commands and even on drives prior to ROYL like Sabre, etc ... Samsung Trinity uses LBA 48 VSC and NOT encapsulated commands. I can show you oif you want. Check my Samsung research thread. There are no SCT generation when we talk about VSC.

Try to sniff WDMarvel with IDE Grabber hardware and we talk later. Just use IDE GRABBER hardware in the middle of your IDE cable and use IDE - SATA adaptor. You will be able to see the data inside the buffer and that includes the SCT or whatever "packet" of data the tool sends to the drive.

This is how one would load VSC (encapsulated) to Maxtor and Quantum using HRT :





Those VSC would be "encapsulated" as data sectors send and recieve to the buffer. If to trigger the DRQ you use some command that is SCT or SMART based or whatever it doesn't matter. As long as you make the drive accept "buffer" (DRQ) you can then send the VSC as "data" to the buffer ...

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.