Changes between Version 4 and Version 5 of Ticket #1070, comment 6


Ignore:
Timestamp:
Jun 29, 2020, 5:34:41 PM (17 months ago)
Author:
Christian Franke
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1070, comment 6

    v4 v5  
    77This is with smartmon version 6.6  ... no obvious kernel dmesg errors... attaching output of
    88`smartctl -r ioctl,2 -x /dev/sdb` ... which ... does show the correct log info: (wow!)
    9 
     9{{{
    1010SMART Extended Comprehensive Error Log Version: 1 (1 sectors)
    1111No Errors Logged
     
    1414# 1  Short offline       Completed without error       00%         0         -
    1515# 2  Conveyance offline  Completed without error       00%         0         -
    16 
     16}}}
    1717Above looks correct, since I just plugged in the brand new disk (thus zero lifetime hours), and then ran the conveyance and the short tests...
    1818
    1919Simply running `smartctl -x /dev/sdb` declutters the display slightly, and suggestively reveals the likely problem:
    20 
     20{{{
    2121=== START OF INFORMATION SECTION ===
    2222... the usual stuff...
     
    3838
    3939SCT Error Recovery Control command not supported
    40 
     40}}}
    4141--------
    4242Oh, that's weird ... so I started to just plain use the disk, i.e. gdisk, copy data onto it, etc. and now the log is .. sort of working ... it shows the below ... so that is unexpected but pleasant surprise...
    43 
     43{{{
    4444Read SMART Error Log failed: scsi error badly formed scsi parameters
    4545
     
    5050
    5151Read SMART Selective Self-test Log failed: scsi error badly formed scsi parameters
    52 
     52}}}
    5353... or not ... half an hour later, the self-test log has disappeared, again. (but still visible with `smartctl -x`) I conclude that I have in my possession brand-new faulty hardware with some kind of intermittency bug ...