Opened 9 years ago

Closed 8 years ago

#147 closed enhancement (fixed)

smartctl logs results of old, and outdated selftest

Reported by: johnjore Owned by: Christian Franke
Priority: major Milestone: Release 5.41
Component: all Version: 5.38
Keywords: Cc:

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 SECTION

SMART 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

Change History (3)

comment:1 in reply to:  description Changed 9 years ago by Christian Franke

Milestone: Release 5.41
Owner: changed from somebody to Christian Franke
Status: newaccepted

Bit 7 of smartctl exit status is always set if at least one self-test log entry reports an error.

I would suggest the following enhancement: If error entries exist bit 7 of smartctl exit status is not set if an entry of a successful long test (Extended offline - Completed without error ...) exists which is newer than all error entries (regardless of the types of the failed tests).

Would this work for you?

comment:2 Changed 9 years ago by johnjore

Thanks for this, and this does sounds like it would work for me. (I'm assuming the notifications from smarctl would therefore stop if this condition is met)

Regards,
John Jore

comment:3 Changed 8 years ago by Christian Franke

Component: smartctlall
Resolution: fixed
Status: acceptedclosed
Note: See TracTickets for help on using tickets.