Opened 7 years ago
Closed 7 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 )
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)
Change History (7)
Changed 7 years ago by
Attachment: | log_security_unset.txt added |
---|
Changed 7 years ago by
Attachment: | log_security_set_not_locked.txt added |
---|
security set but drive is not locked
Changed 7 years ago by
Attachment: | log_security_set_locked.txt added |
---|
security set, drive is locked (SCT command fails)
comment:1 Changed 7 years ago by
Keywords: | ata added |
---|
comment:2 Changed 7 years ago by
Description: | modified (diff) |
---|
comment:3 Changed 7 years ago by
Cc: | chfranke removed |
---|---|
Component: | smartctl → all |
Owner: | set to Christian Franke |
Status: | new → accepted |
Thanks for testing. I will add this soon.
This also affects smartd -l scterc directive.
comment:4 Changed 7 years ago by
Resolution: | → fixed |
---|---|
Status: | accepted → closed |
Summary: | smartctl should not issue SCT commands if drive is locked → smartctl and smartd should not issue SCT commands if drive is locked |
Note: See
TracTickets for help on using
tickets.
drive with ATA security disabled