[Bug 1471462] Re: On bootup smartd reports FailedReadSmartSelfTestLog but there is no hardware problem

[Christian Franke]

> ... kernel: [1128701.864075] ata4.00: cmd b0/d5:01:06:4f:c2/...
> ... kernel: [1128701.864075] res ... Emask 0x4 (timeout)

This ATA cmd is a correct SMART READ LOG 0x06 (self-test log) command.
If the command fails with "timeout", this is possibly not a
smartmontools issue.

> Device info:
> INTEL SSDSA2MH080G1GC, ...

Some older Intel SSDs have known issues with the SMART READ LOG 0x00
(log directory) command: After this command was completed, the drive may
hang. Smartd reads the log directory to check which log is supported,
see https://www.smartmontools.org/ticket/89.

This very old X18/X25-M G1 series SSD may be affected or not. Please try
whether the problem persists if '-F nologdir' is added to the
smartd.conf configuration line.


** Bug watch added: www.smartmontools.org/ #89
   https://www.smartmontools.org/ticket/89

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to smartmontools in Ubuntu.
https://bugs.launchpad.net/bugs/1471462

Title:
  On bootup smartd reports FailedReadSmartSelfTestLog but there is no
  hardware problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1471462/+subscriptions