Re: Device timeout reading fsbn ...

[mlelstv%serpens.de@localhost (Michael van Elst)]

mueller6725%twc.com@localhost ("Thomas Mueller") writes:

>Do you know when (what version) NCQ was introduced to NetBSD?  Was it before or after 7.99.1?

It's only in HEAD and will be in netbsd-9.


>What is atatctl?  "which atatctl" shows nothing.  Is atatctl part of smartmontools?

Sorry, atactl, it is a native command. E.g.

# atactl wd0 smart status
SMART supported, SMART enabled
id value thresh crit collect reliability description                 raw
  1 109    6     yes online  positive    Raw read error rate         25066120
  3 100    0     yes online  positive    Spin-up time                0
  4 100   20     no  online  positive    Start/stop count            77
  5 100   36     yes online  positive    Reallocated sector count    0
  7  86   30     yes online  positive    Seek error rate             415904943
  9  63    0     no  online  positive    Power-on hours count        32748
 10 100   97     yes online  positive    Spin retry count            0
 12 100   20     no  online  positive    Device power cycle count    78
183 100    0     no  online  positive    SATA Downshift Error Count  0
184 100   99     no  online  positive    End-to-end error            0
187 100    0     no  online  positive    Reported uncorrect          0
188 100    0     no  online  positive    Command Timeout             0
189 100    0     no  online  positive    High Fly Writes             0
190  70   45     no  online  positive    Airflow Temperature         30 Lifetime min/max 23/0
194  30    0     no  online  positive    Temperature                 30 Lifetime min/max 0/19
195  50    0     no  online  positive    Hardware ECC Recovered      25066120
197 100    0     no  online  positive    Current pending sector      0
198 100    0     no  offline positive    Offline uncorrectable       0
199 200    0     no  online  positive    Ultra DMA CRC error count   0
240 100    0     no  offline positive    Head flying hours           24661702246380
241 100    0     no  offline positive    Total LBAs Written          4085414554
242 100    0     no  offline positive    Total LBAs Read             4233695140


A high 'raw read error rate' or even recovered ECC errors don't say that
the drive is defective. That's natural behaviour with modern drives
(and some don't hide that).

The 'raw' column is also not standardized and the values may be misleading.
Sometimes smartmontools knows how to interpret the values better.

Critical values (second column) start with some number (mostly 100)
and go down.  The thresholds are based on manufacturing statistics,
when you reach them, it becomes likely that the drive will fail
soon, but maybe it already has :)

Some drives do not have SMART enabled by default. You can change that
with the atactl command, but some drives only then start to collect
statistics.

-- 
-- 
                                Michael van Elst
Internet: mlelstv%serpens.de@localhost
                                "A potential Snark may lurk in every tree."