what I can do to get the ATA error output by sending an incorrect ATA command on purpose

[LeeJeffrey]

Hi, I am now using the pydiskcmd lib to do some ATA protocol test. Some test cases need to send some incorrect field bit on purpose and see the STATUS and ERROR field in ATA error output. This means I need to be able to retrieve the value of ata_pass_thr_return_descriptor even if asc and ascq are incorrect. But the lib always raise an ExecuteCmdErr exception.
How I can do to get the ata status return by this situation.

for example , I create a ata command "read sector ext" by my own. and set the lba field to 0xfffffffff (larger than the max lba range). I expected to get the ata status return and see the STATUS value. But there is always an ExecuteCmdErr exception raised:

Check Condition: Illegal Request(0x05) ASC+Q:LOGICAL BLOCK ADDRESS OUT OF RANGE(0x2100) (Based on Command Execute Error:0x5, Common Error:0x0)

Here is a snapshot which is captured by the SATA protocol Analyzer to show the command:

And I want to get the error output result(the red box position)

Hope u can see this post and help me out.

[jackeichen]

Sorry lost your question, this will be releated to #20 .

This discussion will post here to who have the same question.

[jackeichen]

Waitting an answer:

a small question , it seems the LBA field is not decode correctly. on the same host(kernel 5.15). In the sata analyzer the return lba is ff(low) ff(mid) ff(high). But the new code return ff(low) 00(mid) 00(high).

[jackeichen]

from https://sg.danny.cz/sg/p/sg_v3_ho.html#id2495574.

sb_len_wr
This is the actual number of bytes written to the user memory pointed to by 'sbp'. 'sb_len_wr' is always <= 'mx_sb_len'. Linux 2.2 series kernels (and earlier) truncate this value to a maximum of 16 bytes. The actual number of bytes written will not exceed the length indicated by "Additional Sense Length" field (byte 7) of the Request Sense response. The type of sb_len_wr is unsigned char .

I guess the valid data length in sense_buffer is 18, although we allocate 32 bytes .
While lbal=sense_buffer[17], lbam=sense_buffer[18], lbah=sense_buffer[19], which means it lost the lbam and lbah.

For example:

sb =       b'p\x00\x05\x00\x00\x00\x00\n\x10S\x00\x00!\x00\x00\x00\xa0\xff\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00
\x00\x00'
sb_valid = b'p\x00\x05\x00\x00\x00\x00\n\x10S\x00\x00!\x00\x00\x00\xa0\xff'

only lbal is valid.

@LeeJeffrey I will try to work around it in some way finally, Plz keep patient.

[jackeichen]

@LeeJeffrey We cannot work around it, because the driver only premit 18-length bytes returned. New kernel can be used to avoid it.