Custom Query (1359 matches)
Results (79 - 81 of 1359)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #169 | fixed | smartctl man page outdated (SMART offline test ranges) | ||
| Description |
The man page for smartctl(8) on version 5.40 states the following about vendor,N - [ATA only] issues the ATA command SMART EXECUTE OFF-
LINE IMMEDIATE with subcommand N in LBA LOW register. The sub-
command is specified as a hex value in the range 0x00 to 0xff.
Subcommands 0x40-0x7f and 0x90-0xff are reserved for vendor spe-
cific use, see table 61 of T13/1699-D Revision 6a (ATA8-ACS).
This information has been deprecated per working draft of ATA-8 ACS, T13/2015-D Revision 3 (dated June 18, 2010), table 152, provides a more accurate portrait of what the current vendor and reserved SMART test ranges are for OFF-LINE IMMEDIATE: 00h = Execute SMART off-line routine immediately in off-line mode 01h = Execute SMART Short self-test routine immediately in off-line mode 02h = Execute SMART Extended self-test routine immediately in off-line mode 03h = Execute SMART Conveyance self-test routine immediately in off-line mode 04h = Execute SMART Selective self-test routine immediately in off-line mode 05h-3Fh = Reserved 40h-7Eh = Vendor specific 7Fh = Abort off-line mode self-test routine 80h = Reserved 81h = Execute SMART Short self-test routine immediately in captive mode 82h = Execute SMART Extended self-test routine immediately in captive mode 83h = Execute SMART Conveyance self-test routine immediately in captive mode 84h = Execute SMART Selective self-test routine immediately in captive mode 85h-8Fh = Reserved 90h-FFh = Vendor specific
Let me know and I can come up with a patch for |
|||
| #305 | wontfix | smartctl loses 1 byte from response to scsiModeSense in FreeBSD | ||
| Description |
smartctl -a (and smartd as well) gives an error when trying to examine some disks because the response to a mode sense command cannot be parsed (see attached file smartctl.log). However, if the same command is sent with camcontrol, the response is correct (note the leading byte in camcontrol.log, which is not present in smartctl.log). |
|||
| #147 | fixed | smartctl logs results of old, and outdated selftest | ||
| Description |
Test #19 failed, but since then the sector is fixed (somehow, reallocated or read successfully). Test #2 now shows success. Smartctl is ignoring the new success status, and constantly logging the failure. (which propagates up the monitoring chain) Can smartctl be modified, as default or via an option, to use the last "Completed" instead of an old "Completed" ? (I've snipped a number of lines from the output below: START OF READ SMART DATA SECTIONSMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Interrupted (host reset) 90% 22506 - # 2 Extended offline Completed without error 00% 22488 - #19 Extended offline Completed: read failure 90% 20054 824368247 #20 Extended offline Interrupted (host reset) 90% 19903 - Regards, John Jore |
|||
