Opened 4 years ago

Closed 4 years ago

#637 closed defect (fixed)

smartctl and smartd should not issue SCT commands if drive is locked

Reported by: Alex Samorukov Owned by: Christian Franke
Priority: minor Milestone: Release 6.5
Component: all Version: 6.4
Keywords: ata Cc:

Description (last modified by Alex Samorukov)

If drive is locked using ATA security features running
smartctl -x will trigger SCT commands errors. We should not issue them if drive is locked. According to standard this command will abort in this mode.

Attachments (3)

log_security_unset.txt (11.7 KB) - added by Alex Samorukov 4 years ago.
drive with ATA security disabled
log_security_set_not_locked.txt (11.8 KB) - added by Alex Samorukov 4 years ago.
security set but drive is not locked
log_security_set_locked.txt (7.9 KB) - added by Alex Samorukov 4 years ago.
security set, drive is locked (SCT command fails)

Download all attachments as: .zip

Change History (7)

Changed 4 years ago by Alex Samorukov

Attachment: log_security_unset.txt added

drive with ATA security disabled

Changed 4 years ago by Alex Samorukov

security set but drive is not locked

Changed 4 years ago by Alex Samorukov

Attachment: log_security_set_locked.txt added

security set, drive is locked (SCT command fails)

comment:1 Changed 4 years ago by Alex Samorukov

Keywords: ata added

comment:2 Changed 4 years ago by Alex Samorukov

Description: modified (diff)

comment:3 Changed 4 years ago by Christian Franke

Cc: chfranke removed
Component: smartctlall
Owner: set to Christian Franke
Status: newaccepted

Thanks for testing. I will add this soon.

This also affects smartd -l scterc directive.

comment:4 Changed 4 years ago by Christian Franke

Resolution: fixed
Status: acceptedclosed
Summary: smartctl should not issue SCT commands if drive is lockedsmartctl and smartd should not issue SCT commands if drive is locked
Note: See TracTickets for help on using tickets.