Changes between Initial Version and Version 2 of Ticket #89


Ignore:
Timestamp:
Sep 30, 2010, 10:47:09 PM (14 years ago)
Author:
Christian Franke
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #89

    • Property Owner changed from somebody to Christian Franke
    • Property Status new → accepted
    • Property Component smartctl → all

  • Ticket #89 – Description

    initial v2  
    1 Smartctl assumes that the old SMART error log (log address 0x01) is supported if an error-logging capability bit in IDENTIFY or SMART data is set. Same applies to old SMART self-test log (log address 0x06). These logs were introduced in ATA-5 and are now outdated because 48-bit LBA addresses are not supported. Recent devices may only support the newer 48-bit capable logs (extended comprehensive error-log, extended self-test log) introduced in ATA-6.
     1Smartctl and smartd assume that the old SMART error log (log address 0x01) is supported if an error-logging capability bit in IDENTIFY or SMART data is set. Same applies to old SMART self-test log (log address 0x06). These logs were introduced in ATA-5 and are now outdated because 48-bit LBA addresses are not supported. Recent devices may only support the newer 48-bit capable logs (extended comprehensive error-log, extended self-test log) introduced in ATA-6.
    22
    33{{{smartctl -a ...}}} prints misleading messages then:
    … …  
    1010}}}
    1111
     12Misleading kernel messages may appear during smartd startup:
     13{{{
     14... kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
     15... kernel: hda: drive_cmd: error=0x04 { DriveStatusError }
     16... kernel: ide: failed opcode was: 0xb0
     17... smartd[...]: Device: /dev/hda, Read SMART Self Test Log Failed
     18... smartd[...]: Device: /dev/hda, no SMART Self-Test log; remove -l selftest Directive from smartd.conf
     19}}}
     20
    1221({{{smartctl -x ...}}} is not affected)
    1322
    14 Smartctl should check the log directory (log address 0x00) to check whether the old logs are still supported and print an "{{{unsupported}}}" message if not.
     23Smartctl and smartd should read the log directory (log address 0x00) to check whether the old logs are still supported and print an "{{{unsupported}}}" message if not.