Opened 9 years ago
Closed 9 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)
by , 9 years ago
| Attachment: | log_security_unset.txt added |
|---|
by , 9 years ago
| Attachment: | log_security_set_not_locked.txt added |
|---|
security set but drive is not locked
by , 9 years ago
| Attachment: | log_security_set_locked.txt added |
|---|
security set, drive is locked (SCT command fails)
comment:1 by , 9 years ago
| Keywords: | ata added |
|---|
comment:2 by , 9 years ago
| Description: | modified (diff) |
|---|
comment:3 by , 9 years ago
| Cc: | removed |
|---|---|
| Component: | smartctl → all |
| Owner: | set to |
| Status: | new → accepted |
Thanks for testing. I will add this soon.
This also affects smartd -l scterc directive.
comment:4 by , 9 years ago
| 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