Why was the script unable to run the short test at 7am o'clock?

[Cesar Murilo]

By email, we saw that at 7am o'clock the script was unable to perform any tests for the / dev / sda disk; only for others.

By re-executing the script, the test was performed.

Because the first attempt was not possible? Is there any way to log more deeply to find out the cause?

The result of test at 7am o'clock

SMART Self-test log structure revision number 0
Warning: ATA Specification requires self-test log structure revision number = 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]

The command on script:
/usr/sbin/smartctl -i -l selftest -l error -H -t short {devices}

Thanks for replys

[Christian Franke]

Run smartctl -t short ... as a separate command and check its output and EXIT STATUS (see man page). Then wait a few seconds, run smartctl -c ... an check Self-test execution status:. It should report Self-test routine in progress.... If not, the drive firmware did not start the test properly or the test was very short. Later check smartctl -l selftest -l xselftest ... as -l selftest only prints the legacy self-test log.

The invalid SMART Self-test log structure revision number 0 (see also ticket #1205) suggests that this drive does not implement self-test and self-test logging properly.

[Christian Franke]

Self-tests and self-test logging are controlled by drive firmware. Drive firmware bugs cannot be fixed by smartctl.

PS: AGAIN: this is a bug tracker, not a support forum, see ticket #1205.