Opened 7 years ago

Closed 7 years ago

Last modified 5 years ago

#940 closed defect (fixed)

SCT Support Level no longer valid field in ACS3 or 4

Reported by: Bear Owned by: Christian Franke
Priority: minor Milestone: Release 7.0
Component: smartctl Version: 6.6
Keywords: ata Cc:



In version SMARTCTL 6.4 and 6.5 the SCT Support Level output is referencing the sct_spec bytes 4-5 of the SCT status response. In ACS 3 and 4 this is now an Obsolete field.

I would believe this output should be removed.

Attachments (3)

atacmds_sct_spec.png (102.2 KB ) - added by Bear 7 years ago.
SCT_StatusResponse_ACS3.png (90.1 KB ) - added by Bear 7 years ago.
SCTResponse_smartctl6-5.png (30.8 KB ) - added by Bear 7 years ago.

Download all attachments as: .zip

Change History (8)

by Bear, 7 years ago

Attachment: atacmds_sct_spec.png added

by Bear, 7 years ago

Attachment: SCT_StatusResponse_ACS3.png added

by Bear, 7 years ago

Attachment: SCTResponse_smartctl6-5.png added

comment:1 by Christian Franke, 7 years ago

Component: allsmartctl
Keywords: ata added; SCT Support Level sct_spec removed
Milestone: undecided

Various drives return 0, most still return 1. Printing this field is fairly useless but does not do any harm. Possibly field should be printed only if >= 2.

Actually this field was obsolete since the first ATA standard with SCT. It was originally defined in the TR:

T13/1701DT Revision 5, "SMART Command Transport (SCT)", 2005:
SCT Spec. | 0001h - Highest level of SCT Technical Report supported

T13/1699-D Revision 6a, "ATA-8 ACS", 2008:
SCT Spec. | Obsolete

BTW, if we would take all "obsolete" info for serious, there would be no support for SMART thresholds (obsolete since ATA-4, 1998) in any version of smartmontools (since 2002). We also would have to disable important parts of ATA SMART for devices advertising ACS-4 (see T13/f15138, "The SMART Diet").

PS: Please don't attach screen shots if plain/text output is possible.

comment:2 by Bear, 7 years ago

Thank you for the comments. I am verifying the smartctl -x outputs and trying to map them into the spec for various HDDs. I suppose "no harm no foul" but it is a useless field

My bad on the screenshots.

comment:3 by Christian Franke, 7 years ago

Milestone: undecidedRelease 6.7
Owner: set to Christian Franke
Status: newaccepted

comment:4 by Christian Franke, 7 years ago

Resolution: fixed
Status: acceptedclosed

comment:5 by Christian Franke, 5 years ago

Milestone: Release 6.7Release 7.0

Milestone renamed

Note: See TracTickets for help on using tickets.